Skip to content

Connect Figma (remote MCP) to Conductor

Figma's hosted MCP server with design context and beta canvas writes. Available on all plans, with tight call limits on Starter, View and Collab seats.

MCP serverOfficialChecked 2026-11-16

Before you start

  • Conductor installed (see its MCP documentation (opens in a new tab)).
  • Figma (remote MCP) is available on macOS, Windows, Linux and the web.
  • Starter plan and View/Collab seats get 6 tool calls a month; Dev/Full seats on paid plans get 200 a day.
  1. Step 1: Add Figma (remote 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-remote https://mcp.figma.com/mcp

    For Codex sessions

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

    Terminal
    codex mcp add figma-remote --url https://mcp.figma.com/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-remote": {
          "type": "http",
          "url": "https://mcp.figma.com/mcp"
        }
      }
    }

    Or edit Codex's config file

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

    ~/.codex/config.toml
    [mcp_servers.figma-remote]
    url = "https://mcp.figma.com/mcp"
    Good to know
    • Start a new session in Conductor after adding a server, so the agent loads it.
    • To sign in, open Conductor's MCP status dialog and use the sign-in action on the server's row.
  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 (remote MCP) connected:

    Say to Conductor
    Here's a link to a Figma frame: <paste link>. Summarise its layout and the variables 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].