Framelink MCP for Figma
Spec Support Unverified Confidence: Good (0.85)Framelink MCP for Figma is an MCP server published by Framelink; its MCP spec-revision support has not been verified yet. It is a community implementation. Last verified 2026-08-14.
Does Framelink MCP for Figma support the current MCP specification (2026-07-28)?
Undetermined. We have not verified which MCP specification revision Framelink MCP for Figma supports (as of 2026-08-14).
Is Framelink MCP for Figma a first-party (official) MCP server?
No. Framelink MCP for Figma is a community-published MCP server from Framelink, not a first-party vendor server (last verified 2026-08-14).
How do I connect to Framelink MCP for Figma?
Framelink MCP for Figma is available via the package npm:figma-developer-mcp, the official MCP Registry under io.github.GLips/Figma-Context-MCP, the source repository at https://github.com/GLips/Figma-Context-MCP. Authentication: none. Transports: stdio.
When were Framelink MCP for Figma's facts last verified?
2026-08-14. Each fact on this page links to the sources used to verify it.
Framelink MCP for Figma (repository name Figma-Context-MCP, npm package
figma-developer-mcp) gives coding agents access to Figma design data.
It calls Figma's REST API with a user-supplied personal access token,
then, per its README, "simplifies and translates the response so only
the most relevant layout and styling information is provided to the
model", aimed at one-shot design implementation in tools like Cursor.
It runs locally over stdio via
npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdio. The MCP
server itself carries no authentication; the Figma token is an upstream
credential for Figma's API. A self-hosted HTTP mode exists behind a
PORT setting, serving /mcp with /sse kept for backward
compatibility.
This is a community server, and the distinction matters because Figma has its own official MCP work: the publisher is independent developer Graham Lipsman (GitHub GLips), and his Framelink product site itself draws the line, comparing "Framelink vs. Figma's Official MCP" as two separate products. Nothing in the repository, npm metadata, or site claims Figma affiliation.
No surface names a supported MCP specification revision; the pinned
@modelcontextprotocol/sdk 1.29.0 dependency is not evidence of revision
support. spec_status is therefore unknown.
How widely adopted is Framelink MCP for Figma?
Ranked #12 in The MCP 500 with Adoption Index 84.85 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| npm downloads (weekly) | 94,922 | API · |
| GitHub stars | 15,659 | API · |
| GitHub forks | 1,241 | API · |
| Last push | 2026-08-07T04:58:42Z | API · |
| Repository archived | no | API · |
How was this verified, and what are the sources?
Verified · method: repo-readme
· confidence 0.85 (Good).
- Official MCP Registry record io.github.GLips/Figma-Context-MCP version 0.13.2 (published 2026-06-18) - npm package figma-developer-mcp, stdio transport, repository GLips/Figma-Context-MCP - accessed
- GLips/Figma-Context-MCP README - titled "Framelink MCP for Figma", "Give your coding agent access to your Figma data"; the server fetches Figma API responses and "simplifies and translates the response so only the most relevant layout and styling information is provided to the model"; run via npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdio; the repo owner is the personal account GLips (Graham Lipsman), not a Figma organization - accessed
- framelink.ai - product site carrying a section titled "Framelink vs. Figma's Official MCP", which positions this server as a distinct product from Figma's own MCP offering; no affiliation with Figma is claimed anywhere on the site or in the README - accessed
- Figma-Context-MCP releases - latest v0.13.2 published 2026-06-18; release notes and CHANGELOG carry feature and fix entries with no spec revision named - accessed
- Staleness re-verification via the GitHub API - repository GLips/Figma-Context-MCP active (pushed 2026-08-07, not archived), latest release v0.13.2 (2026-06-18); entity facts unchanged - accessed