Skip to content

Connect Figma (desktop MCP) to Conductor

Figma's local MCP server, served by the desktop app. Gives agents design context, variables and code-connect data for the selected frame.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Conductor installed (see its MCP documentation (opens in a new tab)).
  • Figma (desktop MCP) is available on macOS and Windows. Keep its desktop app open while you work.
  • Needs the Figma desktop app with a Dev or Full seat on a paid plan, and the desktop MCP server enabled.
  1. Step 1: Add Figma (desktop MCP) to Conductor

    For Claude Code sessions

    Saves the server to your Claude Code user settings, so every Conductor workspace gets it.

    Terminal
    claude mcp add --scope user --transport http figma-desktop http://127.0.0.1:3845/mcp

    For Codex sessions

    Saves the server to ~/.codex/config.toml, which Codex sessions in every workspace read.

    Terminal
    codex mcp add figma-desktop --url http://127.0.0.1:3845/mcp

    Or share it with your team

    Add this to .mcp.json at the project root and commit it. Claude Code sessions in every workspace on that branch pick it up.

    .mcp.json
    {
      "mcpServers": {
        "figma-desktop": {
          "type": "http",
          "url": "http://127.0.0.1:3845/mcp"
        }
      }
    }

    Or edit Codex's config file

    Add this to ~/.codex/config.toml.

    ~/.codex/config.toml
    [mcp_servers.figma-desktop]
    url = "http://127.0.0.1:3845/mcp"
    Good to know
    • The desktop app must be open for the server to respond.
    • Start a new session in Conductor after adding a server, so the agent loads it.
  2. Step 2: Check it's connected

    Terminal
    claude mcp list

    In a Conductor session, click the plug icon in the composer or run /mcp-status to see each server's status.

  3. Step 3: Try a first request

    Ask Conductor something that only works with Figma (desktop MCP) connected:

    Say to Conductor
    Get the design context for the frame I have selected in Figma and list the components it uses.

If it doesn't work

  • Conductor has no MCP settings of its own. Claude Code and Codex sessions load the same servers they use outside Conductor.
  • Each workspace is a separate git worktree. Servers added with plain claude mcp add only apply to the folder you ran it in, so use --scope user or a committed .mcp.json.
  • Conductor runs on macOS. Environment variables for local servers can go in .conductor/settings.local.toml, under [environment_variables].