Mirra
Provides two-way integration with Figma through its Plugin API. It lets agents read the design selection or node tree and render or patch frames, text, shapes, instances, SVGs, and images; find and select layers; manage pages; export screenshots and assets; and read or define variables, modes, and styles.
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.
Two-way MCP server for Figma: an agent reads a design or a FigJam board and renders one back through the Figma Plugin API, so it needs no REST token and has no monthly call limit.
https://github.com/user-attachments/assets/f736473e-24c4-486f-980d-e6c90bf4d63a
Install
npx @ttsalpha/mirra initThen restart your agent.
Requires Figma Desktop (macOS or Windows) and Node 24+.
Adds Mirra to Claude Desktop, Claude Code, Cursor, VS Code, Antigravity and Codex / ChatGPT desktop (
--no-configskips)Figma open during
init: import by hand, Plugins → Development → Import plugin from manifest… →~/.mirra/plugin/manifest.jsonUpgrading: run
initagain
Related MCP server: figma-mcp
Use
Open a Figma or FigJam file
Run Plugins → Development → Mirra
Keep the panel open
The panel reads Disconnected until your agent has started Mirra. Open your agent; if the panel
still doesn't connect, run npx @ttsalpha/mirra doctor.
Tools
Tool | What it does |
| Build a whole screen, or a FigJam board, from one declarative tree |
| Read the selection, or a node, back as that same tree |
|
|
| Locate layers by name, kind or key, and select them |
| List the pages, add one, or switch to one |
| Export a layer as PNG and hand the image back |
| List variables and styles, with the |
| Create or update variables, modes, aliases and paint/text/effect styles |
| Write layers to disk as PNG or SVG |
| Check the connection and report the open file and editor |
| Run Plugin API code; off by default, see below |
Tree format
mirra_render and mirra_read share one format, so an agent can write code from what it reads.
Nodes:
frame,text,rect,ellipse,instance,svg,imageFlexbox-like:
layout: {dir, gap, pad, …}w/h: a number,"fill"or"hug""$name"binds a field to a variablekeyletsmirra_patchaddress a node later
{
"type": "frame",
"key": "card",
"layout": { "dir": "vertical", "gap": 12, "pad": 16 },
"fill": "#ffffff",
"radius": 12,
"children": [
{ "type": "text", "text": "Welcome back", "size": 24 },
{ "type": "rect", "w": "fill", "h": 1, "fill": "#eeeeee" }
]
}FigJam
Nodes:
section,sticky,shape,connector,table,code,link,gifA board is one
section; FigJam has no frames, auto layout or variablesPlace a node with
at: {x, y}, or let the section'slayoutplace its childrenA connector joins nodes by
keyand routes itselfmirra_define_tokensand"$name"need a Figma Design fileStamps, highlights, washi tape and widgets: found with
mirra_find, never created or read
Configuration
Variable | What it does |
| Pin one port instead of scanning 51730–51739 |
| Directory that tool file paths resolve from; paths outside it are refused |
| Register |
| Accept one more browser origin on the socket |
Unset, MIRRA_ROOT falls back to the working directory. Set it for agents that start the server
outside a project, such as Claude Desktop.
Running arbitrary code
mirra_execruns any Plugin API code the agent writesNeeds two keys:
MIRRA_ALLOW_EXECon the server, and Allow code execution ticked in the panel (reset on every run)
claude mcp add -s user Mirra-exec -e MIRRA_ALLOW_EXEC=1 -- npx -y @ttsalpha/mirra serveHow it works
Agent ⇄ stdio ⇄ MCP server ⇄ ws://localhost:51730 ⇄ plugin ⇄ FigmaThe socket listens on loopback and rejects browser origins other than Figma's
No authentication against other processes running as you while the plugin is open
Development
packages/schema holds the tree and wire protocol, packages/plugin the Figma side,
packages/server the MCP server and CLI. Tests run against a fake of the Figma sandbox, so
they don't need Figma open. The fake doesn't reproduce FigJam's quirks: try FigJam changes in a
real FigJam file.
License
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
Design canvas for agents: create, edit, render and export Figma-shaped designs over MCP.
Give AI agents your deeepSpace design system: components, tokens, styles and code mappings.
Access and maintain design system docs, tokens, components, skills, and contexts across any project.
Give your AI agents a design superpower. Generate, edit, and publish publication-grade decks, reports, landing pages, resumes, and marketing visuals directly within your agent workflow. Delivering frontier-level design quality at 3× the speed and 53× lower cost -from conversational prompt to live link or vector PDF in minutes.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Figma to create, read, and manage designs using the Figma REST API and a dedicated plugin. It supports advanced features like UI generation from text, webpage reconstruction in Figma, and design token synchronization with codebases.20MIT
- FlicenseBqualityDmaintenanceEnables AI agents to read, inspect, and export Figma designs programmatically. Provides tools for listing components, styles, and exporting assets in various formats.51-
- AlicenseAqualityBmaintenanceEnables an agent to read, edit, and build Figma designs from scratch — including style guides, variables, components, and screens — through a local plugin bridge to the open file's Plugin API, with no Figma token or REST API calls.211MIT
- AlicenseNot gradedqualityCmaintenanceEnables a locally run agent or script to read and write a real Figma layer tree through a local bridge — inspecting node structure and variables, exporting screenshots into the model's context, and performing batched create/update/move/rename/delete operations that collapse into a single undo step. All traffic stays on localhost between the bridge and the Figma plugin, with design-token auditing, binding, and creation included.MIT