Claude Talk to Figma MCP

Enables AI agents to read, analyze, and modify Figma designs via MCP. Connects through a local WebSocket server and a Figma plugin, allowing agents to extract document info, create shapes/text/frames, modify styles (colors, borders, shadows, typography, auto-layout), and work with components.

Evaluated Mar 06, 2026 (0d ago) v0.9.2
Homepage ↗ Repo ↗ Developer Tools figma mcp design-automation websocket ui-design component-management
⚙ Agent Friendliness
73
/ 100
Can an agent use this?
🔒 Security
80
/ 100
Is it safe for agents?
⚡ Reliability
70
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
72
Documentation
75
Error Messages
50
Auth Simplicity
78
Rate Limits
68

🔒 Security

TLS Enforcement
95
Auth Strength
78
Scope Granularity
72
Dep. Hygiene
78
Secret Handling
75

Figma design tool MCP. Figma OAuth2 token. Design files may contain proprietary IP. Read vs edit scope — use read-only for analysis agents.

⚡ Reliability

Uptime/SLA
72
Version Stability
72
Breaking Changes
68
Error Recovery
70
AF Security Reliability

Best When

You want an AI agent to directly read and manipulate Figma designs without requiring Figma Dev Mode, and you are comfortable running a local WebSocket server.

Avoid When

You need a cloud-hosted or headless solution without Figma Desktop, or you need production-grade stability (still v0.9.x).

Use Cases

  • AI-assisted UI design iteration directly in Figma
  • Programmatic creation of design elements from natural language descriptions
  • Auditing and analyzing existing Figma designs for consistency
  • Batch modifications to colors, typography, and layout across a design file
  • Extracting design tokens and component information for handoff

Not For

  • Figma-to-code generation (planned but not yet available)
  • Collaborative real-time design with multiple human designers simultaneously
  • Working with Figma files without Figma Desktop installed

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: websocket-channel-id
OAuth: No Scopes: No

Uses a WebSocket channel ID copied from the Figma plugin to establish a connection. No API keys or OAuth needed.

Pricing

Model: open_source
Free tier: Yes
Requires CC: No

MIT licensed. Requires Figma account (free or paid) and Figma Desktop.

Agent Metadata

Pagination
unknown
Idempotent
Unknown
Retry Guidance
Not documented

Known Gotchas

  • Requires Figma Desktop running with the plugin active - cannot work headlessly
  • WebSocket channel ID must be manually copied and provided to the agent each session
  • Still pre-1.0; API surface may change between versions

Alternatives

Full Evaluation Report

Detailed scoring breakdown, competitive positioning, security analysis, and improvement recommendations for Claude Talk to Figma MCP.

$99

Scores are editorial opinions as of 2026-03-06.

5225
Packages Evaluated
26151
Need Evaluation
173
Need Re-evaluation
Community Powered