| FMRS | 64 / 100 · C | 63 / 100 · C |
|---|
| Reliability | 10 / 20 | 8 / 20 |
|---|
| Security and permissions | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 12 / 20 | 15 / 20 |
|---|
| Documentation | 16 / 20 | 14 / 20 |
|---|
| Setup experience | 14 / 20 | 13 / 20 |
|---|
| Best for | - 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
| - Designers and design system teams looking to integrate AI into their workflow.
- Developers needing quick prototyping or visual spec generation.
- Product managers who need to communicate visual requirements during discussions.
- Teams managing multi-file design systems (via figma_execute_across_files).
- Developers who need to export tokens from Figma to their codebase (token sync).
|
|---|
| Not for | - 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
| - Users who need read-only access and want to avoid installing Node.js — consider Remote SSE mode (9 read-only tools).
- Users who strictly need code generation (e.g., React/HTML) — the official Figma Dev Mode MCP is more suitable.
- Users who want quick evaluation without write capabilities — Remote SSE is sufficient.
- Users who want to design in the cloud but avoid installing the Desktop Bridge plugin (Cloud Mode still requires the plugin).
|
|---|
| Required permissions | - 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)
| - Figma personal access token (PAT): file content read, file versions read, variables read, comments read/write (local mode).
- Desktop Bridge plugin permissions: access current file via plugin API, read selection, console logs, document changes, and execute write operations (create frames, variables, etc.).
- Local filesystem: the server writes/reads plugin files in ~/.figma-console-mcp/ (auto-created).
- WebSocket ports 9223-9232: the server listens on these ports locally for plugin connections.
- For Cloud Mode, OAuth is required (remote endpoint) or PAT (Cloud Mode bypasses Enterprise restrictions).
|
|---|
| Risks and side effects | - 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
| - Write operation risk: tools like figma_execute can run arbitrary plugin code, potentially modifying or deleting designs unintentionally — test on a copy file first.
- Token leakage: FIGMA_ACCESS_TOKEN is stored in plaintext in client configs; if the config file leaks, the token could be abused.
- Remote server trust: the remote SSE endpoint is hosted by a third party (southleft); data (design info) passes through their infrastructure; self-hosting options exist.
- Multi-instance issues: port conflicts may cause connection issues, but multi-instance support is implemented (automatic port fallback).
- Update banner issue: plugin-server version mismatch may cause persistent re-import prompts — fixed in recent releases, but restart clients after upgrading.
|
|---|
| Supported clients | Claude Code, Codex, Gemini CLI, Cursor | Claude Desktop, Claude Code, Cursor, Windsurf |
|---|
| Tools | 10 | 74 |
|---|