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 fieldBeadsWatchlist candidateAtlassian Remote MCPMCP100 Selected
Task fit
Best for
  • Coding-agent teams that want persistent dependency-aware issue/task memory and specifically need an MCP-only interface.
  • 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
  • Shell-capable coding agents where the project itself recommends the CLI, or contexts highly sensitive to MCP schema/token overhead.
  • 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
  • Avoid treating publisher-estimated context overhead as a measured MCP100 Context Footprint; runtime footprint remains unmeasured unless protocol-measured.
  • 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

Ecosystem official

github:gastownhall · Publisher source ↗

First-party MCP

Atlassian · Publisher source ↗

Maintenance
Maintenance details

Stale

Repo: Not documented

Package: Not documented

Repo: Not documented

Package: Not documented

Popularity evidence
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
AuthenticationTypically local project/workspace access rather than a hosted user OAuth service; exact server authentication is deployment-dependent and must come from bound local evidence.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.
CostOpen-source project; local database/infrastructure/model costs may apply.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.
PermissionsCan read/update Beads task/issue state in the configured workspace/database.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 handlingAgent task descriptions, dependencies and project-management context are persisted in the Beads data store and exposed to the connected client.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
  • Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Selected.
  • 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 contextMCP is a secondary interface and can add material schema/context overhead; protect persistent project/task data.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-09-13T00:00:00Z2026-09-05
Candidate evidence2026-09-13T00:00:00Z2026-09-05T00:00:00.000Z

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

Read the evidence method →