figma-mcp-rs
Provides full read/write access to live Figma and FigJam files through a plugin bridge over a local WebSocket, bypassing the REST API and its rate limits. Enables creating and modifying frames, text, shapes, components, styles, variables, and prototypes; reading and serializing Figma/FigJam documents; building FigJam boards with sticky notes, connectors, tables, and code blocks; exporting design tokens; and running Plugin API JavaScript via escape-hatch tools for operations the named tools don't cover.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
figma-mcp-rs
Figma/FigJam MCP server in Rust — free, no rate limits. Rust port of vkhanhqui/figma-mcp-go with a rewritten SolidJS plugin and FigJam support.
Open-source MCP server with full read/write access to Figma and FigJam via plugin — no REST API, no rate limits. Turn text into designs and designs into real code. Works with Claude, Cursor, 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/FigJam data via plugin bridge — 87 tools total (73 from the Go reference, plus
get_status,execute_code, eight FigJam tools, theuse_figmaescape hatch, and four design-system tools:update_style,update_variable,set_variable_mode,bind_variable_to_style)Full design automation — styles, variables (values, aliases, scopes, modes), components, prototypes, and content
Colors accepted anywhere as hex,
rgb(),hsl(), oroklch();get_stylesandexport_tokensemit any of them viacolorFormatDesign strategies included — 12 MCP prompts built in
Native binary, fast startup, low memory
Plugin bundled in the binary — the server self-installs it on first run, no download step
Built on rmcp 3.2; negotiates MCP protocol revision with each client
Why this exists
The official Figma MCP servers go through the REST API, which is rate limited per plan:
Figma plan | REST budget |
Starter | 6 calls/month |
Professional | 200 calls/day |
Enterprise | 600 calls/day |
This server never calls the REST API. It talks to a plugin running inside Figma Desktop over a local WebSocket, so every read and write is unlimited and free — and unlike REST, the plugin can write to the open file.
Related MCP server: layerbridge
Performance
Measured on Apple M4 Pro: ~6 MB RSS idle, ~7 MB with a plugin connected during tool round trips; startup < 10 ms. The Go reference runs ~15–25 MB.
Installation & Setup
1. Configure your AI tool
Claude Code CLI
claude mcp add -s project figma-mcp-rs -- npx -y figma-mcp-rs@latestOr build from source:
make build # cargo build --release + plugin build
claude mcp add -s project figma-mcp-rs -- /path/to/figma-mcp-rs/target/release/figma-mcp-rsCodex CLI
codex mcp add figma-mcp-rs -- npx -y figma-mcp-rs@latestClaude Code plugin marketplace (also installs the 15 skills)
/plugin marketplace add <this-repo>
/plugin install figma-mcp-rs@figma-mcp-rs.mcp.json (Claude and other MCP-compatible tools)
{
"mcpServers": {
"figma-mcp-rs": {
"command": "npx",
"args": ["-y", "figma-mcp-rs"]
}
}
}.vscode/mcp.json (Cursor / VS Code / GitHub Copilot)
{
"servers": {
"figma-mcp-rs": {
"type": "stdio",
"command": "npx",
"args": ["-y", "figma-mcp-rs"]
}
}
}Docker
docker build -t figma-mcp-rs .
docker run -i --rm -p 1998:1998 figma-mcp-rs.mcp.json with Docker:
{
"mcpServers": {
"figma-mcp-rs": {
"command": "docker",
"args": ["run", "-i", "--rm", "-p", "1998:1998", "figma-mcp-rs"]
}
}
}The image listens on 0.0.0.0:1998 (baked into the default CMD), so the Figma plugin connects to ws://127.0.0.1:1998 as usual through the port mapping — keep the host port at 1998 or update the host in the plugin UI. Run one container per plugin connection; for multiple simultaneous MCP clients on one machine prefer the native binary, whose leader election shares a single plugin connection. The self-installed plugin path inside the container is not host-accessible — import the plugin from this repo's plugin/ directory or the release plugin.zip instead.
Server flags: --ip (default 127.0.0.1), --port (default 1998).
2. Install the Figma plugin
The plugin is bundled inside the server binary — no download or build step.
Start the server once (any method above). On startup it writes
manifest.json,dist/code.js, anddist/index.htmlto~/.figma-mcp-rs/plugin/(Windows:%USERPROFILE%\.figma-mcp-rs\plugin\) and logs the path.In Figma Desktop: Plugins → Development → Import plugin from manifest → select
~/.figma-mcp-rs/plugin/manifest.jsonRun the plugin inside any Figma or FigJam file — it connects to the server over
ws://127.0.0.1:1998(host/port configurable in the plugin UI)
If a tool fails with plugin not connected, call get_status — it diagnoses the bridge and returns setup instructions.
Multiple server instances are safe: the first to bind the port becomes leader and owns the plugin connection; others become followers that proxy tool calls and take over automatically if the leader dies.
FigJam & Slides support
The plugin loads in every editor (editorType: ["figma", "figjam", "slides", "dev"]):
Reads work in both:
get_document/get_design_contextserialize FigJam node types (STICKER, CONNECTOR, MARKER, WIDGET, EMBED, MEDIA…)FigJam writes are eight named tools:
create_sticky,create_stickies,create_connector,create_shape_with_text,create_table,create_code_block,auto_arrange,get_board_contentsFigma-only tools (styles, variables, components, prototype reactions, auto-layout) return a clear error in FigJam files
Remaining gaps — Slides, team-library variables/styles (
figma.teamLibrary.*,importVariableByKeyAsync), and anything else unwrapped: useuse_figma
Available Tools
Status
Tool | Description |
| Check whether the plugin bridge is connected; returns setup instructions when it is not. Call this first if any tool fails with |
Escape hatch
Tool | Description |
| Run Plugin API JavaScript inside the file. The code is the body of |
| Run arbitrary Plugin API code in the same sandbox — the code runs as an async function body, with an optional |
Write — Create
Tool | Description |
| Create a frame with optional auto-layout, fill, and parent |
| Create a rectangle with optional fill and corner radius |
| Create an ellipse or circle |
| Create a text node (font loaded automatically) |
| Decode base64 image and place it as a rectangle fill |
| Convert an existing FRAME node into a reusable component |
| Create a Figma Section node to organise frames on a page |
Write — Modify
Tool | Description |
| Update text content of an existing TEXT or STICKER node |
| Set solid fill color (hex) on a node |
| Set solid stroke color and weight on a node |
| Set opacity of one or more nodes (0 = transparent, 1 = opaque) |
| Set corner radius — uniform or per-corner |
| Set auto-layout properties on one or more nodes — direction, padding, gap, alignment, wrap, HUG/FILL sizing, absolute positioning (Figma only) |
| Show or hide one or more nodes |
| Lock/unlock one or more nodes |
| Set absolute rotation in degrees on one or more nodes |
| Change z-order: |
| Set blend mode (MULTIPLY, SCREEN, OVERLAY, …) |
| Set responsive constraints on one or more nodes |
| Move nodes to an absolute x/y position |
| Resize nodes by width and/or height |
| Rename a node |
| Clone a node, optionally repositioning or reparenting |
| Move nodes to a different parent frame, group, or section |
| Group nodes into a GROUP / dissolve groups |
| Bulk rename via find/replace, regex, or prefix/suffix |
| Find and replace text across TEXT nodes in a subtree or page; supports regex |
| Delete one or more nodes permanently |
Write — Prototype (Figma only)
Tool | Description |
| Set prototype reactions (triggers + actions); mode |
| Remove all or specific reactions by index |
Write — Styles (Figma only)
Tool | Description |
| Apply drop shadow / blur effects directly on a node |
| Create named local styles |
| Update any style in place — paint color, text font/size/spacing, effects, grid — plus name and description |
| Bind a variable to a style so the style itself is token-driven |
| Apply an existing local style to a node |
| Delete any style by ID |
Write — Variables (Figma only)
Tool | Description |
| Create a new local variable collection with an optional initial mode |
| Add a new mode to an existing collection (e.g. Light/Dark) |
| Create a variable (COLOR/FLOAT/STRING/BOOLEAN) in a collection |
| Set a variable's value for a mode — a literal or an alias to another variable |
| Rename a variable or collection; set description, scopes, Dev Mode code syntax; rename a mode |
| Apply or clear a collection's mode override on a node or the current page |
| Bind a variable to a node property (fills, strokes, size, spacing, …); omit |
| Delete a variable, an entire collection, or a single mode |
Write — Pages
Tool | Description |
| Add a new page (optional name and index) |
| Delete a page by ID or name |
| Rename a page by ID or current name |
Write — Components & Navigation
Tool | Description |
| Switch the active page by ID or name |
| Swap the main component of an INSTANCE node |
| Detach component instances to plain frames |
Read — Document & Selection
Tool | Description |
| Full current page tree |
| File name, pages, current page |
| All pages (IDs + names) — lightweight |
| Currently selected nodes |
| One node / multiple nodes by ID |
| Depth-limited tree with |
| Find nodes by name substring and/or type |
| All text nodes in a subtree |
| Nodes matching a type list |
| Current viewport center, zoom, visible bounds |
| Prototype reactions on a node |
| Fonts used on the current page, sorted by frequency |
Read — Styles & Variables
Tool | Description |
| Paint, text, effect, and grid styles — with descriptions, publish state, bound variables, and |
| Variable collections, modes, values, aliases, scopes, and code syntax |
| All components + component sets |
| Dev-mode annotations |
| Design tokens (variables + paint styles) as JSON or CSS, with alias |
Export
Tool | Description |
| Base64 image export of any node |
| Export images to disk (server-side write) |
| Multiple frames as one multi-page PDF (server-side merge) |
FigJam
Tool | Description |
| Create a sticky note with text (FigJam only) |
| Create multiple sticky notes at once, with optional grid auto-layout (FigJam only) |
| Create a connector, optionally between two nodes (FigJam only) |
| Create a shape with text — rectangles, circles, diamonds, … (FigJam only) |
| Create a table with optional cell text content (FigJam only) |
| Create a code block with syntax highlighting (FigJam only) |
| Auto-arrange objects in grid, row, or column layout (FigJam only) |
| All objects and connectors on the current FigJam page, with text content and connection data |
MCP Prompts (12)
read_design_strategy, design_strategy, text_replacement_strategy, annotation_conversion_strategy, swap_overrides_instances, reaction_to_connector_strategy, style_audit_strategy, bulk_rename_strategy, design_token_generation_strategy, generate_color_palette, generate_type_scale, generate_component_variants
Claude Skills (15)
skills/ ships the 12 prompts as Claude Code skills plus bridge-troubleshooting (connection diagnostics), figjam-boards (FigJam stickies, shapes, tables, connectors, auto-arrange), and editor-compatibility (Figma/FigJam/Slides tool matrix). Installed automatically via the plugin marketplace; otherwise copy skills/ into your project's .claude/skills/.
Development
make test # cargo test + plugin bun test
make build # release binary + plugin distCI: fmt + clippy + tests (linux amd64/arm64, windows, macos) + plugin typecheck/test/build on every PR.
Releases: conventional commits (
feat:,fix:) on main → release-please opens a version-bump PR (Cargo.toml, Cargo.lock, npm/package.json, CHANGELOG); merging it tagsvX.Y.Zand the same workflow builds the five binaries + plugin.zip, publishes npm, and pushes the multi-arch image toghcr.io/jirayusueb/figma-mcp-rs. Re-run a release build for an existing tag withgh workflow run "Release please" -f tag=vX.Y.Z.Server: Rust (tokio, axum, rmcp). Plugin: TypeScript + SolidJS, built with Vite (UI inlined to
dist/index.html, core IIFEdist/code.js).Toolchain: Bun 1.4.2, TypeScript 7.
The wire protocol (bridge WebSocket frames, follower
/rpc) is kept compatible with the Go reference, so this server also works with the original figma-mcp-go plugin.
Credits
Fork of the architecture and tool design of figma-mcp-go by vkhanhqui — ported to Rust with a SolidJS plugin and FigJam support.
Related Projects
vkhanhqui/figma-mcp-go — the Go reference this port follows
alvinindra/figma-mcp-rust — another Rust port of the same server
grab/cursor-talk-to-figma-mcp — the plugin-bridge approach this lineage comes from
gethopp/figma-mcp-bridge — alternative plugin bridge
License
MIT
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Give AI agents your deeepSpace design system: components, tokens, styles and code mappings.
Build and manage your design system with AI: tokens, themes, components, icons, Figma and code.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to access and manipulate Figma designs, including extracting design systems, creating and debugging UI components, and syncing design tokens bidirectionally.9,800 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI tools to read, edit, check, and export the currently open Figma file locally, with support for design files, FigJam boards, and Slides decks plus quality checks and design-to-code workflows.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, analyze, and modify Figma designs, including bulk style updates, accessibility audits, comment triage, and code generation from designs.679 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to read, create, edit, and organize Figma documents directly through a local plugin bridge, without needing a Figma AI subscription.3Apache 2.0