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 fieldio.github.mobile-next/mobile-mcpShortlist candidateAtlassian Remote MCPMCP100 Recommended
Task fit
Best for
  • Letting an MCP client inspect and automate publisher-supported Android and iOS testing workflows
  • 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
  • Deterministic API-level tests or production devices where broad UI control is unnecessary
  • 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
  • The target device contains personal accounts, messages, credentials, photos, or other data outside the test scope
  • 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

Community implementation

io.github.mobile-next · Publisher source ↗

First-party MCP

Atlassian · Publisher source ↗

Maintenance
Maintenance details

Repo: Aug 9, 2026

Package: Aug 9, 2026

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

5,918

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

Not documented
Package downloads / 30 days

95,397

package downloads / 30 days · checked 2026-08-14T18:46:26.000Z

No reliable download data
External adoption evidence
  • npm: package downloads: 95,397Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
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
AuthenticationStdio has no authentication documented. SSE defaults to localhost:3000 and supports Bearer authorization through MOBILEMCP_AUTH; binding to 0.0.0.0 is also documented.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.
CostThe Apache-2.0 project lists no MCP fee. Devices, platform tooling, client, model, and hosting costs are separate.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.
PermissionsControls iOS and Android simulators, emulators, and real devices, including app install, uninstall and launch, taps, gestures, typing, screenshots, recordings, URLs, hardware buttons, and crash reports.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 handlingReturns accessibility-tree data, screenshots, recordings, app and device metadata, and crash reports to the connected client. Telemetry, retention, and model-training behavior are not documented.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
  • Cross-platform device control can accelerate exploratory testing, while UI automation is brittle and broad device access raises the impact of unintended actions.
  • 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 contextDevice control, app installation and removal, screenshots, recordings, URLs, and crash reports can expose or change sensitive devices. Keep SSE local or set MOBILEMCP_AUTH before network exposure.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-08-112026-09-05
Candidate evidence2026-08-14T18:46:26.000Z2026-09-24T04:25:05.554391Z

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

Read the evidence method →