Data as of
Framelink MCP for Figma for Cursor: Setup & Config
Framelink supplies Cursor with selected Figma metadata and image assets.
Framelink MCP for Figma Cursor configuration
Choose Cursor configuration scope
For Framelink MCP for Figma, open Project: .cursor/mcp.json User: ~/.cursor/mcp.json. Merge into mcpServers at project or user scope.
Add Framelink MCP for Figma to Cursor
Use the Figma-Context-MCP entry below in mcpServers. Keep Framelink MCP for Figma's documented stdio connection fields and your other Cursor entries.
Check Framelink MCP for Figma in Cursor
Framelink MCP for Figma: Enable in Cursor’s MCP settings; inspect tools.
Config file · Project: .cursor/mcp.json
User: ~/.cursor/mcp.json
{
"mcpServers": {
"Figma-Context-MCP": {
"command": "npx",
"args": [
"-y",
"figma-developer-mcp",
"--figma-api-key=YOUR-KEY",
"--stdio"
],
"env": {}
}
}
}Framelink MCP for Figma in Cursor: stdio checks
- Cursor must find npx figma-developer-mcp (Node.js/npm) for Framelink MCP for Figma. Enable the project/user entry in MCP settings and inspect its tools.
- Framelink MCP for Figma uses stdio here: Cursor must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
- Tools
- download_figma_images, get_figma_data
Framelink MCP for Figma — details. Cursor guide
Frequently asked questions
Cursor's Framelink MCP for Figma entry belongs under mcpServers in .cursor/mcp.json (project) or ~/.cursor/mcp.json (user). Confirm the active scope in MCP settings.
Cursor's Figma-Context-MCP example uses stdio.
Framelink MCP for Figma's Cursor configuration invokes npx figma-developer-mcp (Node.js/npm).
Framelink MCP for Figma's stored list contains 2 tools, including download_figma_images, get_figma_data. Compare those names with Cursor's connected tool list; the stored list is not a live check.