figma-opencode-mcp
Local-first MCP server that connects AI coding agents to the currently open Figma file through a local plugin bridge, requiring no Figma API token.
README
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
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 API
See 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@latest
Configure OpenCode/Codex
OpenCode:
opencode mcp add figma-opencode-mcp -- npx -y figma-opencode-mcp@latest
Codex:
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 build
Start MCP Server:
# Development mode (hot reload)
npm run dev
# Production mode
node dist/index.js
Local 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.json - Run the plugin in your Figma file
- The plugin will connect to
ws://127.0.0.1:3845 - Back in OpenCode/Codex, call
figma_ping
Tools
| Tool | Description |
|---|---|
figma_ping |
Check connection status |
figma_get_selection |
Get selected nodes |
figma_get_current_page |
Get current page info |
figma_get_node_tree |
Get node tree |
figma_export_selection_json |
Export as structured JSON |
figma_create_frame |
Create a frame |
figma_create_text |
Create a text node |
figma_audit_selection |
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.md
Security
- 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 flags- Plugin 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
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。