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 fieldNotion MCPMCP100 SelectedSlack MCP ServerMCP100 Selected
Task fit
Best for
  • Reading and updating explicitly shared Notion pages
  • Markdown-oriented page workflows
  • Teams able to create a dedicated least-privilege integration
  • Searching approved Slack channels, messages, files, users, and emoji
  • Reading project conversations and threads from an MCP client
  • Drafting or sending messages and managing canvases with explicit user approval
Not ideal for
  • Whole-workspace access without page scoping
  • Stable local-server APIs with no migration monitoring
  • Workflows that only need occasional manual Notion lookup
  • Bulk Slack export or archival
  • Unattended messaging, channel creation, or canvas modification
Avoid when
  • Sensitive workspace content cannot be exposed to the connected model/client
  • You cannot create a dedicated read-only integration or restrict page access
  • You depend on removed pre-2.0 database tool names
  • Private channels, direct messages, files, or user profiles cannot be shared with the external AI client
  • Workspace administrators have not approved the Slack app and MCP integration
  • The agent combines untrusted external content with write-capable Slack tools without isolation
Provenance
Provenance details

First-party MCP

Notion · Publisher source ↗

First-party MCP

Slack · Publisher source ↗

Maintenance
Maintenance details

Repo: Jul 25, 2026

Package: Jul 25, 2026

Repo: Not documented

Package: Not documented

Popularity evidence
GitHub stars

4,594

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

Not documented
30-day package downloads

624,402

30-day package downloads · checked 2026-07-29T17:30:00.000Z

No reliable download data
External adoption evidence
  • npm: package downloads: 624,402Exact attributable signal.npm: package downloads · Admission snapshot · checked 2026-07-29T17:30:00.000ZEvidence source ↗
  • github: repository stars: 4,594Exact attributable signal.github: repository stars · Admission snapshot · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Not documented
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✓ 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
AuthenticationThe 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.Slack uses confidential OAuth for MCP clients with a registered fixed Slack app ID and client secret. Cursor's publisher-documented integration uses Slack's fixed client ID and opens an OAuth workspace authorization flow.
CostThe 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.Slack documents no separate MCP server fee. Access to history, search, apps, administration, and AI-client capabilities depends on the workspace's Slack plan; standard Slack API rate limits apply.
PermissionsLocal 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.Slack maps tools to granular user-token scopes for public/private/DM search, files, channel history, messages, reactions, conversations, canvases, profiles, and member lists. Actions execute on behalf of the authenticated user and remain subject to workspace/app approval, Slack access controls, and IP allowlists.
Data handlingPage/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.Searches, messages, channel history, file content, canvases, user profiles, and tool outputs flow through Slack's managed MCP endpoint to the configured client and its model provider. Slack audit logs can record MCP activity; client-side retention is governed separately.
Limitations
Tradeoffs
  • Hosted OAuth is actively supported and easier; the local repository warns it may be sunset.
  • Write capability enables useful edits but raises deletion, overwrite, and prompt-injection risk.
  • Version 2 changed database operations to data-source tools, requiring updates to hardcoded prompts.
  • Granular OAuth scopes allow narrow access, but useful cross-workspace search can still reveal highly sensitive conversations.
  • Slack's managed endpoint avoids a local server, while requiring confidential OAuth, a fixed app ID, and an eligible directory-published or internal app.
  • The server includes both read and write tools and is subject to Slack Web API rate limits.
Risk contextWorkspace 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.Slack may contain private messages, credentials, customer data, files, and regulated communications. Request only required OAuth scopes, use an approved app, review the client/model retention policy, isolate other untrusted MCP sources, audit activity, and confirm every send/create/update action. This review does not claim MCP100 execution testing.
Evidence date
Editorial review2026-07-242026-07-24
Candidate evidence2026-08-14T18:46:26.000Z2026-07-29T20:58:26.000Z

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

Read the evidence method →