Figma Context MCP vs Figme
A side-by-side look at the Figma Context MCP and Figme MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Figma Context MCP for architecture & design work as a local process; choose Figme for architecture & design as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Figma Context MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
FIGMA_API_KEY. - You want tools like
get_figma_design, get_image_fills, render_node_images.
Choose Figme when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Architecture & Design |
| Quality signal | 55/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | FIGMA_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 3 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | Not listed |
| Full listing | View Figma Context MCP | View Figme |
Tools & capabilities
Figma Context MCP tools 4
get_figma_designFetches CSS-aligned, LLM-optimized design data. Supports SVG export to custom dir.get_image_fillsRetrieves image fill URLs from a Figma filerender_node_imagesRenders Figma nodes as PNG imagesread_vector_svgReads vector node data as SVG
Figme tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste 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.
Figma Context MCP
{
"mcpServers": {
"figma-context-mcp": {
"command": "npx",
"args": [
"-y",
"@tmegit/figma-to-code-mcp"
],
"env": {
"FIGMA_API_KEY": "YOUR_FIGMA_API_KEY_HERE"
}
}
}
}
Figme
{
"mcpServers": {
"figme": {
"command": "npx",
"args": [
"-y",
"figme-mcp"
]
}
}
}
Frequently asked questions
Figma Context MCP is categorized under Architecture & Design and uses a local stdio subprocess. Figme belongs to Architecture & Design and uses a local stdio subprocess. Pick Figma Context MCP for architecture & design work and Figme for architecture & design.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Figma Context MCP has no declared pricing — check the project's own site. Figme has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add figma-context-mcp and figme as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Figma Context MCP has a quality signal of 55/100 (Good) with 2 views, 0 installs and 6 GitHub stars. Figme has 40/100 (Fair) with 0 views, 0 installs and 3 GitHub stars.