Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldInfluxDB 3 MCPShortlist candidateAtlassian Remote MCPMCP100 Recommended
Task fit
Best for
  • InfluxDB 3 time-series query and diagnostics
  • Use for observability and industrial telemetry queries.
  • Searching and summarizing Jira and Confluence knowledge
  • Creating and updating Jira work items or Confluence content with approval
  • Connecting supported AI clients to Atlassian Cloud without self-hosting a server
Not ideal for
  • Operational metrics and telemetry may expose infrastructure details; query/write permissions differ.
  • Atlassian Server or Data Center deployments
  • Organizations that do not allow enterprise content to pass through an external AI client
  • Headless use when organization administrators do not permit API-token authentication
Avoid when
  • Operational metrics and telemetry may expose infrastructure details; query/write permissions differ.
  • The AI client is not approved for the Jira, Confluence, Bitbucket, Compass, or connected third-party data involved
  • Existing Atlassian user permissions are too broad for agent use
  • Write and bulk actions cannot require review
Provenance
Provenance details

First-party MCP

InfluxData · Publisher source ↗

First-party MCP

Atlassian · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

38

GitHub stars · checked 2026-10-20

Not documented
Package downloads / 30 days

871

package downloads / 30 days · checked 2026-10-20

No reliable download data
Client coverage
Client coverage detailsNot documented
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationInfluxDB 3 connection details depend on deployment: URL plus token for Core/Enterprise/Cloud Serverless, or cluster ID and tokens for Cloud Dedicated/Clustered.OAuth 2.1 browser authorization is the default and recommended method. Admin-enabled, scoped personal API tokens support headless use and are required for Jira Service Management and Bitbucket Cloud tools; Compass tools require OAuth.
CostNo separate MCP fee is documented. InfluxDB Cloud and managed offerings use usage-based or custom pricing; writes, queries, storage and data-out can be billable depending on the product.The core connection has no separately stated MCP fee. Users need applicable Atlassian Cloud products and an AI client. Beta tools are currently free; Atlassian says some may later be billed in Rovo credits with notice, and Teamwork Graph calls are expected to consume credits at general availability.
PermissionsThe server supports a read-only tool profile through INFLUX_MCP_TOOL_PROFILE=readonly; this excludes mutation/admin tools.Tools are grouped by product and read, write, or search intent. Organization admins grant or revoke permission groups, and calls also honor the connected user's Jira, Confluence, Jira Service Management, Bitbucket, Compass, project, space, IP-allowlist, and OAuth or API-token scopes.
Data handlingInfluxDB's MCP telemetry log can include tool name, request/query IDs, duration, database, row count, truncation/success state and error code. It explicitly does not log API tokens, request headers, tool arguments, or query text.The Atlassian-hosted server retrieves and returns authorized Atlassian Cloud content to the external MCP client. Teamwork Graph tools can aggregate relationships across Atlassian products and connected third-party apps and may use AI processing. Traffic uses HTTPS/TLS, and Atlassian records tool-use events in the organization audit log.
Limitations
Tradeoffs
  • Set INFLUX_MCP_TOOL_PROFILE=readonly; npm publishing status unclear, do not assume npx works
  • The hosted service honors existing product permissions and provides audit events, but it can expose broad enterprise knowledge to the connected AI client.
  • OAuth 2.1 is recommended; API tokens support headless workflows but require admin enablement and careful scope management.
  • Some Teamwork Graph and search tools are Beta and may later consume paid Rovo credits.
  • Rovo MCP v2 adds additional supported Atlassian apps through a documented upgrade path; v1 remains documented and is not described as shut down.
Risk contextFull profiles can write data and perform administration. Some operations are irreversible, including database deletion and operator-token regeneration.The integration can read and modify enterprise work and knowledge across several Atlassian products. Approve client domains, use least privilege, restrict permission groups and token scopes, retain write confirmation, review audit logs, and evaluate the external AI client's data policy. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-10-192026-09-05
Candidate evidence2026-10-192026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →