Figma MCP vs Figma Context MCP vs Talk to Figma (2026)

Search for a Figma skill and you'll find a dozen with near-identical descriptions. Three of them account for most real usage, and picking between them is easier than it looks once you notice the split that actually divides them.

Two of these read your Figma file. One writes back into it. That's the fork in the road, and it matters far more than the star counts people compare instead.

Quick Answer

The split nobody mentions

Design-to-code tooling comes in two shapes, and the product pages blur them because "Figma integration" describes both.

Readers pull layout data, component structure, and styles out of Figma and hand them to the agent as context. The output is code. Figma's official server and Figma Context MCP both work this way, and it's the shape that fits most engineering workflows, because the design is the source of truth and code is the artifact.

Writers send instructions into Figma and modify the document. The output is a design. Claude Talk to Figma does this, and it's a much rarer capability with a much narrower use case, mostly bulk edits: rename 200 layers to a convention, apply a token across a file, generate variants from a spec.

Neither is better. They solve opposite problems, and teams that buy the wrong shape conclude the whole category doesn't work.

Comparison table

Figma MCP, the official one

Figma's own server covers design context extraction, component reading, code generation, design tokens, and asset export. Being first-party buys three things the community options can't offer.

Access to internals is the first. When Figma ships a feature such as variables or a new component model, the official integration gets it without a community maintainer reverse-engineering the API surface. Support is the second: it's a supported product, so a broken workflow is a ticket rather than a GitHub issue with no reply. Enterprise procurement is the third, and it's decisive in a lot of organizations. Security review passes a Figma-published tool that will not pass a personal repository, whatever the code quality.

The freemium label is the thing to check before committing. Some capability sits behind paid Figma plan tiers, so confirm what your seat includes rather than assuming feature parity with the free community readers.

Its 52,000 recorded installs are far ahead of anything else in this comparison, which reflects distribution as much as quality. It ships in the places people look first.

Figma Context MCP, the community favorite

GLips' server has 15,609 stars and 1,237 forks, three times the official server's star count, and it's the most actively developed project here with a commit dated 2026-08-07 and 57 new stars in the trailing week.

It was built to give AI coding agents layout information from Figma, originally aimed at Cursor, and it does that one job well. Point it at a frame URL and the agent receives structure, spacing, and styling in a form it can turn into components.

The reason it outgrew the official option is timing and scope. It arrived when the design-to-code gap was most painful, it works with a personal access token and no plan requirements, and it does not try to be a platform. Support across Claude Code, Cursor, and VS Code Copilot means a team on mixed tooling can standardize on it.

Our directory marks it verified and community-reviewed rather than audited. That's the correct read: heavily used, widely forked, not formally security-reviewed by anyone.

Claude Talk to Figma MCP, the write path

At 643 stars this is the smallest project in the comparison, and star count is the wrong lens because it's the only one doing its job.

It lets Claude Desktop, Claude Code, Cursor, and similar tools read, analyze, and modify Figma designs. Modify is the operative word. The agent can change the document.

The workflows where this earns its install are specific and, once you've hit them, memorable:

• Renaming or restructuring layers across a file that grew organically for two years
• Applying a design token or style update across hundreds of instances
• Generating variants from a written spec instead of duplicating and editing by hand
• Auditing a file for inconsistencies and fixing them in the same pass

Two warnings before you install it. Our directory lists it as community trust tier and unreviewed, and it's the one skill here that can alter your design files, so the combination deserves attention. Duplicate the file before the first run, every time.

Second, last recorded update is 2026-04-18 with a flat +2 weekly star growth. Not abandoned, but the slowest-moving project in this comparison, and the one where you should read recent issues before depending on it.

Worth knowing: Cursor Talk to Figma MCP from Grab covers similar ground with 6,957 stars and a more recent 2026-07-26 update. Same read-and-write design, larger backing, and worth evaluating alongside if the write path is what you need.

Installing them

The official server registers with the shortest command:

claude mcp add figma

Community servers register with the repository or package spelled out:

claude mcp add figma-context-mcp -- npx -y GLips/Figma-Context-MCP
claude mcp add claude-talk-to-figma-mcp -- npx -y arinspunk/claude-talk-to-figma-mcp

Check each repository's README before running these. Package names and required flags in this category change between releases, and all three projects publish current instructions on their GitHub page. Every one of them needs a Figma personal access token, generated under Settings, Security, Personal access tokens, and every one of them should get read-only scope unless you specifically need the write path.

Verify registration with:

claude mcp list

Which one to pick

You write code from designs, in a company with procurement. Figma MCP. The support path and the security review are worth more than the feature delta.

You write code from designs, solo or small team. Figma Context MCP. Most active development, no plan requirements, broadest agent support.

You need to change Figma files at scale. Claude Talk to Figma or Grab's Cursor Talk to Figma. Duplicate the file first.

You're not sure yet. Figma Context MCP. It's free, reversible, and the fastest way to find out whether design-to-code fits how you work at all.

Running both readers at once is a mistake worth avoiding. They expose overlapping tools, and the agent picks between them inconsistently, which produces confusing failures that look like model problems rather than configuration problems.

For the broader design tooling picture, see our full list for UX designers.

What none of them fix

Setting expectations honestly, because this is where design-to-code disappoints people.

All three hand the agent a description of a static frame. What they cannot hand it is intent. Why the spacing tightens on mobile, which of two similar buttons is the primary action, what the empty state should say, whether that card is a component or a one-off. A skilled agent guesses well from context and still guesses.

They also don't produce code matching your conventions unless you tell them to. Output arrives in whatever the model considers idiomatic, not in your component library, your utility classes, or your naming. Teams getting real value from these skills pair them with a project-level instruction file describing the codebase, and the pairing does more for output quality than the choice between servers.

Expect a strong first draft that needs your judgment. That's a genuine speedup. It isn't the automated handoff the category markets.

FAQ

Do I need a paid Figma plan?

The community servers work with a free Figma account and a personal access token, which is a large part of their appeal. Figma's official server is listed as freemium, meaning some capability tracks your plan tier, so check what your seat includes before standardizing a team on it. Read access to files you already have permission to open is generally the baseline everywhere.

Can any of these create a Figma file from scratch?

Not meaningfully. The write-capable options modify existing documents, which is a different problem from generating a coherent design from nothing. Tools like Uizard and v0 target generation, and they produce a starting point rather than a production design. For agent workflows, treat Figma as the place designs live and the agent as something that reads or edits them.

Which is safest to install?

Figma MCP, by a clear margin. It's first-party, listed as audited, and carries the accountability of a company shipping it. Figma Context MCP is verified and community-reviewed with heavy adoption, which is meaningful evidence but not a security review. Claude Talk to Figma is community tier and unreviewed, and it can write to your files, so it's the one where duplicating before first use isn't optional caution.

Will these keep my design tokens in sync with code?

Partially, and only in one direction. The official server handles token extraction most completely, so you can pull variables into code. None of them maintains a live two-way sync where a code change updates Figma, and building that reliably needs a dedicated pipeline rather than an agent skill. Treat token extraction as a repeatable manual step you can trigger, not a background process.

Why does the community server have more stars than Figma's own?

Timing, mostly. Figma Context MCP shipped while the design-to-code gap was at its most painful and became the default recommendation in a lot of threads before an official option existed. Stars accumulate and rarely reflect current quality, which is why the last-commit date is the more useful number. On that measure it still leads here, with the most recent commit of the three.