Figma MCP Server by planetabhi: 50 REST API Tools, Run With Bun

What is this Figma MCP server?

This project is built around one idea: every Figma REST endpoint becomes a single self-describing MCP tool. The server finds the tool files in a tools/figma/ folder at startup, so adding an endpoint means adding a file.

Required parameters are checked before each call goes out. It is a local server that talks to Figma with your own personal access token, and it describes its goal as full coverage of the non-deprecated REST API.

What the 50 tools cover

• Files and nodes, including node trees, image rendering, image fills, metadata and version history.
• Variables and design tokens: read, published and bulk modify.
• Components, component sets and styles at file, published and team scope.
• Comments and reactions, folders and subfolders, users and dev resources.
• Webhooks (v2), library analytics, organization logs, embeds and payments.

Plan requirements to know first

Most tools work with a personal access token from any Figma plan. Variables need an Enterprise organization, library analytics need an Organization or Enterprise plan, and logs and AI usage need an Enterprise organization with an admin or plan access token.

Who it is for

Best for

• Developers who want direct REST API access from an agent, such as listing comments, versions or library usage.
• Teams that already hold a Figma token and prefer a local server they can read.
• Readers comparing it with Framelink, the official Figma MCP server or Figma AI Bridge.

Not for

• Node-only setups. The README says Node is not supported and the server must launch with bunx.
• Anyone who needs more than REST API tools. The README describes REST API coverage only. Another option to compare is a Rust Figma MCP server.

Use it with UiChemy

Use this server to pull file data, tokens and component lists out of Figma for an agent. When the design is ready to become a site, UiChemy's Figma to WordPress converts it into an editable WordPress page. Click Get Started on uichemy.com.

Connect Figma MCP Server by planetabhi: 50 REST API Tools, Run With Bun to your AI client

bunx figma-mcp-server

1. Install Bun

   Install Bun 1.2 or newer. The server is Bun-native, so it launches with bunx and does not run under Node.

2. Create a Figma token

   In Figma open Settings, Security, Personal access tokens and choose Generate new token. Provide it as FIGMA_API_KEY, ideally in the env block of your client config.

3. Add the config

   Paste the JSON above. Claude Desktop uses Settings, Developer, Edit Config. Cursor uses ~/.cursor/mcp.json. Gemini CLI uses ~/.gemini/settings.json. If the client cannot find bunx, use its absolute path from which bunx.

4. VS Code variant

   Use .vscode/mcp.json with a servers key and a promptString input, then reference it as ${input:figma-api-key}. VS Code asks once and stores the key in OS secret storage.

5. Restart the client

   Restart the client after editing its config, then check its tool list for the full, current set of tool names and parameters.

Client configuration

{
  "mcpServers": {
    "figma": {
      "command": "bunx",
      "args": ["figma-mcp-server"],
      "env": {
        "FIGMA_API_KEY": "your_figma_api_key_here"
      }
    }
  }
}

What you can do with it

• One tool per endpointEach Figma REST endpoint is one self-describing tool, found automatically at startup.
• Validated parametersRequired parameters are checked before the call is made.
• Wide REST coverage50 tools span files, variables, components, comments, folders, users and webhooks.
• Library analyticsComponent, style and variable actions and usages are available on eligible plans.
• Local over stdioThe server runs on your machine and speaks stdio to the client.
• Secure key entry in VS CodeAn input prompt stores the token in the operating system's secret storage.
• Easy to extendAdding an endpoint means adding one file to the tools folder.

Tools it exposes

Frequently asked questions