Data as of

Framelink MCP for Figma for Claude Desktop: Setup & Config

Framelink supplies Claude Desktop with selected Figma metadata and image assets.

What you can do with Framelink MCP for Figma in Claude Desktop

Bring the design's structure and assets into coding, with context filtering built into the handoff.

  • Give an implementation request the layout metadata behind a shared design link.
  • Inspect file-wide structure when the requested design has no known node identifier.

Before you start: Framelink MCP for Figma in Claude Desktop

  • Personal access token issued by Figma
  • npx available to the client process
  • Editor or assistant with MCP support

The argument array reproduces the macOS/Linux README example, including its YOUR-KEY marker; substitute your token. Windows adds cmd /c around npx. As an alternative to the inline token, the README permits FIGMA_API_KEY in env and also mentions PORT.

Framelink MCP for Figma Claude Desktop configuration

  1. Choose Claude Desktop configuration scope

    For Framelink MCP for Figma, open macOS: ~/Library/Application Support/Claude/claude_desktop_config.json Windows: %APPDATA%\Claude\claude_desktop_config.json. Merge under mcpServers via Settings → Developer → Edit Config when available.

  2. Add Framelink MCP for Figma to Claude Desktop

    Use the Figma-Context-MCP entry below in mcpServers. Keep Framelink MCP for Figma's documented stdio connection fields and your other Claude Desktop entries.

  3. Check Framelink MCP for Figma in Claude Desktop

    Framelink MCP for Figma: Fully quit and reopen Claude Desktop; check developer diagnostics.

Config file · macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

Windows: %APPDATA%\Claude\claude_desktop_config.json

JSON
{
  "mcpServers": {
    "Figma-Context-MCP": {
      "command": "npx",
      "args": [
        "-y",
        "figma-developer-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ],
      "env": {}
    }
  }
}

Framelink MCP for Figma tools available to Claude Desktop

Framelink MCP for Figma's stored tool list documents 2 tools; compare it with Claude Desktop's connected tool list, because the stored list is not a live check.

download_figma_images

When Claude Desktop requests download_figma_images from Framelink MCP for Figma, review the action before approving it.

Fetch design assets as PNG or SVG by specifying image or icon nodes.

get_figma_data

When Claude Desktop requests get_figma_data from Framelink MCP for Figma, review the action before approving it.

Framelink MCP for Figma: full stored tool descriptions

Troubleshooting Framelink MCP for Figma in Claude Desktop

  • Fully quit and reopen Claude Desktop for Framelink MCP for Figma. If npx figma-developer-mcp (Node.js/npm) is missing, check the desktop process's PATH, which may differ from your terminal.
  • Framelink MCP for Figma uses stdio here: Claude Desktop must keep the configured process running; protocol output belongs on stdout and diagnostics on stderr.
  • Known limitation: A personal Figma credential is necessary even when a design link is available.
  • Known limitation: Cursor receives the detailed workflow treatment; other clients are discussed more generally.
  • General Claude Desktop troubleshooting lives in the /clients/claude-desktop guide.

Framelink MCP for Figma — details. Claude Desktop guide

Frequently asked questions

Claude Desktop loads Framelink MCP for Figma from claude_desktop_config.json: ~/Library/Application Support/Claude/ on macOS, or %APPDATA%\Claude\ on Windows. Open it via Settings → Developer → Edit Config when available.

Claude Desktop's Figma-Context-MCP example uses stdio.

Framelink MCP for Figma's Claude Desktop 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 Claude Desktop's connected tool list; the stored list is not a live check.

It comes from Figma metadata rather than image interpretation. Framelink trims the API response around implementation-relevant styling and layout.

No. The documented chat workflow can begin with a group or frame link as well as a file link.