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 fieldAtlassian Remote MCPMCP100 SelectedWindows-MCPMCP100 Selected
Task fit
Best for
  • 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
  • Using an AI client to inspect and operate Windows applications when no safer application API exists
Not ideal for
  • 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
  • Deterministic automation that can be implemented through a documented API, CLI, or test framework
Avoid when
  • 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
  • The desktop session contains sensitive applications, credentials, messages, or files outside the task
Provenance
Provenance details

First-party MCP

Atlassian · Publisher source ↗

Community implementation

io.github.CursorTouch · Publisher source ↗

Maintenance
Maintenance details

Repo: Not documented

Package: Not documented

Repo: Aug 14, 2026

Package: Aug 1, 2026

Popularity evidence
GitHub starsNot documented

6,749

GitHub stars · checked 2026-08-14T18:46:26.000Z

30-day package downloadsNo reliable download data

40,449

PyPI Stats package downloads · checked 2026-08-14T18:46:26.000Z

External adoption evidenceNot documented
  • github: repository stars: 6,749Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • PyPI Stats: package downloads: 40,449Non-comparable contextual signal.PyPI Stats: package downloads · Provider last month · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Streamable HTTP
Claude Desktop✓ Streamable HTTP
Codex✓ Streamable HTTP
VS Code✓ Streamable HTTP
Cursor✓ Streamable HTTP
OpenCode✓ Streamable HTTP
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationOAuth 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.Stdio has no network listener. Non-loopback HTTP requires an auth key or OAuth unless insecure access is explicitly allowed; IP allowlists, TLS, CORS, and host validation are documented.
CostThe 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.The MIT-licensed project lists no MCP fee. Windows, Python, hosting, client, and model costs are separate.
PermissionsTools 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.Runs with the invoking user's full Windows permissions, including PowerShell, files, registry, processes, UI input, screenshots, and web scraping; many actions are irreversible.
Data handlingThe 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.Processing is local. Telemetry excludes screenshots, state captures, arguments, and outputs but includes status, duration, tool and client information, anonymized sessions, and possibly paths in error messages.
Limitations
Tradeoffs
  • 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.
  • General computer-use reaches many applications, but visual automation is brittle and broad input control can produce high-impact unintended actions.
Risk contextThe 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.It is not sandboxed and can delete files, alter registry or system settings, type into applications, and execute PowerShell. Use a VM or low-privilege account, backups, supervision, loopback binding, and disabled high-risk tools.
Evidence date
Editorial review2026-07-242026-08-11
Candidate evidence2026-07-29T20:58:26.000Z2026-08-14T18:46:26.000Z

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

Read the evidence method →