Slack MCP Server vs Notion MCP Server
Where does your team's context live? The archived Slack reference server gives Claude access to channels and messages — conversational, ephemeral context. The Notion server reaches structured, long-lived documents. For agent workflows that summarize discussions, Slack fits; for ones that read and update specs, Notion — and Notion's active maintenance is a real advantage over an archived reference implementation.
GitHub data verified 2026-07-30 — objective fields only, no editorial scoring.
| Slack MCP Server Slack workspace integration for channels, messages, and user management | Notion MCP Server Read and write Notion pages, databases, and blocks | |
|---|---|---|
| GitHub stars | 293 | 4,560 |
| Forks | 165 | 612 |
| Open issues | 0 | 193 |
| Last commit | 2025-05-28 | 2026-07-25 |
| Maintenance status | Archived (read-only) | Actively maintained |
| License | MIT | MIT |
| Language | TypeScript | TypeScript |
| Install | npx @modelcontextprotocol/server-slack | — |
| Author | Anthropic | Notion |
| Official listing | Yes | No |
| Community votes | 0 | 0 |
| Copies from directory | 0 | 0 |
GitHub statistics are measured at repository level; servers that live in a shared monorepo show that repository's stats. This comparison is generated from directory data — no sponsored placement, see the curation policy.