Figma MCP Bridge
figma-mcp-bridge
A Figma Desktop plugin and an MCP server: an agent reads tokens, styles and components without the Figma REST API and its limits. Not from Figma
- 745 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- An unofficial project, version 0.0.x
- The desktop Figma is needed
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add mcp/figma-mcp-bridgeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- An unofficial project, version 0.0.x
- The desktop Figma is needed
This is third-party code. Review the repository files before installing.
What it does
Figma MCP Bridge is a Figma Desktop plugin and an MCP server that pass the open document's data to an agent bypassing the Figma REST API. Per the README it works around API limits: free accounts, by the author's words, get 6 requests per month. The agent reads variables, styles and components, several files can be connected at once and the write tools are enabled separately. Server: `npx -y @gethopp/figma-mcp-bridge`. It needs the desktop Figma for macOS or Windows. Version 0.0.23 from 04.10.2026, MIT license.
Who it is for. For developers and designers on a free Figma plan who need layout tokens and components in an agent without hitting API limits.
Good fit when
- You need to move Figma tokens and components into code
- The Figma REST API limits get in the way
- You need to read several Figma files at once
Not a fit when
- You work in the browser version of Figma: development plugins cannot be imported there
- You need an official Figma tool: the project is unofficial
Example request
Read the color and spacing variables of the open file through Figma MCP Bridge and build a CSS tokens file from themMCP
- Transport
- stdio
- Authentication
- not required
Limitations
The project is not from Figma. It needs the desktop app and the browser version does not accept development plugins. Version 0.0.x, behavior may change. The write tools are enabled separately: give them to an agent on a copy of the file. Access is extended: the agent reads your document.
How to disable. Remove the skill from the agent's folder or the plugin through the plugin manager.
FAQ
Why is the bridge needed?
So an agent reads Figma data through a plugin and not through the REST API with its limits.
Does it work in the browser?
No, the desktop Figma is needed: the browser version does not import development plugins.
Is it from Figma?
No, it is a separate project.
Discussion
No questions or reviews yet.
Related
MCP serversMCP bridge between an agent (Cursor, Claude Code, Codex) and Figma for reading designs and editing them on the canvas
An MCP server that lets an agent read and edit Figma designs: colors, typography, components and export
An MCP server that gives the agent simplified Figma layout data from a link so it can build the screen more accurately than from a screenshot
A free, two-way Figma MCP server: turns designs into framework-aware code and pushes code back to the canvas
Figma Console MCP
figma-console-mcp
A two-way Figma MCP server for design systems: reads and writes variables, components and styles and syncs tokens with code
Figma's official MCP server: code from a selected frame, design system variables and components, and writing designs to the canvas
Comparison with similar tools
Entries that share the main search query, and how they differ.
| Entry | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Figma MCP Bridge (this entry) | no | not required | 745 | |
| figma-use | no | 609 | writing to Figma from a CLI and JSX, an unofficial route | |
| TemPad Dev | no | 593 | Figma layouts into JSX and Vue code with Tailwind |
README in short
The README describes a plugin and an MCP server for reading Figma data without REST API limits with the write tools separate. Version 0.0.23, MIT license.