Figbridge MCP Server

What the code does

We read the source, 1 d ago · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

              await fs.writeFile(outPath, Buffer.from(b64, "base64"));

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    const p = execSync(process.platform === "win32" ? "where node" : "which node", { encoding: "utf8" }).split(/\r?\n/)[0].trim();

Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.

        var p = eval(wrapped);

      caret.innerHTML = ICONS.caret;

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add figbridge -- npx -y figbridge-mcp

{
  "mcpServers": {
    "figbridge": {
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}

[mcp_servers.figbridge]
command = "npx"
args = ["-y", "figbridge-mcp"]

{
  "mcpServers": {
    "figbridge": {
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}

{
  "servers": {
    "figbridge": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "figbridge-mcp"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: FIGBRIDGE_PORT (Preferred TCP port for the local HTTP+SSE bridge that the Figma plugin connects to. Defaults to 7331. If the port is in use, the bridge walks 7331..7340 automatically).