What is figma-mcp-rust?
figma-mcp-rust is an open source Figma MCP server written in Rust. It reads and writes live Figma data through a plugin bridge instead of the REST API, so no API token is needed and rate limits do not apply. The README counts 73 tools covering design, styles, variables and export.
It is a Rust port of vkhanhqui's figma-mcp-go, and the README credits that author for the original design, the plugin bridge and the tool catalogue. The rewrite keeps the same server and changes the engine underneath.
The maintainer says he built it because Figma's REST limits, as few as 6 tool calls a month on Starter, Collab and View plans, are used up in minutes. The plugin bridge avoids the API entirely.
What the Rust rewrite changed
- A websocket bridge that correlates requests with tokio oneshot channels, which removes a send on closed channel race.
- One declarative table holds all 73 tool registrations, so a new tool is one added entry.
- Structured logging through tracing, with
FIGMA_MCP_LOG=debugfor verbose output. - Typed errors such as NotConnected and Timeout, and pure Rust PDF merging with no external CLI.
Design strategies as prompts
The server ships 12 MCP prompts, including read_design_strategy, style_audit_strategy, design_token_generation_strategy and generate_color_palette. Installing through the plugin marketplace also adds matching skills and a bridge troubleshooting skill.
Who it suits
Best for
- Free plan users who hit limits with the official Figma MCP or REST based servers.
- Agents that must create and edit frames, text, styles and variables, not only read them.
- Related: Talk to Figma and Hopp's Figma bridge.
Not for
- Figma in the browser only. The plugin is imported in Figma Desktop.
- Anyone wanting a small tool list. The server registers 73 tools.
- Work on destructive edits without care, since delete_nodes removes nodes permanently.
Use it with UiChemy
figma-mcp-rust helps an agent build or tidy a Figma design. UiChemy's Figma to WordPress then converts that Figma file into Elementor or Gutenberg pages, so the design reaches a live WordPress site. Click Get Started on uichemy.com.
Connect figma-mcp-rust: Figma MCP with 73 Tools and No REST API to your AI client
claude mcp add -s project figma-mcp-rust -- npx -y @alvinindra/figma-mcp-rust@latestAdd the server
In Claude Code run the command above, or use
codex mcp add figma-mcp-rust -- npx -y @alvinindra/figma-mcp-rust@latestin Codex CLI. The JSON goes in.mcp.json.Use the VS Code form if needed
For Cursor, VS Code or GitHub Copilot, put a stdio entry with the same npx command in
.vscode/mcp.json.Install the Figma plugin
In Figma Desktop choose Plugins, Development, Import plugin from manifest. Select
manifest.jsonfrom the plugin.zip on the releases page.Run the plugin in a file
Open any Figma file and run the plugin so the bridge connects, then ask the agent to read or edit the design.
Optional: add the plugin marketplace skills
In Claude Code run
/plugin marketplace add alvinindra/figma-mcp-rust, then/plugin install figma-mcp-rust@figma-mcp-rust. This adds 13 skills.
Client configuration
{
"mcpServers": {
"figma-mcp-rust": {
"command": "npx",
"args": ["-y", "@alvinindra/figma-mcp-rust"]
}
}
}Endpoints and ports
https://github.com/alvinindra/figma-mcp-rust/releasesplugin.zip with manifest.jsonhttps://github.com/vkhanhqui/figma-mcp-goThe Go server this is ported fromWhat you can do with it
- Read and write accessThe plugin bridge lets an agent create, modify and delete live Figma content, not only read it.
- No API tokenNothing goes through the REST API, so no token is required and there are no rate limits.
- Styles and variablesTools create paint, text, effect and grid styles, variable collections, modes and variable bindings.
- Prototype reactionsset_reactions and remove_reactions edit triggers and actions on a node.
- Bulk operationsbatch_rename_nodes and find_replace_text change many nodes at once, with regex support.
- Export toolsScreenshots, multi page PDFs and token export to JSON or CSS run server side.
- Built in strategiesTwelve MCP prompts cover reading, token generation, style audits, palettes and type scales.
Tools it exposes
create_frame
Creates a frame with optional auto layout, fill and parent.
create_text
Creates a text node with the font loaded automatically.
set_auto_layout
Sets or updates auto layout properties on a frame.
create_variable
Creates a COLOR, FLOAT, STRING or BOOLEAN variable in a collection.
bind_variable_to_node
Binds a variable to a node property such as fill, opacity or spacing.
get_design_context
Returns a depth limited tree with a minimal, compact or full detail level.
get_selection
Returns the currently selected nodes.
get_variable_defs
Returns variable collections and their values.
search_nodes
Finds nodes by name substring or type within a subtree.
get_screenshot
Exports a base64 image of any node.
export_tokens
Exports design tokens, variables and paint styles, as JSON or CSS.
export_frames_to_pdf
Exports several frames as one multi page PDF saved to disk.
Frequently asked questions
What is figma-mcp-rust?
It is an open source Figma MCP server written in Rust, ported from figma-mcp-go. It reads and writes live Figma data through a plugin bridge, needs no REST API token and has no rate limits, with 73 tools in total.
How do I install figma-mcp-rust?
Add the server with claude mcp add -s project figma-mcp-rust -- npx -y @alvinindra/figma-mcp-rust@latest, or the codex equivalent. Then import the plugin manifest in Figma Desktop and run the plugin inside a file.
Does it need a Figma API token?
No. The README lists no API token required as a highlight. The server talks to a Figma plugin you import in Figma Desktop, so it works on the free plan and avoids the REST call limits.
Which AI coding agents does it support?
The README gives setup for Claude Code, Codex CLI, and Cursor, VS Code and GitHub Copilot through .vscode/mcp.json. It says it works with any MCP compatible AI tool using a standard .mcp.json entry.
What are the MCP prompts?
The server includes 12 design strategy prompts, such as read_design_strategy, style_audit_strategy, bulk_rename_strategy, generate_color_palette and generate_type_scale. Each is also a skill when you install through the plugin marketplace and keep working in your editor.
How is it different from figma-mcp-go?
It is a Rust migration of the same server. The README lists a memory safe websocket bridge, a declarative tool table, structured tracing logs, typed errors and pure Rust PDF merging. Credit for the original tool catalogue stays with the Go author.
What license does it use?
The repository is MIT licensed, so personal and commercial use is allowed under the usual terms. It is open source, with full read and write access to Figma through a plugin and no REST API or rate limits. Related: Figma UI MCP.