Figma MCP Server (Antonytm)
Figma MCP Server
A community MCP server with a Figma plugin: the agent creates frames, text and components in the open file, not just reads them
- 176 ★ on the repository
- Last commit
- Apache-2.0
Broad access
Why this level
- The agent writes into the open Figma document: it creates, edits and deletes nodes without a separate confirmation of each action
- The plugin opens the document to an external system, that is, to any client connected to the local server
Install
- Works in
Manual install
{"mcpServers": {"figma": {"url": "http://localhost:38450/mcp"}}}Streaming HTTP to the local address. The entry follows the address in the README; the field format depends on the client version.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- The agent writes into the open Figma document: it creates, edits and deletes nodes without a separate confirmation of each action
- The plugin opens the document to an external system, that is, to any client connected to the local server
This is third-party code. Review the repository files before installing.
What it does
The project has two parts: an MCP server on Node.js and a Figma plugin. The official Figma server gives an agent a read-only view of a design, while this one lets the agent change the document. It creates frames, rectangles, text, images and components, clones and moves nodes, sets fills, strokes, corner radius and auto layout, and deletes nodes. The server accepts tool calls, queues them and passes them to the plugin over a socket.io WebSocket. The plugin performs the action in the open Figma file and returns the result. If a reply takes too long, the server ends the call with a timeout. There are read tools too: the list of pages, node details and all components in the file. Components have properties, bindings of those properties to layers and instance properties, and a separate tool adds prototype links between frames.
Who it is for. Designers and frontend developers who ask Claude Code or Cursor to build an interface straight in a working Figma file and do not want to move the result over from a chat by hand.
Good fit when
- You need a screen draft: the agent builds frames, headings and buttons in the open Figma file
- A component library is edited in bulk, for example adding a property to ten components at once
- Nodes have to be moved to another parent or recolored from a task description
- The agent should read the file structure and extend it: pages, components, node properties
- A prototype is assembled from ready frames and needs transition links between them
Not a fit when
- Reading a design and exporting it to code is enough: Figma has an official server for that, and the author himself recommends it
- The file is shared and in use, and there is no backup: the agent deletes and edits nodes without a separate confirmation
- You need access over the network from another machine: the project is meant for local work, and network use is at your own responsibility
- Node.js is missing, or the plugin cannot be attached through Figma development mode
Example request
In the open Figma file create a 390 by 844 frame on the Login page with a heading, two input fields and a blue button, then list the nodes you createdMCP
- Transport
- http, stdio
- Authentication
- not required
Environment variables
TRANSPORT- Server transport: stdio by default, or streamable-http for connecting by address.
Limitations
- The plugin is not published in the Figma catalog yet: the author is waiting for review. For now it is built from source and attached through Plugins, Development, Import plugin from manifest.
- The plugin window has to stay open. While it is closed, tool calls do not reach Figma.
- The tools section of the README is marked TBD, so the feature set is easier to learn from the source and from the tool list in the client.
- The server listens on local port 38450 and is meant for a single machine; network use is left at your own responsibility by the author.
How to disable. Close the plugin window in Figma and stop the server, then remove the http://localhost:38450/mcp entry from the MCP client settings. The plugin itself is removed from the Plugins, Development list in Figma. Changes the agent already made to the file can be rolled back with Figma's regular version history.
FAQ
How does this server differ from the official Figma MCP server?
The official server only reads a design, while this one changes the document through a plugin: it creates, moves, recolors and deletes nodes. The author says outright to use the official server when reading is enough.
How do I connect Figma MCP Server to Claude Code or Cursor?
Build and start the plugin and the server following the repository instructions, then add a streaming HTTP transport to the client with the address http://localhost:38450/mcp. Once the plugin is running, Figma shows the message Connected to MCP server.
Why does the agent not change the design and the plugin says Not connected to MCP server?
Either the server is not running yet or the plugin window is closed. Start the server with npm run start in the mcp folder, keep the plugin window open and wait for the message Connected to MCP server.
What tools does the server have?
Reading: pages, node details, all components in the file. Writing: frames, rectangles, text, images, components and their instances, fill, stroke, corner radius, auto layout, moving, cloning and deleting nodes, component properties, prototype links. The README list is marked TBD, so check the tool list in the client.
Is it safe to expose the server over a network?
The author built the project for local work: the server listens on port 38450 on your machine and, like the official one, does not expose data to the network. Exposing it is advised only at your own responsibility, because the plugin opens the document to any connected client.
Discussion
No questions or reviews yet.
Related
MCP serversFigma's official MCP server: code from a selected frame, design system variables and components, and writing designs to the canvas
MCP bridge between an agent (Cursor, Claude Code, Codex) and Figma for reading designs and editing them on the canvas
An MCP server that lets an agent read and edit Figma designs: colors, typography, components and export
An MCP server that gives the agent simplified Figma layout data from a link so it can build the screen more accurately than from a screenshot
Figma MCP Bridge
figma-mcp-bridge
A Figma Desktop plugin and an MCP server: an agent reads tokens, styles and components without the Figma REST API and its limits. Not from Figma
A free, two-way Figma MCP server: turns designs into framework-aware code and pushes code back to the canvas
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Figma MCP Server (Antonytm) (this card) | no | not required | 176 | |
| Claude Talk to Figma MCP | no | not required | 676 | also reads and edits Figma designs; here the MCP endpoint and the socket server live in one process on port 38450 |
| Figma Console MCP | no | API key | 3,159 | focused on variables, styles and syncing design-system tokens with code |
README in short
The README explains why the project exists and walks through three steps: build the Figma plugin, start the MCP server, connect the client over HTTP. It then covers a developer section with dev mode and the MCP inspector, a diagram of how the parts talk and a security section. At the end the author lists alternatives and asks to use the official server where it is enough.