A side-by-side look at the Figma MCP and Figma Context MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma MCP for architecture & design work as a local process; choose Figma Context MCP for architecture & design as a local process. You can also run both side by side in one mcpServers block.
FIGMA_TOKEN, FIGMA_API_BASE_URL, FIGMA_REQUEST_TIMEOUT_MS, FIGMA_MAX_JSON_BYTES, FIGMA_MAX_FRAME_BYTES, FIGMA_OUTPUT_ROOT, FIGMA_ALLOW_HTTP_FOR_TESTS.list_frames, fetch_frame.FIGMA_API_KEY, PORT.get_figma_data, download_figma_images.Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 53/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | FIGMA_TOKENFIGMA_API_BASE_URLFIGMA_REQUEST_TIMEOUT_MSFIGMA_MAX_JSON_BYTESFIGMA_MAX_FRAME_BYTESFIGMA_OUTPUT_ROOTFIGMA_ALLOW_HTTP_FOR_TESTS | FIGMA_API_KEYPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 16,009 |
| Directory activity | 1 views 0 installs 0 upvotes | 6 views 0 installs 0 upvotes |
| Tools | 2 | 2 |
| Full listing | View Figma MCP | View Figma Context MCP |
list_framesList and optionally filter all top-level FRAME nodes in a Figma file, with exact page/name/node-id data, dimensions, and file metadatafetch_frameFetch one Figma frame and transactionally write frame.png, node.json, and a normalized image-fill map into a directory below the output rootget_figma_dataGet comprehensive Figma file data including layout, content, visuals, and component informationdownload_figma_imagesDownload SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/userPaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
{
"mcpServers": {
"figma-mcp-2": {
"command": "npx",
"args": [
"-y",
"@scalably-io/figma-mcp"
],
"env": {
"FIGMA_TOKEN": "YOUR_FIGMA_TOKEN_HERE",
"FIGMA_API_BASE_URL": "YOUR_FIGMA_API_BASE_URL_HERE",
"FIGMA_REQUEST_TIMEOUT_MS": "YOUR_FIGMA_REQUEST_TIMEOUT_MS_HERE",
"FIGMA_MAX_JSON_BYTES": "YOUR_FIGMA_MAX_JSON_BYTES_HERE",
"FIGMA_MAX_FRAME_BYTES": "YOUR_FIGMA_MAX_FRAME_BYTES_HERE",
"FIGMA_OUTPUT_ROOT": "YOUR_FIGMA_OUTPUT_ROOT_HERE",
"FIGMA_ALLOW_HTTP_FOR_TESTS": "YOUR_FIGMA_ALLOW_HTTP_FOR_TESTS_HERE"
}
}
}
}
{
"mcpServers": {
"glips-figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}