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.

DimensionOpenWAFree, open-source WhatsApp API gateway that can serve as an MCP server for AI agentsMartinLoop MCP ServerAn independent control layer that gives AI coding agents budgets, brakes, and receipts
FMRS47 / 100 · D79 / 100 · B
Reliability5 / 2012 / 20
Security and permissions10 / 2018 / 20
Maintenance6 / 2016 / 20
Documentation14 / 2018 / 20
Setup experience12 / 2015 / 20
Best for
  • Developers and hobbyists wanting a self-hosted WhatsApp API gateway
  • Scenarios requiring WhatsApp automation integrated into AI agents
  • Personal projects or internal tools needing low-cost messaging automation
  • Developers willing to accept unofficial API risks and account restrictions
  • Engineering teams scaling AI coding agents while controlling spend
  • Platform teams that need auditable, rollback-aware agent execution records
  • Organizations using multiple agents (Claude, Codex, Gemini) under one governed flow
Not for
  • Production environments requiring official WhatsApp Cloud API compliance (e.g., healthcare, finance, large-scale commercial messaging)
  • Users who cannot accept account ban risks
  • Users wanting zero-configuration setup (requires some deployment and configuration)
  • Scenarios needing full REST API coverage (MCP exposes only curated tools)
  • Developers who just want a simple code-completion helper without run governance
  • Teams unwilling to accept local JSONL run records with HMAC signing
  • Environments without a supported adapter (Claude/Codex/Gemini CLIs, direct provider, or verifier-only)
Required permissions
  • Requires API key authentication (role OPERATOR or lower, session-scoped)
  • May require access to the Docker socket (if using built-in orchestration, protected by docker-proxy)
  • MCP endpoint must be reachable from the client (e.g., localhost or LAN)
  • Recommended to use a dedicated WhatsApp number to avoid risks to primary numbers
  • Read/write access to the configured repo root (writable scope restrictable via --allow-path/--deny-path)
  • Ability to invoke the chosen agent CLI (Claude/Codex/Gemini, etc.) and its underlying model account
  • Local disk writes for run records, receipts, and share outputs (share/run-receipt., etc.)
  • Execution of user-configured verifier commands (e.g. npm test)
Risks and side effects
  • Unofficial WhatsApp API, risk of account restriction or ban
  • Messages may be dropped by WhatsApp server-side (first message to new contacts)
  • Requires regular updates to dependencies to cope with WhatsApp protocol changes
  • If /mcp is exposed publicly without an auth proxy, it could be abused
  • Verifier commands are executed; poorly chosen verifier commands carry security risk despite preflight policy checks
  • Cost and token figures may be estimates (labeled with provenance) and should not be treated as settled accounting
  • Receipt integrity must be verified before use as trustworthy evidence; missing rollback evidence is flagged as EVIDENCE_BOUNDARY
  • Policy defaults come from martin.config.yaml and can be overridden by CLI flags; misconfiguration can loosen safety boundaries
Supported clientsClaude Desktop, CursorClaude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue
Tools10