Framelink MCP for Figma
Framelink MCP for Figma is an MCP server published by Framelink, verified on MCP revision 2025-11-25; support for the current revision (2026-07-28) is not yet confirmed. It is a community implementation. Last verified 2026-08-20.
Does Framelink MCP for Figma support the current MCP specification (2026-07-28)?
Not yet confirmed. Framelink MCP for Figma is verified on revision 2025-11-25; we have not confirmed support for the current revision (2026-07-28) as of 2026-08-20.
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-20).
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.
Does Framelink MCP for Figma support MCP revision 2025-11-25?
Yes. Framelink MCP for Figma supports MCP revision 2025-11-25 (checked 2026-08-20).
Does Framelink MCP for Figma support MCP revision 2026-07-28?
No. Framelink MCP for Figma was checked against MCP revision 2026-07-28 and does not support it (checked 2026-08-20).
When were Framelink MCP for Figma's facts last verified?
2026-08-20. 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.
Which MCP spec revisions does Framelink MCP for Figma support?
Framelink MCP for Figma has 2 verified spec-support records. Each row lists the revision, the verified status, the evidence URL, and the date that fact was last checked.
| Spec revision | Status | Last checked | Evidence |
|---|---|---|---|
| MCP 2025-11-25 | Supported | Source | |
| MCP 2026-07-28 | Not supported | Source |
How widely adopted is Framelink MCP for Figma?
Ranked #11 in The MCP 500 with Adoption Index 71.84 (snapshot , methodology v1).
| Measurement | Value | Source |
|---|---|---|
| Official MCP Registry | yes | API · |
| Docker MCP Catalog | no | API · |
| npm downloads (weekly) | 55,619 | API · |
| GitHub stars | 15,863 | API · |
| GitHub forks | 1,260 | API · |
| Last push | 2026-09-15T07:13:43Z | API · |
| Repository archived | no | API · |
Repository and package signals for Framelink MCP for Figma
Measured directly from the source registries, not asserted from a document. Each figure carries the date it was read; none of it affects the verified spec status above.
Repository as of
- Created
- Open issues
- 25
- Primary language
- TypeScript
- License (repository)
- MIT
- Continuous integration
- Present
- Tests
- Present
- Security policy
- Present
Declared topics: ai, cursor, figma, mcp, typescript — author-declared on the repository, not our taxonomy.
Package (npm) as of
- Latest version
0.13.2- Last published
- First published
- Releases
- 51
- License (package)
- MIT
- Maintainers
- 1
- Direct dependencies
- 16
- Unpacked size
- 90 KB
- Registry signature
- Signed
- Build provenance
- Attested
How was this verified, and what are the sources?
Verified · method: sdk-protocol-constant
· 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
- npm registry metadata for figma-developer-mcp at published version 0.13.2, retrieved 2026-08-20 - declares a dependency on @modelcontextprotocol/sdk, which resolves to @modelcontextprotocol/sdk@1.29.0 - accessed
- Published artifact of @modelcontextprotocol/sdk@1.29.0, retrieved 2026-08-20 - the artifact declares LATEST_PROTOCOL_VERSION 2025-11-25 and carries no 2026-07-28 implementation. Read from the artifact itself, not from release notes - accessed