Figma MCP Rs MCP Server

What the code does

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

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 result = spawnSync(binaryPath, process.argv.slice(2), { stdio: 'inherit' });

const binaryPath = path.join(__dirname, `${osDir}-${archDir}`, binaryName);

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.

  const compiled: unknown = eval(`(async () => {\n${code}\n})`);

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 figma-mcp-rs -- npx -y figma-mcp-rs

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

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

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

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