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.

DimensionSlack MCP ServerSend messages & manage channelsWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS58 / 100 · C64 / 100 · C
Reliability13 / 2010 / 20
Security and permissions11 / 2012 / 20
Maintenance10 / 2012 / 20
Documentation13 / 2016 / 20
Setup experience11 / 2014 / 20
Best for
  • Internal collaboration workflows that need channel history or team notifications
  • Development teams testing message automation in a non-production workspace
  • 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
  • Organizations that prohibit model access to internal chat history
  • Workspaces that cannot tightly restrict bot channels and OAuth scopes
  • 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
  • A Slack Bot Token and Team ID
  • Least-privilege OAuth scopes for channel history, messages, or reactions
  • 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
  • Channel history may contain internal or personally sensitive information
  • Messages and reactions are visible to real members; confirm channel and content before writes
  • 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 Desktop, Cursor, ClineClaude Code, Codex, Gemini CLI, Cursor
Tools410