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.

DimensionAttio MCP ServerAI-powered Attio CRM access. Manage contacts, companies, deals, tasks, notes and workflows.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS52 / 100 · D64 / 100 · C
Reliability7 / 2010 / 20
Security and permissions11 / 2012 / 20
Maintenance10 / 2012 / 20
Documentation12 / 2016 / 20
Setup experience12 / 2014 / 20
Best for
  • Attio users looking to automate CRM workflows with AI assistants, reducing manual input
  • Teams needing integration with Claude Desktop, Cursor, or Claude Code
  • Those who want to query CRM data and manage deals, lists, and tasks via natural language
  • 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 without an Attio account or API key
  • Scenarios requiring local data storage or offline operations (server proxies API, does not store data)
  • Those who wish to restrict to read-only tools (can be achieved by setting `ATTIO_MCP_TOOL_MODE=search`)
  • 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 `ATTIO_API_KEY` environment variable (required API key)
  • Optional workspace ID: `ATTIO_WORKSPACE_ID`
  • Optional tool mode: `ATTIO_MCP_TOOL_MODE` ('full' or 'search')
  • Optional log level: `MCP_LOG_LEVEL`
  • Options for default deal stage, owner, currency can be configured
  • 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
  • API key exposure: if the API key is shared or exposed, others could access your CRM data
  • Data modification risk: default tool mode allows write operations (create, update, delete), potentially leading to accidental changes
  • Third-party dependency risk: open-source project, self-audit required
  • Configuration error risk: improper field mapping configuration can lead to API call failures
  • 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 Web, Cursor, Claude CodeClaude Code, Codex, Gemini CLI, Cursor
Tools2410