Figma MCP server in Rust: plugin bridge, no API token, no rate limits, 73 tools.
io.github.alvinindra/figma-mcp-rust — Figma Model Context Protocol (MCP) Server
This Model Context Protocol (MCP) server provides a Rust-based bridge to Figma. It uses a plugin bridge approach and is described as free with no API token and no rate limits. The Rust rewrite includes structured logging, race-free request correlation, and a declarative tool table with 73 tools.
🛠️ Key Features
Rust port of a Figma MCP server
Figma plugin bridge
No API token required
No rate limits
Structured logging
Race-free request correlation
Declarative tool table
73 tools
🚀 Use Cases
Using MCP tools to interact with Figma content via the plugin bridge
Referencing an MCP tool catalogue for Figma-related operations
⚡ Developer Benefits
Easier tool management via a declarative tool table
More reliable request handling via race-free request correlation
Improved observability with structured logging
⚠️ Limitations
Limited to the Figma MCP scope described by the server’s plugin bridge and tool catalogue
A high-performance Rust port of vkhanhqui/figma-mcp-go.
All credit for the original design, the Figma plugin bridge, and the tool catalogue goes to
@vkhanhqui. This repo migrates that same MCP server to Rust
with structured logging, race-free request correlation, and a declarative tool table;
see "What changed in the Rust rewrite" below.
Figma MCP: Free, No Rate Limits
Open-source Figma MCP server with full read/write access via plugin. No REST API, no rate limits. Turn text into designs and designs into real code. Works with Cursor, Claude, GitHub Copilot, and any MCP-compatible AI tool.
Highlights
No Figma API token required
No rate limits, free plan friendly
Read and Write live Figma data via plugin bridge, 73 tools in total
Full design automation: styles, variables, components, prototypes, and content
Design strategies built in as MCP prompts, plus matching Claude Code skills
Why this exists
Most Figma MCP servers rely on the Figma REST API.
That sounds fine until you hit this:
Plan
Limit
Starter / View / Collab
6 tool calls/month
Pro / Org (Dev seat)
200 tool calls/day
Enterprise
600 tool calls/day
If you're experimenting with AI tools, you'll burn through that in minutes.
I didn't have enough money to pay for higher limits.
So I built something that doesn't use the API at all.
Installation & Setup
Install via npx, no build step required.
1. Configure your AI tool
Claude Code CLI
bash
claude mcp add -s project figma-mcp-rust -- npx -y @alvinindra/figma-mcp-rust@latest
Set blend mode (MULTIPLY, SCREEN, OVERLAY, and more) on one or more nodes
set_constraints
Set responsive constraints { horizontal, vertical } on one or more nodes
move_nodes
Move nodes to an absolute x/y position
resize_nodes
Resize nodes by width and/or height
rename_node
Rename a node
clone_node
Clone a node, optionally repositioning or reparenting
reparent_nodes
Move nodes to a different parent frame, group, or section
batch_rename_nodes
Bulk rename nodes via find/replace, regex, or prefix/suffix
find_replace_text
Find and replace text across all TEXT nodes in a subtree or page; supports regex
Write: Delete
Tool
Description
delete_nodes
Delete one or more nodes permanently
Write: Prototype
Tool
Description
set_reactions
Set prototype reactions (triggers + actions) on a node; mode replace or append
remove_reactions
Remove all or specific reactions by zero-based index from a node
Write: Styles
Tool
Description
set_effects
Apply drop shadow / blur effects directly on a node (no style required)
create_paint_style
Create a named paint style with a solid color
create_text_style
Create a named text style with font, size, and spacing
create_effect_style
Create a named effect style (drop shadow, inner shadow, blur)
create_grid_style
Create a named layout grid style (columns, rows, or grid)
update_paint_style
Rename or recolor an existing paint style
apply_style_to_node
Apply an existing local style to a node, linking it to that style
delete_style
Delete any style (paint, text, effect, or grid) by ID
Write: Variables
Tool
Description
create_variable_collection
Create a new local variable collection with an optional initial mode
add_variable_mode
Add a new mode to an existing collection (e.g. Light/Dark)
create_variable
Create a variable (COLOR/FLOAT/STRING/BOOLEAN) in a collection
set_variable_value
Set a variable's value for a specific mode
bind_variable_to_node
Bind a variable to a node property; supports fillColor, strokeColor, visible, opacity, rotation, width, height, corner radii, spacing, and more
delete_variable
Delete a variable or an entire collection
Write: Pages
Tool
Description
add_page
Add a new page to the document (optional name and index)
delete_page
Delete a page by ID or name (cannot delete the only page)
rename_page
Rename a page by ID or current name
Write: Components & Navigation
Tool
Description
navigate_to_page
Switch the active Figma page by ID or name
group_nodes
Group two or more nodes into a GROUP
ungroup_nodes
Ungroup GROUP nodes, moving children to the parent
swap_component
Swap the main component of an INSTANCE node
detach_instance
Detach component instances, converting them to plain frames
Read: Document & Selection
Tool
Description
get_document
Full current page tree
get_metadata
File name, pages, current page
get_pages
All pages (IDs + names), lightweight, no tree loading
get_selection
Currently selected nodes
get_node
Single node by ID
get_nodes_info
Multiple nodes by ID
get_design_context
Depth-limited tree with detail level (minimal/compact/full)
search_nodes
Find nodes by name substring and/or type within a subtree
scan_text_nodes
All text nodes in a subtree
scan_nodes_by_types
Nodes matching given type list
get_viewport
Current viewport center, zoom, and visible bounds
Read: Styles & Variables
Tool
Description
get_styles
Paint, text, effect, and grid styles
get_variable_defs
Variable collections and values
get_local_components
All components + component sets with variant properties
get_annotations
Dev-mode annotations
get_fonts
All fonts used on the current page, sorted by frequency
get_reactions
Prototype/interaction reactions on a node
Export
Tool
Description
get_screenshot
Base64 image export of any node
save_screenshots
Export images to disk (server-side, no API call)
export_frames_to_pdf
Export multiple frames as a single multi-page PDF file saved to disk
export_tokens
Export design tokens (variables + paint styles) as JSON or CSS
MCP Prompts
Prompt
Description
read_design_strategy
Best practices for reading Figma designs
design_strategy
Best practices for creating and modifying designs
text_replacement_strategy
Chunked approach for replacing text across a design
annotation_conversion_strategy
Convert manual annotations to native Figma annotations
swap_overrides_instances
Transfer overrides between component instances
reaction_to_connector_strategy
Map prototype reactions into interaction flow diagrams
style_audit_strategy
Find nodes using raw values instead of linked styles or variables
bulk_rename_strategy
Rename nodes to follow a consistent naming convention
design_token_generation_strategy
Build a variable and style token system from an existing design
generate_color_palette
Create a primitive color scale plus semantic aliases as variables
generate_type_scale
Create a full typographic scale as text styles
generate_component_variants
Clone a component into size, theme, state, or dark-mode variants
Each prompt is also available as a Claude Code skill when the server is installed through the plugin marketplace, alongside a bridge-troubleshooting skill for connection issues.
Memory-safe websocket bridge: request/response correlation uses tokio::sync::oneshot
instead of Go channels guarded by sync.Once, removing the send-on-closed-channel race.
Declarative tool table: all 73 tool registrations live in a single static array
(src/tools/definitions.rs) instead of ~700 lines of repetitive Go handlers. New tools
are added by appending one entry plus an optional JSON Schema builder.
Structured logging via tracing: every component emits per-target events
(bridge, leader, follower, election, node) at adjustable levels. Set
FIGMA_MCP_LOG=debug for verbose output.
thiserror-based error types instead of formatted strings, so callers can match on
specific failure modes (NotConnected, Timeout, etc.).
Pure-Rust PDF merging via lopdf, no external CLI dependency.
First-class CLI via clap with derived help text and validation.
