Skip to content
aicoolies logo
cursor-talk-to-figma-mcp Grab parent mark

Talk to Figma MCP

Read/write MCP bridge between AI coding agents and Figma

Talk to Figma MCP is an MIT-licensed bridge from Grab that connects Cursor, Claude Code, and other MCP-capable agents to Figma through a local MCP server, WebSocket bridge, and Figma plugin. Unlike read-only context servers, it can inspect selections, create or modify nodes, update text in bulk, and automate design operations, so teams should review permissions before enabling write access.

About Talk to Figma MCP

Talk to Figma MCP is a read/write Model Context Protocol integration between AI coding agents and Figma. The project connects an MCP server, a local WebSocket bridge, and a Figma plugin so tools such as Cursor and Claude Code can inspect selected frames, read node information, create design elements, modify existing nodes, update text content in bulk, and work with components, styles, annotations, and prototype connections. That makes it a more operational Figma bridge than screenshot prompting or read-only context extraction.

The strongest use case is agent-assisted design-to-code handoff where the developer wants the agent to understand the current Figma selection and, when appropriate, push structured changes back into the design file. The repository documents a Bun-based setup, Cursor MCP configuration, a WebSocket server, local plugin installation, and examples such as bulk text replacement and instance override propagation. With 6.8K+ GitHub stars, 700+ forks, MIT licensing, and a public Figma Community plugin link, it has enough traction to merit a dedicated aicoolies tool page in the UI/design-to-code and MCP server clusters.

Teams should treat the write path as a governance decision rather than a default. The tool can be valuable for design automation, batch edits, and agentic UI workflows, but it also means an MCP-enabled agent can act on live Figma documents through the plugin bridge. Sensitive design systems should start with limited files, local development channels, explicit Figma permissions, and human review of generated changes. For lower-risk implementation context only, a read-only server such as Figma Context MCP may remain the safer default.

Pricing & Platform Specs

Pricing Summary

cursor-talk-to-figma-mcp is free and open-source software under the MIT license. It runs as a local bridge between Cursor/Claude and Figma; standard Figma account permissions and AI model token consumption apply.

Supported Platforms

MCP server, Figma plugin, WebSocket bridge, Cursor, Claude Code, Bun/Node local development.

Explore categories, tags & use cases

Side-by-Side Comparisons

Figma MCP Server logo
Figma MCP Server
vs
cursor-talk-to-figma-mcp Grab parent mark
Talk to Figma MCP

Figma MCP Server vs Talk to Figma MCP: Official Workflow or Community Control?

Figma's official MCP server and Talk to Figma MCP both connect agents to design files, but their trust, setup, and automation models differ. Figma MCP Server serves as the more practical daily standard for supported design-to-code teams; Talk to Figma MCP is compelling when a local, open-source plugin bridge and granular community tools matter more.

Figma MCP ServerTalk to Figma MCP
cursor-talk-to-figma-mcp Grab parent mark
Talk to Figma MCP
vs
Figma Context MCP logo
Figma Context MCP

Talk to Figma MCP vs Figma Context MCP — Read/Write Automation vs Read-Only Design Context

Talk to Figma MCP and Figma Context MCP both connect Figma to AI coding agents through MCP, but they solve different risk profiles. Figma Context MCP is the safer default when developers only need structured layout context from a Figma file. Talk to Figma MCP is better when a team intentionally wants a local agent bridge that can read selections and write changes back into Figma through a plugin and WebSocket flow.

Talk to Figma MCPFigma Context MCP

Community experience

Sources & verification

Sources checked
Content verified

Verification dates are editorial checks. Routine CMS saves and automatic updatedAt timestamps do not advance them.

optional / review badge

Optional image for a README or docs page. The snippet links to this review. No link is required.

Talk to Figma MCP reviewed on aicoolies
[![Talk to Figma MCP reviewed on aicoolies](https://aicoolies.com/api/badge/tool/cursor-talk-to-figma-mcp.svg)](https://aicoolies.com/reviews/cursor-talk-to-figma-mcp-review)

FAQ

What is Talk to Figma MCP?

Talk to Figma MCP is an MIT-licensed bridge from Grab that connects Cursor, Claude Code, and other MCP-capable agents to Figma through a local MCP server, WebSocket bridge, and Figma plugin. Unlike read-only context servers, it can inspect selections, create or modify nodes, update text in bulk, and automate design operations, so teams should review permissions before enabling write access.

Is Talk to Figma MCP free?

Yes — Talk to Figma MCP is open source and free to use. cursor-talk-to-figma-mcp is free and open-source software under the MIT license. It runs as a local bridge between Cursor/Claude and Figma; standard Figma account permissions and AI model token consumption apply.

Is Talk to Figma MCP open source?

Yes — Talk to Figma MCP is open source.

Is Talk to Figma MCP still maintained?

Yes — Talk to Figma MCP is active. Its listing was last verified on August 26, 2026.

How does Talk to Figma MCP score in our review?

The published editorial review lists Talk to Figma MCP at 81/100 overall across speed, privacy, and developer experience. Check the review's evidence status and test metadata for its verification level.