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.
| Evidence field | io.github.mobile-next/mobile-mcpWatchlist candidate | Notion MCPMCP100 Selected |
|---|---|---|
| Task fit | ||
| Best for |
|
|
| Not ideal for |
|
|
| Avoid when |
|
|
| Provenance | ||
| Provenance details | Community implementation io.github.mobile-next · Publisher source ↗ | First-party MCP Notion · Publisher source ↗ |
| Maintenance | ||
| Maintenance details | Repo: Aug 9, 2026 Package: Aug 9, 2026 | Repo: Jul 25, 2026 Package: Jul 25, 2026 |
| Popularity evidence | ||
| GitHub stars | 5,918 GitHub stars · checked 2026-08-14T18:46:26.000Z | 4,594 GitHub stars · checked 2026-08-14T18:46:26.000Z |
| 30-day package downloads | 95,397 30-day package downloads · checked 2026-08-14T18:46:26.000Z | 624,402 30-day package downloads · checked 2026-07-29T17:30:00.000Z |
| External adoption evidence |
|
|
| 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 note | Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server. | |
| Access and data | ||
| Authentication | Stdio 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. | The supported hosted service uses OAuth. The documented local server uses NOTION_TOKEN or OPENAPI_MCP_HEADERS; HTTP transport has a separate bearer token and supports carefully configured per-request Notion token passthrough. |
| Cost | The Apache-2.0 project lists no MCP fee. Devices, platform tooling, client, model, and hosting costs are separate. | The local server is MIT licensed. A Notion account and workspace plan are required, and Notion plan/API limits apply; hosted MCP-specific charges were not established in the reviewed materials. |
| Permissions | Controls 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. | Local access is limited by the Notion integration capabilities and pages connected to that integration. Read-only capability is available; write-capable tools can create or update workspace content. Local HTTP transport requires bearer authentication unless an explicitly unsafe flag disables it. |
| Data handling | Returns 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. | Page/database content accessible to the integration can be returned to the MCP client and model. The local server calls Notion APIs; hosted Notion MCP additionally processes requests through Notion's remote service. |
| Limitations | ||
| Tradeoffs |
|
|
| Risk context | Device 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. | Workspace content may be read or modified within the integration's reach. Use a dedicated integration, Read content only where possible, explicitly connect only needed pages, avoid unsafe HTTP auth disabling, and monitor hosted/local migration guidance. |
| Evidence date | ||
| Editorial review | 2026-08-11 | 2026-07-24 |
| Candidate evidence | 2026-08-14T18:46:26.000Z | 2026-08-14T18:46:26.000Z |
Popularity, maintenance, fit, permissions, and client support are independent evidence fields.
Read the evidence method →