Figma Context MCP
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Description from the maker (original English)
Figma REST API client: files, nodes, images, styles, components, projects and comments.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"designport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/designport",
"mcp"
]
}
}
}Run this in your terminal
claude mcp add designport -- npx -y @reneturcios/designport mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"designport": {
"command": "npx",
"args": [
"-y",
"@reneturcios/designport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"designport": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/designport",
"mcp"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account CloudCorpRecords, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 5 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js, Docker on your computer.
In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.
Let any LLM watch a video locally — and search everything it has ever watched.
Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
designport is a compatible client for the Figma REST API, packaged as an MCP server and a small CLI. It is an independent client for the same public upstream API (https://api.figma.com/v1) — it is not a copy of Figma's hosted OAuth remote MCP server, and none of that server's OAuth tool surface (design context, screenshots, metadata, variable definitions, code-connect, FigJam, or design-system rules) is reproduced here.
The subset covers reading design files: fetch a file or specific nodes, render nodes to images, list image fills, styles, and components, browse team projects and project files, and read or post comments on a file.
Authentication is a Figma personal access token, sent as the X-Figma-Token header. Set FIGMA_PERSONAL_ACCESS_TOKEN before starting the server; a call made without it fails with an error naming the variable. The API base can be overridden with FIGMA_API_BASE.
npx @reneturcios/designport get_file <file_key>
docker run -i ghcr.io/cloudcorprecords/designport
designport get_file <file_key> --depth 2
designport get_file_nodes 1:2,3:4 designport get_images 1:2 --format png --scale 2 designport get_file_styles designport get_team_projects designport list_project_files designport post_comment "Looks good" designport --version
Exit codes: 0 success, 1 API error, 2 usage error.
npx -y @reneturcios/designport mcp
{
"mcpServers": { "designport": { "command": "npx", "args": ["-y", "@reneturcios/designport", "mcp"], "env": { "FIGMA_PERSONAL_ACCESS_TOKEN": "your-token" } } } }
| Tool | Input | Figma endpoint |
|---|---|---|
get_file | file_key, version?, depth? | GET /files/{key} |
get_file_nodes | file_key, node_ids, depth?, version? | GET /files/{key}/nodes |
get_images | file_key, node_ids, format?, scale? | GET /images/{key} |
get_image_fills | file_key | GET /files/{key}/images |
get_file_styles | file_key | GET /files/{key}/styles |
get_file_components | file_key | GET /files/{key}/components |
get_team_projects | team_id | GET /teams/{id}/projects |
list_project_files | project_id | GET /projects/{id}/files |
get_comments | file_key | GET /files/{key}/comments |
post_comment | file_key, message, client_meta? | POST /files/{key}/comments |
node_ids is a comma-separated string of node IDs, sent as the API's ids parameter. post_comment's optional client_meta is a string containing a JSON-encoded object — for example '{"x":10,"y":20}' — which is parsed and sent as the API's client_meta object; keeping it a string keeps the tool schema simple.
Out of scope for this subset: the variables API, dev resources, library assets and search, webhooks, activity logs, and payments.
npm install
npm run build npm test
Tests run entirely on fake-fetch fixtures; no network and no real token are used.
MIT — see LICENSE.