M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
COMPARE UP TO 4 SERVERS

Compare MCP servers

Compare scores, permissions, risks, and fit in one decision-focused table.

DimensionBetter Notion MCP ServerMarkdown-first Notion for AI agents -- pages, databases, blocks, and comments in one callWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS63 / 100 · C64 / 100 · C
Reliability8 / 2010 / 20
Security and permissions12 / 2012 / 20
Maintenance15 / 2012 / 20
Documentation15 / 2016 / 20
Setup experience13 / 2014 / 20
Best for
  • Heavy Notion users who want Markdown-based collaboration with AI agents
  • Developers integrating Notion workflows into Claude Code, Cursor, and similar clients
  • Automation scenarios needing the full Notion surface: uploads, comments, block-level edits
  • Individuals who want to talk to Claude from their personal WhatsApp number
  • Developers comfortable configuring from a terminal and using the Claude Code development flag
  • Automation scenarios needing remote tool approval from a phone
Not for
  • Users seeking a server officially supported by Notion (this is third-party open source)
  • Users unwilling to grant a Notion integration token or complete OAuth consent
  • Environments with Node.js < 24 and no Docker available
  • Compliance scenarios requiring the official WhatsApp Business API or a Meta developer account
  • Teams needing officially hosted, multi-tenant, or cloud multi-instance deployment
  • Environments unable to guarantee only one client instance at a time
  • Users expecting voice transcription without setting up mlx-whisper themselves
Required permissions
  • Requires a Notion integration token (ntn_ prefix); it can only access pages explicitly shared with the integration
  • HTTP mode requires a Notion Public Integration OAuth client ID and secret
  • Token is passed via the NOTION_TOKEN environment variable and is a secret
  • Read and send WhatsApp messages as your personal number
  • Access the local runtime state directory ~/.whatsapp-channel/ (auth, allowlists, group configs, inbox)
  • Read and write local repository files and run scripts (e.g. bun scripts/access.ts, scripts/watchdog.sh)
  • Optional local voice transcription (ffmpeg and an mlx-whisper environment)
Risks and side effects
  • Third-party project not maintained by Notion; review the code yourself
  • In stdio mode the token is stored AES-GCM encrypted in a local config file, but the integration token itself is broad in scope
  • In hosted HTTP mode tokens live only in process memory and are cleared on restart
  • Setting MCP_AUTH_DISABLE=1 on a shared/public deployment collapses all users into a single token bucket -- a serious risk
  • Earlier versions had instability around credential handling and daemon-bridge auto-spawn; use the latest release
  • Messages Claude sends appear from your own number and are indistinguishable to recipients
  • WhatsApp allows one linked-device session per account; running two servers makes them kick each other off
  • Access-control commands are deliberately not MCP tools (terminal-only); exposing them to the message side risks prompt injection
  • Session waking depends on the Claude Code channel extension; other clients get no push
  • A known Claude Code client bug (#37933) may cause messages not to arrive, a client-side issue
  • Launching with --dangerously-load-development-channels carries risk, so verify the source is trustworthy
Supported clientsClaude Code, Cursor, Codex, Gemini CLI, WindsurfClaude Code, Codex, Gemini CLI, Cursor
Tools1110