Compact Figma MCP with validated batch ops through a local plugin bridge.
io.github.sunhome243/figma-mcp-express — MCP Server
A compact Model Context Protocol (MCP) server that enables AI agents to interact with Figma through a local plugin bridge. It focuses on validated batch operations, and is distributed as the figma-mcp-express project.
🛠️ Key Features
Compact Figma MCP
Local plugin bridge integration
Validated batch operations
🚀 Use Cases
Automating batch actions against Figma from an MCP-compatible client
Running workflows via Claude Code integration (as indicated by compatibility)
⚡ Developer Benefits
MIT-licensed project
Built with Go (badge indicates Go 1.21+)
Available on npm as figma-mcp-express
Works with Claude Code (noted as compatible)
Compatible with Codex (noted as compatible)
⚠️ Limitations
Source data does not include tool list, configuration details, or supported operations beyond “validated batch ops.”
Fast, quota-free, stable Figma automation for coding agents.figma-mcp-express lets Claude Code, Codex, and other local agents read, edit, migrate, audit, screenshot, and prototype inside the real Figma Desktop file. It is built for serious design-system work: batch edits, multi-file routing, large-file reads, visible multi-agent activity, and prototype wiring without burning through official Figma MCP tool-call quotas.
Use it when screenshots and comments are not enough. The agent can inspect actual nodes, components, variables, styles, frames, prototype reactions, and connected files, then make targeted changes in the file designers already use.
Follow AI agents live as they fix issues, edit layouts, and design screens directly in Figma.
Why teams use it
More automation, fewer quota walls. Normal plugin-side work is not capped by the official Figma MCP server's seat-based tool-call limits.
Compact tool surface. Compared with vkhanhqui/figma-mcp-go@fe6cd768 (the intermediate fork baseline used for this measurement), the default tools/list drops from 73 tools / 12,214 o200k_base tokens to 21 tools / 3,283 tokens (73.1% smaller) — less context burned before the agent does any work.
Real Figma context, not screenshots. Agents work with live nodes, components, variables, styles, frames, screenshots, and prototype links in the open Desktop file.
Built for design-system migration. Route a source library and product file through separate channels, then rebuild screens with the right components and tokens.
Made for multi-agent runs. Watch agent activity live, follow one agent's edits, and keep file sessions separated by channel.
Large files stay usable. Big reads spill to disk so agents can inspect only the useful slice instead of flooding the model context.
Prototype automation is part of the workflow. Read prototype flows, set reactions, and set flow starting points.
Capabilities
Watch live agent activity in the Figma plugin.
Build polished Figma screens with built-in AI agent skills.
Route multiple open files through separate channels.
Migrate design systems with real components, variables, and styles.
Read and wire prototype flows directly in the open Figma file.
Good fit
Design system migrations and component-library swaps
Large file audits, cleanup, and token rebinding
Design-to-code handoff that needs real token and component context
Prompt-to-Figma workflows that should use your actual library instead of raw shapes
Prototype audits and wiring for navigation, overlays, transitions, and flow starts
Quick start
1. Install the server
Plugin install is the shortest path.
Claude Code
bash
claude plugin marketplace add sunhome243/figma-mcp-express
claude plugin install figma-mcp-express@figma-mcp-express
In Figma Desktop, go to Plugins -> Development -> Import plugin from manifest....
Select manifest.json from the unzipped plugin folder or from this repo's plugin/ directory.
3. Run it
Open the target file in Figma Desktop.
Start Plugins -> Development -> Figma MCP Express.
Keep the plugin running while the agent works.
If you open multiple files, each file gets its own channel ID for multi-file workflows.
Important limits
Most live tools require the target file to be open in Figma Desktop with the plugin running.
fetch_library_catalog is the main REST-only exception and requires FIGMA_TOKEN.
Plugin execution is still single-threaded per file; the server reduces contention, but it does not make one file fully parallel.
Community kits must be published as a library before import_component_by_key can use them.
Remote follower (beta) is private Tailnet-only. It is not a public MCP URL: keep the leader loopback-only, expose it with Tailscale Serve (never Funnel), and connect the AI client to the follower's local /mcp. See DEV-SETUP.md.
Build from source
For other MCP clients, or if you want to modify the server:
bash
git clone https://github.com/sunhome243/figma-mcp-express.git
cd figma-mcp-express
make build
This produces bin/figma-mcp-express and plugin/dist/.
figma-mcp-express was initially created from an intermediate fork without knowing this earlier provenance. After learning the full lineage, we restored GETHOPP LTD's copyright notice and now credit the original project directly. We value a healthy, transparent open-source ecosystem and aim to make authorship and derivation explicit.
Required third-party copyright notices are preserved in LICENSE. figma-mcp-express is MIT-licensed and permits commercial use.
