figma-opencode-mcp
Connects AI coding agents to a locally open Figma file via a plugin bridge, enabling reading selections, exporting JSON, creating frames and text, and auditing design system heuristics.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@figma-opencode-mcp Get my current selection and export as structured JSON"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
figma-opencode-mcp
Local-first MCP server for OpenCode/Codex that connects AI coding agents to the currently open Figma file through a local plugin bridge.
No Figma API token required. No Figma REST API in default mode. All communication stays on your machine.
Version: v0.2.2 ā fix docs URL in CLI help. Run with a single npx command.
Key Features
š No Figma API token required in default mode
š No data leaves your machine ā local WebSocket bridge
š Read current selection ā get node data from Figma
š Export selection as JSON ā structured data for design-to-code
āļø Create frames and text ā basic write operations
š Audit selection ā design system heuristics (spacing, typography, layout)
š§© Works with OpenCode and Codex via MCP stdio transport
š¦ Run with a single
npxcommand ā no clone or install needed
Related MCP server: Figma Bridge MCP
Important Limitations
ā ļø This does not magically access any private Figma file by URL.
You still need to open the Figma file in Figma.
You must run the local plugin bridge inside the file.
The plugin can only access what Figma Plugin API allows in the current file/session.
Architecture
OpenCode/Codex ā MCP stdio ā WebSocket (127.0.0.1:3845) ā Plugin UI ā Plugin Main ā Figma APISee docs/architecture.md for details.
Quick Start
Option A: Install with npx (recommended)
Run the MCP server directly ā no clone or local build needed:
npx -y figma-opencode-mcp@latestConfigure OpenCode/Codex
OpenCode:
opencode mcp add figma-opencode-mcp -- npx -y figma-opencode-mcp@latestCodex:
codex mcp add figma-opencode-mcp -- npx -y figma-opencode-mcp@latest.mcp.json (any MCP client):
{
"mcpServers": {
"figma-opencode-mcp": {
"command": "npx",
"args": ["-y", "figma-opencode-mcp@latest"]
}
}
}Note: The npm/npx command only installs the MCP server. You still need to import and run the Figma plugin separately (see step 4).
Option B: Local clone (for development)
git clone <repo-url> figma-opencode-mcp
cd figma-opencode-mcp
npm install
npm run buildStart MCP Server:
# Development mode (hot reload)
npm run dev
# Production mode
node dist/index.jsLocal MCP config:
{
"mcpServers": {
"figma-opencode-mcp": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/figma-opencode-mcp/dist/index.js"]
}
}
}4. Run Figma Plugin (required for both options)
Build the plugin:
npm run build:plugin(skip if using npx ā download the plugin from releases)In Figma: Plugins ā Development ā Import plugin from manifest
Select
plugin/manifest.jsonRun the plugin in your Figma file
The plugin will connect to
ws://127.0.0.1:3845Back in OpenCode/Codex, call
figma_ping
Tools
Tool | Description |
| Check connection status |
| Get selected nodes |
| Get current page info |
| Get node tree |
| Export as structured JSON |
| Create a frame |
| Create a text node |
| Audit for design issues |
See docs/tools.md for detailed documentation.
Example Prompts
Use figma_ping to check connection.
Use figma_get_selection to read my current selected frame.
Use figma_export_selection_json and generate a React/Vite component.
Use figma_audit_selection and suggest design-system improvements.Project Structure
figma-opencode-mcp/
āāā src/ # MCP server source
ā āāā index.ts # Entry point
ā āāā mcp/ # MCP layer (server, tools, schemas, handlers)
ā āāā bridge/ # WebSocket bridge (WS server, client, pending requests)
ā āāā shared/ # Shared types (protocol, errors, logger, serialize)
āāā plugin/ # Figma plugin (manifest, code, UI, types)
āāā docs/ # Documentation
āāā examples/ # MCP config examples
āāā scripts/ # Dev/build/verify scripts
āāā README.mdSecurity
No token, no REST API in default mode.
WebSocket binds only to
127.0.0.1.No data sent to external servers.
No eval or shell execution.
No
.envwith secrets.
See docs/security.md.
Roadmap
v0.2.0 ā
npm package packaging with
npxsupport--versionand--helpCLI flagsPlugin packaging (
plugin.zip)Documentation updates for npx install
v0.3.0
figma_extract_design_tokensfigma_generate_react_specfigma_compare_code_with_designfigma_create_componentfigma_apply_auto_layoutfigma_export_svg_png
v0.4.0
Integration profile for
opencode-power-kit/figma-setupslash command/figma-to-reactworkflow/figma-auditworkflowfigma-design-systemskill
v1.0.0
Stable no-token local bridge
Better plugin session management
Better schema docs
License
MIT
Available Tools
8 toolsfigma_audit_selectionB
Audit the current selection for design system issues (spacing, colors, typography, auto layout, accessibility).
Inputs: checkColors, checkSpacing, checkAutoLayout, checkTypography, +1 more.
figma_create_frameB
Create a new frame node in the current page.
Inputs: name (required), width (required), height (required), x, +3 more.
figma_create_textB
Create a new text node in the current page.
Inputs: text (required), x, y, fill, +2 more.
figma_export_selection_jsonA
Export the current selection as structured JSON (geometry, layout, typography, colors, spacing, auto layout).
Inputs: maxDepth, includeStyle, includeLayout, includeChildren.
figma_get_current_pageB
Get information about the current page in the active Figma file.
Inputs: no named parameters.
figma_get_node_treeC
Get the node tree starting from the current page or a specific node.
Inputs: nodeId, maxDepth, includeInvisible.
figma_get_selectionB
Get the list of currently selected nodes in the active Figma file.
Inputs: maxDepth, includeChildren.
figma_pingA
Check if the MCP server is alive and the Figma plugin bridge is connected.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: ping for health, getters for page/selection/tree, creators for frame/text, audit for design issues, and export for JSON. No overlap.
All tools follow a consistent 'figma_verb_noun' snake_case pattern, making them predictable and easy to navigate.
8 tools is well-scoped for a Figma design assistant, covering essential reading, creation, auditing, and health checking without being excessive.
Missing update/delete operations for nodes, lack of shape variety (only frame and text), and no style manipulation tools, leaving notable gaps for full design workflows.
Maintenance
Related MCP Connectors
The Figma MCP server brings Figma design context directly into your AI workflow.
Nifty's MCP server ā exposes tasks, projects, messages, and files as tools for AI agents.
Official MCP server for Agentwork ā delegate tasks to AI agents with human-in-the-loop
Official Fibery MCP server: query and update your workspace from any AI client via OAuth.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceA local MCP server that gives AI agents live access to open Figma files for design handoff and UX writing without API tokens or rate limits.3-
- FlicenseBqualityCmaintenanceLocal MCP server connecting AI clients to the Figma desktop app for inspecting and editing Figma documents via the Plugin API.161-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.81MIT
- AlicenseBqualityBmaintenanceA local MCP server that lets AI assistants inspect, create, and update designs in Figma Desktop through a development plugin, requiring no Figma Personal Access Token or cloud services.121MIT