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 "Install 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-mcpGet 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: figmind
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
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/laivannha0202/figma-opencode-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server