1. Home
  2. Framelink MCP for Figma
  3. Framelink MCP for Figma for VS Code: Setup & Config

Data as of

Framelink MCP for Figma for VS Code: Setup & Config

Framelink supplies VS Code with selected Figma metadata and image assets.

Framelink MCP for Figma VS Code configuration

  1. Choose VS Code configuration scope

    For Framelink MCP for Figma, open Workspace: .vscode/mcp.json. Merge into servers; preserve existing inputs.

  2. Add Framelink MCP for Figma to VS Code

    Use the Figma-Context-MCP entry below in servers. Keep Framelink MCP for Figma's documented stdio connection fields and your other VS Code entries.

  3. Check Framelink MCP for Figma in VS Code

    Framelink MCP for Figma: Start in VS Code’s MCP controls; inspect output and trust prompts.

Config file · Workspace: .vscode/mcp.json

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

Framelink MCP for Figma in VS Code: stdio checks

  • Make npx figma-developer-mcp (Node.js/npm) available in the workspace, container, or remote environment hosting Framelink MCP for Figma. Start through VS Code's MCP controls; inspect output and trust prompts.
  • Framelink MCP for Figma uses stdio here: VS Code 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. VS Code guide

Frequently asked questions

For Framelink MCP for Figma, edit workspace .vscode/mcp.json. VS Code requires servers rather than mcpServers; preserve the displayed type on each entry.

VS Code's Figma-Context-MCP example uses stdio.

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