MCP
Figma Context MCP
An MCP server that gives coding agents such as Cursor access to Figma layout information.
GLips/Figma-Context-MCP is an MIT-licensed MCP server that gives coding agents such as Cursor Figma layout information, so an implementation can follow the file instead of guessing spacing from a screenshot.
Grant access only to the files the task needs. Do not mint a team-wide Figma token with the widest scope. A design file may hold unreleased product. Avoid pasting the whole file into a chat log or the repository.
Mentioned by:
- @HermesWatcher mentioned this project on 27 October 2026 (1149 likes and 126 reposts, captured 15 November 2026).
- @stewy0x mentioned this project on 14 November 2026 (52 likes and 7 reposts, captured 15 November 2026).
This page is a guide, not the original text.
What problem it solves
Figma Context MCP (repository GLips/Figma-Context-MCP, npm package figma-developer-mcp, product name Framelink MCP for Figma) gives a coding agent layout and style data from a Figma file, instead of leaving it to guess spacing from a screenshot. The server simplifies the Figma API response before the model sees it.
There are two official tools: get_figma_data reads the design structure, and download_figma_images saves image assets into your project. Agents typically call them after you paste a Figma link.
Who it is for
It is for people who implement UI from a design file in Cursor, Claude Code, Claude Desktop, VS Code, or another MCP client. The project is MIT-licensed. You need a Figma personal access token before you start.
The token is tied to your Figma account and can read any file that account can open. Grant only the files the task needs. Do not mint a team-wide token with the widest scopes and hand it to an agent. A design file may hold unreleased product work. Avoid pasting the whole file into a repository or a long-lived chat log.
How to install it
Checked on 15 November 2026 (Asia/Shanghai) against the repository README and the Framelink Quickstart.
First create a personal access token in Figma: account settings → Security → Personal access tokens. Official docs say a token created with the default options often lacks the scopes this MCP needs. The Quickstart lists a full set to tick. The Authentication page says the one scope strictly required is file_content:read, and that file_dev_resources:read should be added if you hit the matching 403. Figma shows the token once. Do not commit it to a public repository.
On macOS or Linux, most clients accept this config (replace YOUR-KEY with the token):
{
"mcpServers": {
"Framelink_Figma_MCP": {
"command": "npx",
"args": ["-y", "figma-developer-mcp", "--figma-api-key=YOUR-KEY", "--stdio"]
}
}
}On Windows, official docs note that npx is a batch file most MCP clients cannot launch directly. Use cmd instead:
{
"mcpServers": {
"Framelink_Figma_MCP": {
"command": "cmd",
"args": ["/c", "npx", "-y", "figma-developer-mcp", "--figma-api-key=YOUR-KEY", "--stdio"]
}
}
}You can also set FIGMA_API_KEY in the environment instead of passing the token in args.
Claude Code
claude mcp add Framelink_Figma_MCP -- npx -y figma-developer-mcp --figma-api-key=YOUR-KEY --stdioCursor
Go to Settings → Cursor Settings → MCP → Add new global MCP server, or paste the JSON above into ~/.cursor/mcp.json. For a single project, you can put .cursor/mcp.json in the project folder.
Claude Desktop
Open Settings → Developer, edit claude_desktop_config.json, and add the same mcpServers block (on Windows, use the official cmd form). The troubleshooting guide also covers Claude Desktop picking the wrong Node.js version when you use a version manager such as NVM.
A worked example
The prompt below is a check written for this page, not a canned official phrase. It was not run in this review, so the page does not invent layout data or generated code.
- Finish the install and confirm
get_figma_datais visible in your client. - In Figma, right-click a single frame or group and choose Copy/Paste as → Copy link to selection. Official docs recommend working on one section at a time; a whole file can overwhelm the model.
- Paste the link and send:
Implement this Figma frame. First call get_figma_data; do not invent spacing from a screenshot. - Based on official tool descriptions, the agent should call
get_figma_datawith the link you provided. Check spacing, type, and color against the file yourself. Do not treat a first draft as a verified match.
Common pitfalls
- A 403 whose body contains
Invalid scope(s). Official troubleshooting says this usually means the PAT was created without scopes such asfile_content:read. Generate a new token from the Quickstart list instead of retrying the same one. - Figma API rate limits (
429). Official docs say the limit comes from Figma, not from this MCP: about 6 requests per month on the free plan, and 10 requests per minute as the starting point on paid plans (including Dev Seats) for the endpoints this server uses. The file owner’s plan also matters. See Troubleshooting and Figma’s rate-limit documentation. Cannot find module. Official docs suggest closing the client, runningnpx clear-npx-cache, and opening the client again.- Image downloads rejected because of the path. Files can only be written inside the directory set by
--image-dir(the server’s startup directory by default). Many MCP clients start the server somewhere other than your project root, so you may need to set--image-direxplicitly. - Launching
npxdirectly as the command on Windows. Use the officialcmd /c npx ...form instead.
FAQ
Do I have to use a personal access token?
That is the official recommendation for most people. The server can also take an access token you already obtained from a Figma OAuth app, but it does not run the OAuth flow or refresh tokens. When the token expires, requests fail until you supply a new one. HTTP mode can also accept a token per request. stdio mode needs a token at startup.
Is a free Figma account enough?
You can create a token and call the API, but the free-plan rate limit is tight. Official troubleshooting describes it as about 6 requests per month. If you will read design files often, check Figma’s current plan limits instead of assuming you can refresh freely.
Why is the server connected, but tool calls still return 403?
Look at the err field in the error body. Official docs treat Invalid scope(s), Invalid token, Token expired, and File not exportable as separate cases. The file must also belong to the account behind the token, or be shared with it. Issue #358 reported a similar “connected, but 403 on the call” case (that issue is now closed).
Can I implement a whole page in one go?
You can try, but the official Quickstart recommends one section at a time. Complex files can still overflow the model’s context. A link to a single frame is usually safer than a link to the entire file.
Should the token go in the command arguments?
Both --figma-api-key and FIGMA_API_KEY are officially supported. If you put the token in a user-level config, keep it out of git. For a shared HTTP deployment, per-request tokens are a better fit than one service-account token used by everyone.
Sources and license
GLips/Figma-Context-MCP is licensed under MIT. This page follows the README, Quickstart, Authentication, Tools, and Troubleshooting as of 15 November 2026, rewritten for CQBase — Context & Query Base. If the install commands or token scopes change, follow those official pages.
In this category
- MCP
Awesome MCP Servers
The MCP server list people most often cite, under MIT.
punkpeye - MCP
MCP reference servers
Reference servers from the protocol organization, for seeing the smallest shape of an MCP server.
modelcontextprotocol - MCP
Context7
An MCP that feeds current library docs to an agent so it writes against the API you have.
upstash