Framelink MCP for Figma
The leading design-to-code MCP server. Bridges the Figma API to MCP clients, simplifying the API response to keep only layout and styling information so the model gets useful context with the agent's context budget kept tight. Specifically tuned for Cursor; works with any MCP client.
“Framelink MCP for Figma solves the design-to-code problem better than every alternative I have tested. The core insight is that pasting screenshots gives the LLM pixels and asks it to reverse-engineer the layout; Framelink fetches the structured Figma data through Figma's API directly, simplifies the response to keep only layout and styling information, and hands that to the model. The result is one-shot designs that compile and look correct. Cursor users get the most value because the server is specifically tuned for Cursor's agent mode, but any MCP-compatible client works. The 14.5k stars are the loudest signal in the design category and reflect a tool that solved a real workflow gap. Setup is simple: an npm install and a Figma personal access token. The honest weakness is that the simplification step is opinionated; teams whose designs use Figma plugins or auto-layout features in non-standard ways may find the simplified response misses information that matters to their codebase.”
INSTALL THIS SERVER
{
"mcpServers": {
"Framelink Figma MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
]
}
}
}
{
"mcpServers": {
"Framelink Figma MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
]
}
}
}
{
"mcpServers": {
"Framelink Figma MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
]
}
}
}
{
"mcpServers": {
"Framelink Figma MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
]
}
}
}
{
"mcpServers": {
"Framelink Figma MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
]
}
}
}
4 TOOLS AVAILABLE
OUR ASSESSMENT
- Simplifies Figma's verbose API response so the model receives layout and styling context only; reduces hallucination and improves first-shot accuracy.
- 14.5k stars and active maintenance signal real workflow adoption among design-to-code teams.
- Simple install: npx figma-developer-mcp with a Figma personal access token.
- Specifically tuned for Cursor's agent mode; every MCP-compatible client benefits from the same context reduction.
- Context simplification is opinionated; designs using non-standard Figma plugins or unusual auto-layout patterns may produce simplified responses that miss codebase-relevant information.
- Requires a Figma personal access token; team-shared tokens carry the usual rotation discipline overhead.
- Best-fit experience is in Cursor; other clients work but get less of the agent-mode-specific tuning.
The server requires a Figma personal access token (passed via --figma-api-key flag or FIGMA_API_KEY env var). The token's scope determines what the agent can read; Figma personal access tokens are read-write by default, so for agent contexts a read-only token (when Figma supports it for the team's plan) is the safer choice. The server itself is local and stateless; tokens stay on the operator's machine and pass to Figma's API on each call.
Teams using Figma for design and Cursor (or any AI coding tool) for implementation. Best for greenfield component implementation; pairs well with design system tokens.
TECHNICAL DETAILS
ADOPTION METRICS
// Reading this14.5k stars place this among the most-starred MCP servers in the design category. Star traction reflects strong design-to-code workflow adoption among Cursor users.
// Reading thisTop-ranked design MCP by every stat we track. The context-simplification approach is the architectural reason it outperforms screenshot-based alternatives.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 5 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4.5editorial | 14,550 | — | APR 28, 2026 |
| PulseMCP | — unrated | unavailable | unavailable | APR 28, 2026 |
| MCP.so | — unrated | unavailable | unavailable | APR 28, 2026 |
| Official MCP Registry | — unrated | unavailable | unavailable | APR 28, 2026 |
| Awesome MCP Servers | — unrated | unavailable | unavailable | APR 28, 2026 |
| Smithery | — unrated | unavailable | unavailable | APR 28, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.