Notion MCP Server vs Slack MCP Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Notion MCP Server MCP Servers	Slack MCP Server MCP Servers
Tagline	The official Notion MCP server: give Claude, Cursor, and Copilot typed access to your Notion pages, databases, and comments.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
Category	MCP Servers	MCP Servers
Pricing	Free· Server is free and MIT-licensed; a paid Notion workspace is only required for features gated behind Notion's own plans. Notion tiers: Free / Plus $10 per user/mo / Business $18 per user/mo / Enterprise (custom).	Free· Free / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
Model	—	—
Editorial score	—	—
Use cases	AI agent drafting weekly status reports into a Notion pageResearch assistant querying a projects database and appending findingsMeeting-notes pipeline inlining transcripts as Markdown blocksClaude Code reading a spec page and filing follow-up commentsCross-workspace search from a chat clientAutomated triage that comments on pages by title matchTemplate-driven page creation under a specified parentKnowledge-base RAG grounding pulled live from Notion pages	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
Pros	Official and actively maintained by Notion, so the tool surface tracks the real API rather than a community reverse-engineering Markdown read/write endpoints make page editing dramatically more token-efficient than raw block JSON Runs via npx or Docker with no build step; wiring into Claude Desktop, Cursor, or Copilot CLI is a small JSON snippet Both stdio and streamable HTTP transports, with bearer-token auth and per-request token passthrough for multi-tenant hosting Permission scope is bounded by which pages you share with the integration in Notion, giving fine-grained blast-radius control MIT-licensed and easy to fork if you need custom tool shapes or additional guardrails Broad coverage: pages, blocks, data sources, comments, search, templates, and content moves	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
Cons	Internal-integration tokens are static secrets; there is no first-party OAuth flow in the local server yet (a remote OAuth version is hinted but not shipped) V2.0 dropped the old database_id tools in favour of data_source_id, so older agent prompts and any scripts that hard-coded the previous tool names need to be updated Intentionally omits destructive operations like deleting databases, which is safe but occasionally frustrating for cleanup workflows README itself flags a non-zero risk of exposing workspace data to an LLM; you need to think about read-only integrations for sensitive spaces Requires a per-page or per-database access grant in Notion for every resource the agent should see — easy to forget and a common cause of empty query results Rate limits, pagination quirks, and schema oddities are inherited from the underlying Notion API and are not smoothed over by the server	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
Website	github.com	github.com

Pick Notion MCP Server if

✅ Official and actively maintained by Notion, so the tool surface tracks the real API rather than a community reverse-engineering
✅ Markdown read/write endpoints make page editing dramatically more token-efficient than raw block JSON
✅ Runs via npx or Docker with no build step; wiring into Claude Desktop, Cursor, or Copilot CLI is a small JSON snippet
✅ Both stdio and streamable HTTP transports, with bearer-token auth and per-request token passthrough for multi-tenant hosting

Pick Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →