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.

DimensionGoogle Workspace MCPControl Google Workspace with natural language.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS56 / 100 · C64 / 100 · C
Reliability8 / 2010 / 20
Security and permissions10 / 2012 / 20
Maintenance12 / 2012 / 20
Documentation14 / 2016 / 20
Setup experience12 / 2014 / 20
Best for
  • Individuals and teams needing access to several Google Workspace services.
  • Developers deploying by tool tier, service, or permission scope.
  • Organizations needing self-hosted, multi-user OAuth 2.1, or container deployments.
  • Developers who want to call MCP tools through a CLI.
  • 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 requiring a server maintained by Google.
  • Users with only a personal @gmail.com account who need Google Chat.
  • Users unwilling to configure Google Cloud OAuth credentials or APIs.
  • Applications seeking unauthorized access to Google Workspace data.
  • 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 Google Cloud OAuth client credentials.
  • OAuth scopes depend on the enabled services and tools.
  • Supports read-only scopes, per-service granular permissions, and full access.
  • Write tools for Drive, Gmail, and other services require corresponding write permissions.
  • Google Chat requires a configured Chat app and a Google Workspace account.
  • Optional service-account mode requires service-account credentials and domain-wide delegation.
  • 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
  • Full tools and write scopes may allow modifying, sending, deleting, or sharing user data.
  • For public deployments, unrestricted dynamic-client redirect URIs can create a phishing risk.
  • Stdio is a legacy fallback; OAuth 2.1 is recommended for remote or shared deployments.
  • Local attachments and credential stores write to configured local directories; stateless mode avoids file writes.
  • Google API quotas, OAuth consent configuration, and account permissions may limit functionality.
  • The Chat API is unavailable for personal Gmail accounts.
  • 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 Code, VS Code, LM StudioClaude Code, Codex, Gemini CLI, Cursor
Tools2910