Figbridge MCP Server

What the code does

We read the source, 18 h ago · rules 3dff92dd89df

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();

        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": {
      "args": [
        "-y",
        "figbridge-mcp"
      ],
      "command": "npx"
    }
  }
}

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

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

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

This one needs environment variables set before it will start: 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.). The author declared them in the registry entry; get the values from the project itself.