Get Crossfade
  1. Crossfade
  2. Guides

Figma MCP alternatives: seven ways to connect an agent to Figma

By Sabarish Sanjay, maker of Crossfade · Updated

Figma's own MCP server is the obvious way to connect an agent, but it isn't the only one. If you've hit a rate limit, need local fonts or just want your agent to work in the file you have open, these are the real options.

A note on bias: I make Crossfade, one of the options here, and it's the only paid one. I've tried to be fair: every open-source tool below is described from its own README, and the stars and dates are from GitHub on 7 November 2026. Check them yourself before you install anything, because these tools run on your machine.

The short version

ToolBest forEdits the canvasCost
Figma’s MCP serverCode Connect, working with Figma closedYes, on the remote serverIncluded with plans, paid writes planned
FramelinkTurning designs into codeBuilt for readingFree, MIT
TalkToFigmaA free, widely used plugin bridgeYesFree, MIT
Claude Talk to FigmaA free bridge built around ClaudeYesFree, MIT
Figma Console MCPDesign systems and token syncYesFree, MIT
figma-cliDescribing what you want in plain languageYesFree, MIT
CrossfadePolished setup, seeing what your agents doYes$19 once

Figma’s MCP server

The official route, and the one to pick if you need Code Connect, FigJam, Slides, or to work without the app open. The remote server handles writing, and the desktop server is read-only. Reads are limited by plan and seat, and writing outside your drafts needs a Full seat. Writing is free during the beta and will become usage-based.

Framelink

GLips/Figma-Context-MCP has about 16,000 stars and gives coding agents layout information from your files, using a Figma access token you create. It's a strong choice if you're going from design to code and don't need the agent to change the file.

TalkToFigma

grab/cursor-talk-to-figma-mcp has about 7,000 stars. It pairs a Figma plugin with a local WebSocket server that you start yourself, and supports Cursor, Claude Code and Codex. If you're comfortable in a terminal and want something free, start here.

Claude Talk to Figma

arinspunk/claude-talk-to-figma-mcp has about 700 stars and works the same way, with a plugin and a local WebSocket. Its README says it works with any Figma account, including free ones. Its last code push was in April 2026, so check it's still active.

Figma Console MCP

southleft/figma-console-mcp has about 3,200 stars and is the most design-system focused. It can write to Figma, sync tokens both ways, compare components with code and more. Choose it if your work is mostly about a design system.

figma-cli

silships/figma-cli has about 1,100 stars. You open Claude in the project and describe what you want, and it builds in Figma Desktop, locally and with no API key.

Crossfade

Crossfade is my own, and costs $19 once. Like the plugin-based tools above, it works in your open file on your machine, so nothing is counted. What you're paying for is the finish: you paste one prompt and your agent sets up the bridge, the plugin shows each agent on a live wire with the direction data is moving, every run is a single undo step, and it can save a named version before a big change. It's built and tested on Claude Code. Codex and Cursor connect the same way but haven't been tested yet.

How to choose

Common questions

Is there a free alternative to Figma's MCP server?

Yes, several. Framelink, TalkToFigma, Claude Talk to Figma, Figma Console MCP and figma-cli are all open source under the MIT licence.

Which Figma MCP alternatives can edit designs?

TalkToFigma, Claude Talk to Figma, Figma Console MCP, figma-cli and Crossfade all work through the Figma desktop app and change the file. Framelink is built to read design data for coding.

Do I still need Figma's server if I use one of these?

Only if you need something it does uniquely, like Code Connect. They don't clash, so plenty of people can keep both.

Sources

Keep reading