| FMRS | 64 / 100 · C | 79 / 100 · B |
|---|
| Reliability | 7 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 18 / 20 |
|---|
| Maintenance | 14 / 20 | 16 / 20 |
|---|
| Documentation | 17 / 20 | 18 / 20 |
|---|
| Setup experience | 14 / 20 | 15 / 20 |
|---|
| Best for | - Product and frontend teams with paid Figma seats (Dev/Full) who frequently generate code from designs
- Teams with well-structured design systems using components, variables, and Auto Layout
- Teams using Code Connect to keep generated code consistent with real components
| - 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 | - Use cases requiring an offline or local stdio MCP server (this server is remote Streamable HTTP only)
- Starter plan users or View/Collab seat holders, who are capped at 6 tool calls per month
- Scenarios needing direct local filesystem access (this server provides Figma design data, not filesystem access)
| - 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 Figma account authentication (e.g. `/mcp auth figma` in Gemini CLI) to access files the user has permission to view
- The remote server can read design data (layers, variables, styles, screenshots) for selected Figma nodes
- The write-to-canvas feature (remote server only) can create/modify frames, components, variables, and Auto Layout in Figma files
| - 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 | - Design data is processed through Figma's officially hosted remote server and your AI client, not run locally
- Write-to-canvas access could unintentionally modify real Figma files if an agent follows a bad instruction
- Read-type tool calls are rate limited per Figma plan/seat; Starter and View/Collab seat users are capped at just 6 calls per month
- Write-to-canvas is currently free during beta but is expected to become a usage-based paid feature
| - 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 clients | VS Code, Cursor, Claude Code, Gemini CLI | Claude Code, Codex, Gemini CLI, Cursor, VS Code, GitHub Copilot, Continue |
|---|
| Tools | 4 | 0 |
|---|