20 Best Figma MCP Servers, Compared (October 2026)
The short answer
For most developers, reach for figma-console-mcp: it is a Community favourite with 2,507 GitHub stars, 11,004 npm downloads in a typical week, 185 stars gained per 30 days, a commit 16 days ago, and 38 commits in the last 12 weeks. It documents extraction, creation, debugging, and bidirectional token sync, so it fits design-system parity as well as general Figma access. If you are on a free Figma plan and keep hitting API limits, Figma MCP Bridge (gethopp/figma-mcp-bridge) is the better answer because it streams live document data from a local plugin over WebSocket instead of the standard cloud API, and it had a commit 7 days ago with 16 commits in the last 12 weeks.
Whichever you choose, give it the narrowest access that still works (a read-only credential, a replica, a scratch account), and widen it only once you have watched what your agent actually asks for.
Glama operates the MCP registry these numbers are measured from, and sells MCP hosting and a gateway. No position on this page is paid for. How the registry is built.
Quick picks
- 1figma-console-mcp : Design-system teams syncing tokens both ways between Figma variables and code: the server documents bidirectional token export/import, variable management, and deterministic design-code parity checks.
- 2Figma MCP Bridge : Figma free accounts hitting monthly API limits: it streams live document data from a local plugin to AI tools over WebSocket, bypassing Figma's API.
- 3figma-ui-mcp : For bidirectional Figma work in Figma Desktop: it exposes figma_write to draw UI and figma_read to extract designs over localhost.
- 4Figma MCP Server : For Cursor users implementing Figma file, frame, or group designs: it provides simplified layout and styling data from the Figma API for code generation.
- 5Figma MCP Server : Developers generating code from Figma frames in VS Code, Cursor, or Claude Code: it documents design context, Code Connect, and remote canvas writes through MCP.
Which one, for your situation
| Your situation | What to use |
|---|---|
| I want one Figma MCP for general extraction, creation, and debugging | figma-console-mcp is a general fit, with 2,507 GitHub stars, 11,004 npm downloads in a typical week, and a commit 16 days ago. |
| I use Cursor and need Figma design context for code generation | Figma MCP Server (figma/mcp-server-guide) documents code generation, Code Connect, and canvas writes, and it had a commit 3 days ago with 23 commits in the last 12 weeks. |
| I am on a free Figma plan hitting API limits | Figma MCP Bridge (gethopp/figma-mcp-bridge) bypasses Figma's free API rate limits by streaming live document data over a local WebSocket, and it had a commit 7 days ago. |
| I need to draw and edit Figma designs from an agent | figwright exposes 112 bidirectional tools for reading designs and writing frames, text, styles, variables, and components, with 243 stars gained per 30 days and 182 commits in the last 12 weeks. |
| I need Flutter widgets generated from Figma designs | Figma to Flutter MCP Server (mhmzdev/figma-flutter-mcp) is the match for Flutter guidance, though it had a commit 234 days ago and 0 commits in the last 12 weeks. |
| I need design system reconciliation across Figma, code, and tokens | Primitiv scans Figma, code, Storybook, and token files and serves 9 read-only MCP tools, with a commit 4 days ago and 70 commits in the last 12 weeks. |
Top MCP servers for Figma
| Best for | Profile | ||||||
|---|---|---|---|---|---|---|---|
| 1 | Design-system teams syncing tokens both ways between Figma variables and code: the server documents bidirectional token export/import, variable management, and deterministic design-code parity checks. | Community favourite | 2,507 | +185 | 16 days ago | 89.6 | |
| 2 | Figma free accounts hitting monthly API limits: it streams live document data from a local plugin to AI tools over WebSocket, bypassing Figma's API. | Community favourite | 757 | +124 | 7 days ago | 82.3 | |
| 3 | For bidirectional Figma work in Figma Desktop: it exposes figma_write to draw UI and figma_read to extract designs over localhost. | Community favourite | 264 | +16 | 7 days ago | 78.6 | |
| 4 | For Cursor users implementing Figma file, frame, or group designs: it provides simplified layout and styling data from the Figma API for code generation. | Abandoned but popular | 15,999 | +121 | 116 days ago | 78.5 | |
| 5 | Developers generating code from Figma frames in VS Code, Cursor, or Claude Code: it documents design context, Code Connect, and remote canvas writes through MCP. | Community favourite | 2,076 | +81 | 3 days ago | 75.7 | |
| 6 | For editing Figma designs from Cursor or Claude Code: it exposes 19 MCP tools for reading documents, selections, and nodes and modifying design elements. | Abandoned but popular | 7,061 | +31 | 84 days ago | 74.2 | |
| 7 | Free Figma accounts needing AI-driven design edits and audits: it exposes 92 read and write tools and works without a Dev Mode license. | Abandoned but popular | 670 | +10 | 183 days ago | 64.2 | |
| 8 | Agents drawing into Figma files: five tools cover read, write, rules, docs and connection diagnostics, with a layout audit for overflow and clipping. | Emerging | 96 | +54 | 30 days ago | 63.3 | |
| 9 | Working on a free Figma plan that keeps hitting REST API limits: it reads and writes live Figma documents through a locally installed Figma plugin instead of the REST API. | Emerging | 66 | +20 | 6 days ago | 59.5 | |
| 10 | Editing a live Figma design file rather than only reading it: a WebSocket bridge to a Figma plugin lets Claude create shapes and modify styles. | Steady | 79 | +6 | 4 days ago | 57.1 | |
| 11 | Flutter developers using Cursor with a Figma API key: the README documents npx stdio setup and extraction of Figma node/screen data for Flutter guidance. | Abandoned but popular | 244 | -1 | 234 days ago | 56.0 | |
| 12 | Figma free-tier users needing an agent to read designs and write frames, text, styles, variables, and components: it exposes 112 bidirectional tools. | Community favourite | 1,063 | +243 | 2 days ago | 52.9 | |
| 13 | Generating UI code from Figma links in Cursor: the get_figma_design tool returns CSS-aligned design data with layout, styling, text, and components, plus SVG export. | Steady | 6 | +1 | 51 days ago | 49.2 | |
| 14 | Teams on free Figma accounts hitting API rate limits: it caches fetched file data locally with a configurable TTL before serving it to MCP clients. | Dormant | 79 | +3 | 144 days ago | 45.8 | |
| 15 | Teams reconciling Figma, code, Storybook, and tokens for AI agents: it exposes nine read-only MCP tools for component, token, conflict, and violation context. | Steady | 21 | +2 | 4 days ago | 45.5 | |
| 16 | MCP client users needing Figma REST API access across files, variables, components, comments, webhooks, and library analytics: it exposes each non-deprecated endpoint as a tool. | Steady | 10 | 0 | today | 45.3 | |
| 17 | Design-to-code work from Figma or live URLs: 28 tools normalize either source into one design spec, then verify the built UI against it. | Steady | 80 | -2 | 8 days ago | 44.0 | |
| 18 | Choosing a Figma MCP for token and component extraction without plugin setup: pull_design_system_rest uses the Figma REST API with FIGMA_TOKEN and FIGMA_FILE_KEY. | Steady | 47 | +6 | 21 days ago | 43.7 | |
| 19 | Bulk design edits in a scoped Figma page or frame: it exposes 45 tools, validates every batch item, and refuses edits outside the chosen area. | Steady | 14 | +7 | 76 days ago | 42.9 | |
| 20 | Free Figma account hitting Figma API rate limits while implementing designs in Cursor: it caches Figma file responses on disk via FIGMA_CACHING. | Dormant | 28 | 0 | 117 days ago | 41.3 |
The ranking, with the evidence
Each position is a weighted mean of adoption (40%), maintenance (24%), momentum (14%), tool description quality (13%) and trust (9%), multiplied by three attenuators: how directly the server is about Figma (named for it, declaring it, tagged with it, or merely mentioning it), whether its repository is still moving, and how much independent evidence of adoption it has. Open the score on any entry to see every number, including the ones marked ≈, which were imputed from the median of the other candidates rather than measured. The maintenance grade on each entry is mostly issue responsiveness, release recency and open security alerts rather than commits, so a recent commit beside a low grade is two different measurements rather than a contradiction.
- Abandoned but popular: People use it, but its default branch has stopped moving. Fine to keep running, risky to adopt.
- Community favourite: Widely adopted and still actively maintained.
- Dormant: Neither changing nor widely adopted. Here because it still matches the search.
- Emerging: Small audience, growing quickly, maintained. The bet with the most upside.
- Steady: Maintained, modest audience, no surprises in either direction.
Best for: Design-system teams syncing tokens both ways between Figma variables and code: the server documents bidirectional token export/import, variable management, and deterministic design-code parity checks.
Its README documents a server that connects AI assistants to Figma for design-system extraction, bidirectional token sync, design creation, variable management, visual debugging, accessibility scanning, and design-code parity checks. The codebase-to-design-system extraction path requires NPX or Local Git with Node.js; Remote SSE is read-only, and Cloud Mode omits real-time monitoring and codebase extraction.
GitHub stars2,507Stars / 30 days+185npm / typical week11KPyPI / typical weekno attributed packageTools exposednever inspectedLast commit16 days agoCommits / 12 weeks38Maintenance gradeBTool descriptionsNot gradedScore 89.6: show every number behind it
- Adoption99 / 100 · weight 40%
- GitHub stars85
- npm downloads86
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance95 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence100
- Momentum72 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute92
- npm download trend0
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 89.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 89.6
Best for: Figma free accounts hitting monthly API limits: it streams live document data from a local plugin to AI tools over WebSocket, bypassing Figma's API.
Figma MCP Bridge is a Figma plugin paired with an MCP server that connects over a local WebSocket, and its README documents tools for listing connected files, retrieving document trees, selections, nodes, styles, variables, screenshots, prototype connections, and write tools for text, visibility, and animation. Before choosing it, note that it requires the Figma desktop app on macOS or Windows; the browser version does not support importing development plugins.
GitHub stars757Stars / 30 days+124npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit7 days agoCommits / 12 weeks16Maintenance gradeATool descriptionsNot gradedScore 82.3: show every number behind it
- Adoption72 / 100 · weight 40%
- GitHub stars72
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum94 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute85
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 82.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 82.3
Best for: For bidirectional Figma work in Figma Desktop: it exposes figma_write to draw UI and figma_read to extract designs over localhost.
The server exposes five MCP tools (figma_status, figma_write, figma_read, figma_docs, figma_rules) and bridges an MCP client to a Figma plugin over localhost so assistants can draw on the canvas and read designs back. The main constraint is that Figma Desktop is required: the plugin communicates over localhost, and the web app does not allow localhost network access.
GitHub stars264Stars / 30 days+16npm / typical week200PyPI / typical weekno attributed packageTools exposed5Last commit7 days agoCommits / 12 weeks14Maintenance gradeATool descriptionsAScore 78.6: show every number behind it
- Adoption64 / 100 · weight 40%
- GitHub stars61
- npm downloads24downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum61 / 100 · weight 14%
- Stars gained, relative to size81
- Stars gained, absolute49
- npm download trend40
- Tool quality93 / 100 · weight 13%
- Tool description quality85
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 78.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 78.6
Best for: For Cursor users implementing Figma file, frame, or group designs: it provides simplified layout and styling data from the Figma API for code generation.
Framelink MCP for Figma is an MCP server, distributed as the npx package figma-developer-mcp, that documents a workflow for Cursor and other AI coding tools to read Figma file, frame, or group links and receive simplified layout and styling data from the Figma API. Before choosing it, note that it requires a Figma access token, supplied through --figma-api-key or FIGMA_API_KEY, and its documented configuration runs through npx with --stdio.
GitHub stars15,999Stars / 30 days+121npm / typical week94.6KPyPI / typical weekno attributed packageTools exposednever inspectedLast commit116 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 78.5: show every number behind it
- Adoption100 / 100 · weight 40%
- GitHub stars100
- npm downloads100
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance63 / 100 · weight 24%
- Last commit touching this server88dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 3 days ago, which counts every ref; the stored date would have published 3 days ago
- Repository maintenance grade55
- Commit cadence5
- Momentum44 / 100 · weight 14%
- Stars gained, relative to size35
- Stars gained, absolute84
- npm download trend12
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 78.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 78.5
Best for: Developers generating code from Figma frames in VS Code, Cursor, or Claude Code: it documents design context, Code Connect, and remote canvas writes through MCP.
The server connects MCP clients to Figma through the documented HTTP endpoint at https://mcp.figma.com/mcp, with setup instructions for VS Code, Cursor, and Claude Code and documented capabilities including design context extraction, code generation from selected frames, remote canvas writes, Code Connect, and placeholder image generation. Before choosing it, note that rate limits apply to tools that read Figma data, with Starter plan and View or Collab seat users facing monthly call limits, while tools that write to Figma files are exempt.
GitHub stars2,076Stars / 30 days+81npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit3 days agoCommits / 12 weeks23Maintenance gradeBTool descriptionsNot gradedScore 75.7: show every number behind it
- Adoption83 / 100 · weight 40%
- GitHub stars83
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance92 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence85
- Momentum78 / 100 · weight 14%
- Stars gained, relative to size79
- Stars gained, absolute77
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust15 / 100 · weight 9%
- License0
- Published by the vendor it integrates100
- Weighted mean of the five
- 75.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 75.7
Best for: For editing Figma designs from Cursor or Claude Code: it exposes 19 MCP tools for reading documents, selections, and nodes and modifying design elements.
Talk to Figma MCP connects Cursor or Claude Code to Figma through a Figma plugin and a WebSocket server, exposing 19 MCP tools for reading document, selection, and node information and for creating or modifying elements, text, styles, and components, plus exporting nodes as images. It requires Bun, a running WebSocket server, and the Figma plugin connected via join_channel before Cursor can act on a document.
GitHub stars7,061Stars / 30 days+31npm / typical weekdownloads not countedPyPI / typical weekno attributed packageTools exposed19Last commit84 days agoCommits / 12 weeks0the weekly history behind this count has not caught up with the commit aboveMaintenance gradeFTool descriptionsBScore 74.2: show every number behind it
- Adoption96 / 100 · weight 40%
- GitHub stars96
- npm downloadsnot measurednpm names no repository for cursor-talk-to-figma-mcp, so its downloads cannot be attributed
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance51 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade5
- Commit cadence5
- Momentum41 / 100 · weight 14%
- Stars gained, relative to size27
- Stars gained, absolute61
- npm download trendnot measuredno download history for the selected registry
- Tool quality68 / 100 · weight 13%
- Tool description quality60
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 74.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 74.2
Best for: Free Figma accounts needing AI-driven design edits and audits: it exposes 92 read and write tools and works without a Dev Mode license.
The server exposes 92 tools that read Figma document, selection, node, style, component, and page data and that create or modify elements such as frames, text, rectangles, ellipses, auto layout, colors, and effects. Before choosing it, note that setup requires Node.js, Figma Desktop, a local websocket, and importing the plugin manifest, and its stateful set_current_page command is blocked so creation commands must supply a parentId.
GitHub stars670Stars / 30 days+10npm / typical week329PyPI / typical weekno attributed packageTools exposed92Last commit183 days agoCommits / 12 weeks0Maintenance gradeDTool descriptionsCScore 64.2: show every number behind it
- Adoption79 / 100 · weight 40%
- GitHub stars71
- npm downloads54
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance46 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade30
- Commit cadence5
- Momentum41 / 100 · weight 14%
- Stars gained, relative to size45
- Stars gained, absolute42
- npm download trend33
- Tool quality53 / 100 · weight 13%
- Tool description quality45
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 64.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 64.2
Best for: Agents drawing into Figma files: five tools cover read, write, rules, docs and connection diagnostics, with a layout audit for overflow and clipping.
Reqwise Figma MCP pairs a local MCP server with a companion Figma plugin so an agent can inspect and draw on a Figma canvas by executing JavaScript against a figma.* proxy, exposing five tools: figma_status, figma_read, figma_write, figma_rules and figma_docs. Its README states that it assumes the companion plugin is installed and running locally, and that features such as components, design-system generation, BPMN and accessibility audits sit behind the Pro edition rather than the free one.
GitHub stars96Stars / 30 days+54npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed5Last commit30 days agoCommits / 12 weeks8Maintenance gradeBTool descriptionsAScore 63.3: show every number behind it
- Adoption50 / 100 · weight 40%
- GitHub stars50
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance88 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence65
- Momentum88 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute70
- npm download trendnot measuredno download history for the selected registry
- Tool quality93 / 100 · weight 13%
- Tool description quality85
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 74.5
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 63.3
Best for: Working on a free Figma plan that keeps hitting REST API limits: it reads and writes live Figma documents through a locally installed Figma plugin instead of the REST API.
figma-mcp-rust carries Figma document operations to an AI tool as MCP tools over a plugin bridge: creating and modifying nodes, setting fills, strokes and auto-layout, managing styles and prototype reactions, and deleting layers, with no Figma API token involved. Choosing it means importing the project's Figma plugin from its release manifest into Figma Desktop and running that plugin inside the target file, because every call travels over the bridge rather than an authenticated API.
GitHub stars66Stars / 30 days+20npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposednever inspectedLast commit6 days agoCommits / 12 weeks15Maintenance gradeATool descriptionsNot gradedScore 59.5: show every number behind it
- Adoption46 / 100 · weight 40%
- GitHub stars46
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum81 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute53
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 70.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 59.5
Best for: Editing a live Figma design file rather than only reading it: a WebSocket bridge to a Figma plugin lets Claude create shapes and modify styles.
Figma MCP Bridge runs a Node.js MCP server that talks stdio to Claude and WebSocket to a Figma plugin, exposing read and mutation tools for Figma and FigJam documents, including node queries, shape creation, style and component edits, and asset export. It assumes the Figma desktop app, Node.js 18+, and a plugin imported manually from the manifest, and since Dev Mode documents are read-only there, every mutation tool returns a READ_ONLY_EDITOR error and editing requires an editor seat in the Design editor.
GitHub stars79Stars / 30 days+6npm / typical week42PyPI / typical weekno attributed packageTools exposednever inspectedLast commit4 days agoCommits / 12 weeks24Maintenance gradeATool descriptionsNot gradedScore 57.1: show every number behind it
- Adoption53 / 100 · weight 40%
- GitHub stars48
- npm downloads35
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance97 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence85
- Momentum40 / 100 · weight 14%
- Stars gained, relative to size65
- Stars gained, absolute33
- npm download trend5
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 67.2
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 57.1
Best for: Flutter developers using Cursor with a Figma API key: the README documents npx stdio setup and extraction of Figma node/screen data for Flutter guidance.
The README documents installing the npm package figma-flutter-mcp through an npx command in Cursor's MCP settings with a Figma API key, and says it extracts Figma component and screen data to guide Flutter widget and screen implementation. Before choosing it, note that it requires a Figma access token and the README says it does not generate actual Flutter code files or screens, leaving code creation to the AI agent.
GitHub stars244Stars / 30 days-1npm / typical week35PyPI / typical weekno attributed packageTools exposednever inspectedLast commit234 days agoCommits / 12 weeks0Maintenance gradeBTool descriptionsNot gradedScore 56.0: show every number behind it
- Adoption62 / 100 · weight 40%
- GitHub stars60
- npm downloads17downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance58 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade80
- Commit cadence5
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend0
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 56.0
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 56.0
Best for: Figma free-tier users needing an agent to read designs and write frames, text, styles, variables, and components: it exposes 112 bidirectional tools.
Figwright connects an MCP client to a Figma plugin over a local WebSocket relay and exposes 112 tools for reading and writing Figma files, covering selection and node inspection, styles, variables, components, screenshots, PDF and video export, and canvas edits such as frames and text. Before choosing it, note that it requires the Figma desktop app to import the plugin, and the plugin is not yet on the Figma Community marketplace.
GitHub stars1,063Stars / 30 days+243npm / typical weekShips no npm packagePyPI / typical weekno attributed packageTools exposed112Last commit2 days agoCommits / 12 weeks182Maintenance gradeATool descriptionsAScore 52.9: show every number behind it
- Adoption76 / 100 · weight 40%
- GitHub stars76
- npm downloadsnot measuredno npm package
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum99 / 100 · weight 14%
- Stars gained, relative to size100
- Stars gained, absolute96
- npm download trendnot measuredno download history for the selected registry
- Tool quality85 / 100 · weight 13%
- Tool description quality77
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 88.2
- × relevance: the keyword is tagged here
- 0.60
- × continuity: actively changing
- 1.00
- × evidence: widely adopted
- 1.00
- Composite score
- 52.9
Best for: Generating UI code from Figma links in Cursor: the get_figma_design tool returns CSS-aligned design data with layout, styling, text, and components, plus SVG export.
The server exposes tools that fetch CSS-aligned, LLM-friendly Figma design data, retrieve image fill URLs, render node images, and read vector node SVGs, and it is configured with a Figma API key via CLI flag or environment variable. Variable resolution, however, requires an Enterprise Figma plan, so non-Enterprise users must set resolveVariables to false.
GitHub stars6Stars / 30 days+1npm / typical week130PyPI / typical weekno attributed packageTools exposednever inspectedLast commit51 days agoCommits / 12 weeks3Maintenance gradeBTool descriptionsNot gradedScore 49.2: show every number behind it
- Adoption48 / 100 · weight 40%
- GitHub stars21
- npm downloads45
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance76 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade80
- Commit cadence40
- Momentum22 / 100 · weight 14%
- Stars gained, relative to size39
- Stars gained, absolute16
- npm download trend0
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 57.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 49.2
Best for: Teams on free Figma accounts hitting API rate limits: it caches fetched file data locally with a configurable TTL before serving it to MCP clients.
Figma-Context-MCP-Cached documents tools for preparing a Figma file, fetching its design data, and inspecting or cleaning the local cache (figma_prepare_file, get_figma_data, list_cache, cleanup_cache). It requires a Figma personal access token at launch, and within the configured TTL it can return cached design data that no longer matches a file still under revision, so the README recommends enabling the cache only once a design is settled.
GitHub stars79Stars / 30 days+3npm / typical weekdownloads not countedPyPI / typical weekno attributed packageTools exposednever inspectedLast commit144 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 45.8: show every number behind it
- Adoption48 / 100 · weight 40%
- GitHub stars48
- npm downloadsnot measurednpm publishes @pactortester/figma-mcp-cached from Pactortester/Figma-Context-MCP-Cached
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance52 / 100 · weight 24%
- Last commit touching this server68
- Repository maintenance grade55
- Commit cadence5
- Momentum37 / 100 · weight 14%
- Stars gained, relative to size46
- Stars gained, absolute24
- npm download trendnot measuredno download history for the selected registry
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 53.9
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 45.8
Best for: Teams reconciling Figma, code, Storybook, and tokens for AI agents: it exposes nine read-only MCP tools for component, token, conflict, and violation context.
Primitiv builds a local design contract from Figma, code, Storybook, and token files and serves it to MCP-compatible agents through nine read-only tools covering component catalogs, design context, tokens, conflicts, inferred rules, and violations. Before choosing it, keep the MCP configuration at project level, because the README warns that a global configuration can serve the wrong project's contract when switching repositories.
GitHub stars21Stars / 30 days+2npm / typical week112PyPI / typical weekno attributed packageTools exposed9Last commit4 days agoCommits / 12 weeks70Maintenance gradeATool descriptionsAScore 45.5: show every number behind it
- Adoption49 / 100 · weight 40%
- GitHub stars34
- npm downloads44
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum36 / 100 · weight 14%
- Stars gained, relative to size46
- Stars gained, absolute20
- npm download trend36
- Tool quality85 / 100 · weight 13%
- Tool description quality77
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 68.6
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 45.5
Best for: MCP client users needing Figma REST API access across files, variables, components, comments, webhooks, and library analytics: it exposes each non-deprecated endpoint as a tool.
It is a stdio MCP server that maps non-deprecated Figma REST API endpoints to self-describing tools, auto-discovered from tools/figma at startup, covering files and nodes, variables, components and styles, comments, folders, users, dev resources, webhooks, library analytics, Enterprise activity logs, developer logs and AI usage, embeds, and payments. Before choosing it, note that it requires Bun, is launched with bunx rather than npx because Node is not supported, needs a Figma personal access token in FIGMA_API_KEY, and that some tools, including variables and library analytics, need higher Figma plan tiers.
GitHub stars10Stars / 30 days0npm / typical week1.8KPyPI / typical weekno attributed packageTools exposednever inspectedLast committodayCommits / 12 weeks46Maintenance gradeATool descriptionsNot gradedScore 45.3: show every number behind it
- Adoption55 / 100 · weight 40%
- GitHub stars26
- npm downloads51downloads capped: not corroborated by repository audience
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum11 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend45
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 64.7
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 45.3
- 17
Best for: Design-to-code work from Figma or live URLs: 28 tools normalize either source into one design spec, then verify the built UI against it.
Plumb exposes 28 tools that read a Figma screen, a saved .fig file, or a live webpage into a normalized Plumb Design Spec (deduplicated tokens plus a CSS-shaped node tree), generate React from it, and run a separate write direction that builds prompts and briefs back into Figma. Reads and writes against a live Figma file depend on a paired Figma desktop plugin, so setup is not purely a standalone install; the .fig and webpage paths work without a Figma connection.
GitHub stars80Stars / 30 days-2npm / typical week84PyPI / typical weekno attributed packageTools exposed28Last commit8 days agoCommits / 12 weeks63Maintenance gradeATool descriptionsAScore 44.0: show every number behind it
- Adoption51 / 100 · weight 40%
- GitHub stars48
- npm downloads21downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance100 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade100
- Commit cadence100
- Momentum5 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend19
- Tool quality96 / 100 · weight 13%
- Tool description quality88
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 66.4
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 44.0
Best for: Choosing a Figma MCP for token and component extraction without plugin setup: pull_design_system_rest uses the Figma REST API with FIGMA_TOKEN and FIGMA_FILE_KEY.
Memoire exposes 50 tools for design-system work: pulling tokens and components from Figma or Penpot, extracting tokens from a URL, generating React and shadcn/ui components from saved specs, running WCAG audits, and syncing tokens bidirectionally. The REST Figma pull requires FIGMA_TOKEN and FIGMA_FILE_KEY, and bridge-based tools such as pull_design_system, capture_screenshot, and get_selection require a running Figma bridge with a connected plugin.
GitHub stars47Stars / 30 days+6npm / typical week224PyPI / typical weekno attributed packageTools exposed50Last commit21 days agoCommits / 12 weeks378Maintenance gradeBTool descriptionsAScore 43.7: show every number behind it
- Adoption46 / 100 · weight 40%
- GitHub stars42
- npm downloads25downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance95 / 100 · weight 24%
- Last commit touching this server100
- Repository maintenance grade80
- Commit cadence100
- Momentum43 / 100 · weight 14%
- Stars gained, relative to size70
- Stars gained, absolute33
- npm download trend5
- Tool quality76 / 100 · weight 13%
- Tool description quality68
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 65.9
- × relevance: the keyword is declared here
- 0.78
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 43.7
Best for: Bulk design edits in a scoped Figma page or frame: it exposes 45 tools, validates every batch item, and refuses edits outside the chosen area.
Figma Edit MCP connects AI assistants to Figma through MCP and exposes tools for page and node inspection, creation, transformation, styling, components, variables, text, and exports. Before choosing it, note that edits are confined to one page or frame selected at connection, and editing variables or styles requires separate permission checkboxes that are off by default.
GitHub stars14Stars / 30 days+7npm / typical week91PyPI / typical weekno attributed packageTools exposed45Last commit76 days agoCommits / 12 weeks43Maintenance gradeATool descriptionsAScore 42.9: show every number behind it
- Adoption33 / 100 · weight 40%
- GitHub stars29
- npm downloads21downloads show none of the weekday rhythm human traffic has; halved
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance93 / 100 · weight 24%
- Last commit touching this server88dated from the last commit on the default branch, re-read from GitHub at publication; github.com shows a push 0 days ago, which counts every ref; the stored date would have published 25 days ago
- Repository maintenance grade100
- Commit cadence100
- Momentum51 / 100 · weight 14%
- Stars gained, relative to size85
- Stars gained, absolute36
- npm download trend7
- Tool quality76 / 100 · weight 13%
- Tool description quality68
- Built and inspected by Glama100
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 61.3
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: small audience
- 0.70
- Composite score
- 42.9
Best for: Free Figma account hitting Figma API rate limits while implementing designs in Cursor: it caches Figma file responses on disk via FIGMA_CACHING.
It runs as an MCP server configured through npx with the figma-developer-mcp-caching-dev-fork package and a Figma API key, giving Cursor and other coding tools access to Figma file data that is simplified into layout and styling information. Before choosing it, note that it is a development fork adding disk caching and requires a Figma access token to fetch design data.
GitHub stars28Stars / 30 days0npm / typical week21PyPI / typical weekno attributed packageTools exposednever inspectedLast commit117 days agoCommits / 12 weeks0Maintenance gradeCTool descriptionsNot gradedScore 41.3: show every number behind it
- Adoption41 / 100 · weight 40%
- GitHub stars37
- npm downloads29
- Used through Glamanot measurednot used through Glama in the last 30 days
- Maintenance63 / 100 · weight 24%
- Last commit touching this server88
- Repository maintenance grade55
- Commit cadence5
- Momentum0 / 100 · weight 14%
- Stars gained, relative to size0
- Stars gained, absolute0
- npm download trend0
- Tool quality≈63 / 100 · weight 13%
- Tool description quality≈63tool descriptions not yet scored
- Built and inspected by Glamanot measurednever built and inspected by Glama
- Trust100 / 100 · weight 9%
- License100
- Published by the vendor it integratesnot measurednot published by the vendor it integrates
- Weighted mean of the five
- 48.6
- × relevance: the keyword is dedicated here
- 1.00
- × continuity: actively changing
- 1.00
- × evidence: modest but real audience
- 0.85
- Composite score
- 41.3
Questions people ask
How do I choose between figma-console-mcp and Figma MCP Server (GLips/Figma-Context-MCP)?
figma-console-mcp is a Community favourite with 2,507 GitHub stars, 11,004 npm downloads in a typical week, a commit 16 days ago, and 38 commits in the last 12 weeks. It documents bidirectional token export and import, variable management, and design-code parity checks. Figma MCP Server (GLips/Figma-Context-MCP) has 15,999 GitHub stars and 94,591 npm downloads in a typical week, but its profile is Abandoned but popular: it had a commit 116 days ago and 0 commits in the last 12 weeks. Pick figma-console-mcp if you want the more recently committed option; consider the GLips server only if you accept its inactivity.
What does Figma MCP Bridge (gethopp/figma-mcp-bridge) require before it will run?
It is a combined Figma plugin and MCP server that streams live document data directly to AI tools via a local WebSocket connection instead of the standard cloud API. It is aimed at Figma free accounts hitting monthly API limits, because it bypasses Figma's API. It had a commit 7 days ago and 16 commits in the last 12 weeks, and no npm package is published for it. The evidence points to a local plugin plus WebSocket setup rather than an npm install.
Does figma-ui-mcp work without Figma Desktop?
No. Its description says it requires Figma Desktop. It is a bidirectional MCP bridge that exposes figma_write to draw UI and figma_read to extract designs over localhost. It exposes 5 tools, has a tool description grade of A, 264 GitHub stars, 200 npm downloads in a typical week, a commit 7 days ago, and 14 commits in the last 12 weeks.
What should I be careful about with Figma MCP Server (GLips/Figma-Context-MCP)?
It is popular, with 15,999 GitHub stars and 94,591 npm downloads in a typical week, but its profile is Abandoned but popular. It had a commit 116 days ago and 0 commits in the last 12 weeks, though its repository is not archived. It is described for Cursor users implementing Figma file, frame, or group designs. If you need recent commits, choose a server with a more recent commit.
Which server is best for free Figma accounts that hit API limits?
Figma MCP Bridge (gethopp/figma-mcp-bridge) is explicitly for Figma free accounts hitting monthly API limits, because it streams live document data from a local plugin to AI tools over WebSocket and bypasses Figma's API. It had a commit 7 days ago and 16 commits in the last 12 weeks. figma-mcp-rust is also for free Figma plans that keep hitting REST API limits: it reads and writes live documents through a local Figma plugin, had a commit 6 days ago, and 15 commits in the last 12 weeks. Figma-Context-MCP-Cached caches fetched file data locally with a configurable TTL, but it had a commit 144 days ago and 0 commits in the last 12 weeks.
Can these servers write to Figma, or do they only read?
Several servers document writes: figma-ui-mcp exposes figma_write to draw UI and figma_read to extract designs; Talk to Figma MCP (grab/cursor-talk-to-figma-mcp) exposes 19 MCP tools for reading and modifying design elements; figwright exposes 112 bidirectional tools; and Figma Edit MCP (neozhehan/figma-edit-mcp) exposes 45 tools for read, create, and modify with validation and scoped edits. figma-console-mcp also documents creation and bidirectional token sync. If writing is your priority, start with one of those servers and check its write tools before pointing an agent at a file. Servers described only for code generation or design context may be sufficient when you only need reads.