figma-opencode-mcp

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.

Category
Visit Server

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 npx command — 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)

  1. Build the plugin: npm run build:plugin (skip if using npx — download the plugin from releases)
  2. In Figma: Plugins → Development → Import plugin from manifest
  3. Select plugin/manifest.json
  4. Run the plugin in your Figma file
  5. The plugin will connect to ws://127.0.0.1:3845
  6. 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 .env with secrets.

See docs/security.md.

Roadmap

v0.2.0 āœ…

  • npm package packaging with npx support
  • --version and --help CLI flags
  • Plugin packaging (plugin.zip)
  • Documentation updates for npx install

v0.3.0

  • figma_extract_design_tokens
  • figma_generate_react_spec
  • figma_compare_code_with_design
  • figma_create_component
  • figma_apply_auto_layout
  • figma_export_svg_png

v0.4.0

  • Integration profile for opencode-power-kit
  • /figma-setup slash command
  • /figma-to-react workflow
  • /figma-audit workflow
  • figma-design-system skill

v1.0.0

  • Stable no-token local bridge
  • Better plugin session management
  • Better schema docs

License

MIT

Recommended Servers

playwright-mcp

playwright-mcp

A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.

Official
Featured
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.

Official
Featured
Local
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.

Official
Featured
Local
TypeScript
VeyraX MCP

VeyraX MCP

Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.

Official
Featured
Local
graphlit-mcp-server

graphlit-mcp-server

The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.

Official
Featured
TypeScript
Kagi MCP Server

Kagi MCP Server

An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.

Official
Featured
Python
E2B

E2B

Using MCP to run code via e2b.

Official
Featured
Neon Database

Neon Database

MCP server for interacting with Neon Management API and databases

Official
Featured
Exa Search

Exa Search

A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.

Official
Featured
Qdrant Server

Qdrant Server

This repository is an example of how to create a MCP server for Qdrant, a vector search engine.

Official
Featured