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.

DimensionOutlook Desktop MCPTurn your running Outlook Desktop into an MCP server. No Graph API, no OAuth.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS59 / 100 · C64 / 100 · C
Reliability8 / 2010 / 20
Security and permissions10 / 2012 / 20
Maintenance12 / 2012 / 20
Documentation15 / 2016 / 20
Setup experience14 / 2014 / 20
Best for
  • Users who have Outlook Desktop installed and want to avoid cloud API integration.
  • Users who need quick setup without OAuth or admin consent.
  • Users who want to leverage local Outlook session and cached data.
  • 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 who do not use Outlook Desktop.
  • Users who need cloud API or remote access to Outlook data.
  • Users on unsupported Outlook versions (e.g., new Outlook on Windows without COM) or without necessary permissions (macOS).
  • 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
  • Windows: Access to Outlook COM object model; may require authorization or registry policy changes.
  • macOS: Requires Automation and Accessibility permissions to control Outlook via osascript and read Exchange inbox.
  • 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
  • Programmatic Access prompts may appear; must allow access or configure registry.
  • Automated tools could be misused by malicious instructions, potentially sending or modifying emails, calendar, or tasks unexpectedly.
  • Local-only, not cloud-based.
  • 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, Claude CodeClaude Code, Codex, Gemini CLI, Cursor
Tools2910