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.

DimensionVexa MCP ServerOpen-source meeting bots and real-time transcription for Google Meet, Teams and ZoomWhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS57 / 100 · C64 / 100 · C
Reliability9 / 2010 / 20
Security and permissions10 / 2012 / 20
Maintenance13 / 2012 / 20
Documentation14 / 2016 / 20
Setup experience11 / 2014 / 20
Best for
  • Teams that want to self-host and fully own their meeting data and transcripts
  • Regulated organizations needing air-gapped meeting intelligence on their own infrastructure
  • Developers wiring meeting transcripts into their own AI agents and knowledge bases
  • 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 only want hosted SaaS and do not need self-hosting (agent-plane features are self-hosted only)
  • Users needing full mid-call bot control or TTS speech into calls (those endpoints return 404 in the open-core stack)
  • Scenarios requiring guaranteed speaker attribution (heavy crosstalk yields empty speakers on roughly 4–7% of rows)
  • 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 Vexa API key is required for the remote MCP endpoint (Authorization: Bearer header, secret)
  • HTTP API calls use the X-API-Key header
  • Self-hosting requires Docker (engine ≥ v26 recommended) or a Kubernetes/OpenShift cluster
  • Transcription requires an STT service or hosted token; recordings require object storage such as MinIO
  • 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
  • A leaked API key lets someone send bots, read transcripts and dispatch agents as you
  • The bot joins calls as a visible participant, so participant knowledge and consent matter
  • Recordings and transcripts may contain sensitive content; self-hosting with your own storage controls the data boundary
  • Agents handling untrusted input (email, web pages) must run propose-only with human approval, otherwise writes can be irreversible
  • In the open-core stack, mid-call bot config and speak endpoints currently return 404 and should not be relied on
  • 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, CodexClaude Code, Codex, Gemini CLI, Cursor
Tools010