Skip to main content
Glama
figma-opencode-mcp

figma-opencode-mcp

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

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 API

See docs/architecture.md for details.

Quick Start

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

Available Tools

8 tools
figma_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

    A3.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    All tools follow a consistent 'figma_verb_noun' snake_case pattern, making them predictable and easy to navigate.

    Tool Count5/5

    8 tools is well-scoped for a Figma design assistant, covering essential reading, creation, auditing, and health checking without being excessive.

    Completeness3/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI tools to read and write Figma designs via a plugin bridge, bypassing the Figma REST API and rate limits.
      81
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A 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.
      12
      1
      MIT