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.

DimensionTalkToFigmaConnect AI agents to Figma for programmatic design work through MCP.WhatsApp Channel for Claude CodeDrive your Claude Code session straight from WhatsApp
FMRS47 / 100 · D64 / 100 · C
Reliability8 / 2010 / 20
Security and permissions7 / 2012 / 20
Maintenance10 / 2012 / 20
Documentation11 / 2016 / 20
Setup experience11 / 2014 / 20
Best for
  • Design and development teams using Cursor, Claude Code, or Codex to drive Figma with natural language
  • Figma workflows requiring batch text, layout, annotation, or component-instance operations
  • Users able to run Bun, a WebSocket server, and a Figma plugin
  • 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
  • Static file-reading workflows that do not run the Figma plugin
  • Read-only review workflows where AI must not modify the Figma document
  • Workflows requiring explicitly documented remote hosting, authentication, or another transport
  • 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 running the companion development plugin in Figma
  • Requires local WebSocket communication between the MCP server and the Figma plugin
  • Modification tools require corresponding read/write access to the current Figma document; the exact scope depends on the tool used
  • 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
  • delete_node and delete_multiple_nodes remove nodes, so targets should be confirmed and results verified
  • Batch text, layout, styling, and instance-override operations can affect multiple design elements
  • Incorrect WebSocket channel connections can prevent communication with Figma
  • Node image export has limited support and returns base64 as text
  • 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 clientsCursor, Claude Code, CodexClaude Code, Codex, Gemini CLI, Cursor
Tools4010