Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Figma MCP Express

by sunhome243version 2.8.1i★ –iRuns on your computer
Registry nameio.github.sunhome243/figma-mcp-express

Install

Overview

Description from the maker (original English)

Compact Figma MCP with validated batch ops through a local plugin bridge.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Design, images & audio

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "figma-express": {
      "command": "npx",
      "args": [
        "-y",
        "figma-mcp-express"
      ]
    }
  }
}

Run this in your terminal

claude mcp add figma-express -- npx -y figma-mcp-express

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "figma-express": {
      "command": "npx",
      "args": [
        "-y",
        "figma-mcp-express"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "figma-express": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "figma-mcp-express"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account sunhome243, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Design, images & audioi

  • More stars than 0% of the other 2789 servers in this category
  • Published to the registry more recently than 21% of the other 2789 servers in this category
  • Basic checks equal to or better than 100% of the other 2789 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Figma MCP Express safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (2.8.1) reached the registry 3 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Figma Context MCP, Claude Real Video, Figma MCP Server

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Figma Context MCP

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

by GLipsWidely used↓ 161.2K/wk★ 16.2KUpdated 5 months ago

Runs on your computer

Claude Real Video

Let any LLM watch a video locally — and search everything it has ever watched.

by HUANGCHIHHUNGLeoWidely used↓ 1.1K/wk★ 2.3KUpdated 2 months ago

Runs on your computer

Figma MCP Server

Figma’s official server gives AI your design data so it can turn designs into code or describe them accurately. Connects to Figma’s cloud.

by figmaGrowing★ 2.2KUpdated 13 months ago

Runs in the cloud✓ mcp.figma.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

figma-mcp-express

Fast, quota-free, stable Figma automation for coding agents. figma-mcp-express lets Claude Code, Codex, and other local agents read, edit, migrate, audit, screenshot, and prototype inside the real Figma Desktop file. It is built for serious design-system work: batch edits, multi-file routing, large-file reads, visible multi-agent activity, and prototype wiring without burning through official Figma MCP tool-call quotas.

Use it when screenshots and comments are not enough. The agent can inspect actual nodes, components, variables, styles, frames, prototype reactions, and connected files, then make targeted changes in the file designers already use.

Demo

Watch the demo video

Follow AI agents live as they fix issues, edit layouts, and design screens directly in Figma.

Why teams use it

  • More automation, fewer quota walls. Normal plugin-side work is not capped by the official Figma MCP server's seat-based tool-call limits.
  • Compact tool surface. Compared with vkhanhqui/figma-mcp-go@fe6cd768 (the intermediate fork baseline used for this measurement), the default tools/list drops from 73 tools / 12,214 o200k_base tokens to 21 tools / 3,283 tokens (73.1% smaller) — less context burned before the agent does any work.
  • Real Figma context, not screenshots. Agents work with live nodes, components, variables, styles, frames, screenshots, and prototype links in the open Desktop file.
  • Built for design-system migration. Route a source library and product file through separate channels, then rebuild screens with the right components and tokens.
  • Made for multi-agent runs. Watch agent activity live, follow one agent's edits, and keep file sessions separated by channel.
  • Large files stay usable. Big reads spill to disk so agents can inspect only the useful slice instead of flooding the model context.
  • Prototype automation is part of the workflow. Read prototype flows, set reactions, and set flow starting points.

Capabilities

  • Watch live agent activity in the Figma plugin.
  • Build polished Figma screens with built-in AI agent skills.
  • Route multiple open files through separate channels.
  • Migrate design systems with real components, variables, and styles.
  • Read and wire prototype flows directly in the open Figma file.

Good fit

  • Design system migrations and component-library swaps
  • Large file audits, cleanup, and token rebinding
  • Design-to-code handoff that needs real token and component context
  • Prompt-to-Figma workflows that should use your actual library instead of raw shapes
  • Prototype audits and wiring for navigation, overlays, transitions, and flow starts

Quick start

1. Install the server

Plugin install is the shortest path.

Claude Code

claude plugin marketplace add sunhome243/figma-mcp-express

claude plugin install figma-mcp-express@figma-mcp-express

Codex

codex plugin marketplace add sunhome243/figma-mcp-express

codex plugin add figma-mcp-express@figma-mcp-express

2. Import the Figma Desktop plugin
  1. Download plugin.zip or build from source.
  2. In Figma Desktop, go to Plugins -> Development -> Import plugin from manifest....
  3. Select manifest.json from the unzipped plugin folder or from this repo's plugin/ directory.
3. Run it
  1. Open the target file in Figma Desktop.
  2. Start Plugins -> Development -> Figma MCP Express.
  3. Keep the plugin running while the agent works.
  4. If you open multiple files, each file gets its own channel ID for multi-file workflows.

Important limits

  • Most live tools require the target file to be open in Figma Desktop with the plugin running.
  • fetch_library_catalog is the main REST-only exception and requires FIGMA_TOKEN.
  • Plugin execution is still single-threaded per file; the server reduces contention, but it does not make one file fully parallel.
  • Community kits must be published as a library before import_component_by_key can use them.
  • Remote follower (beta) is private Tailnet-only. It is not a public MCP URL: keep the leader loopback-only, expose it with Tailscale Serve (never Funnel), and connect the AI client to the follower's local /mcp. See DEV-SETUP.md.

Build from source

For other MCP clients, or if you want to modify the server:

git clone https://github.com/sunhome243/figma-mcp-express.git

cd figma-mcp-express make build

This produces bin/figma-mcp-express and plugin/dist/.

Add it to your .mcp.json:

{

"mcpServers": { "figma-mcp-express": { "command": "/absolute/path/to/bin/figma-mcp-express", "args": ["--port", "1994"] } } }

Restart your MCP client after building.

Advanced environment variables

FIGMA_TOKEN

Most workflows do not need a token. Live read/write tools talk directly to Figma Desktop through the plugin.

You only need FIGMA_TOKEN for REST-backed library catalog lookups such as fetch_library_catalog.

  • Generate it in Figma at Account Settings -> Personal access tokens
  • Read-only file access is enough for catalog lookup
  • Treat it like a password and never commit it

If you installed from the marketplace, set it in your shell profile:

echo 'export FIGMA_TOKEN=your_token_here' >> ~/.zshrc

source ~/.zshrc

If you built from source, you can either export it in your shell or place it in a local .env file:

cat <<'EOF' > .env

FIGMA_TOKEN=your_token_here EOF

Shell environment variables take precedence over .env.

VariableDefaultDescription
FIGMA_TOKEN-Required only for fetch_library_catalog.
FIGMA_MCP_TOOL_PROFILEcorecore keeps the compact default tool surface. full restores the legacy compatibility/debugging surface.
FIGMA_MCP_TOOL_SCHEMA_MODEcompactcompact trims tools/list descriptions to reduce MCP context tokens. Use verbose for full in-schema guidance.
FIGMA_MCP_BATCH_MAX_OPS200Maximum top-level batch.ops entries accepted before plugin execution.
FIGMA_MCP_BATCH_MAX_BYTES2097152Maximum encoded batch.ops payload size in bytes before plugin execution.
FIGMA_MCP_STDIO_WORKERS16Number of stdio tool-call workers. Server-local tools can run concurrently; plugin-facing calls still serialize per Figma file.
FIGMA_MCP_STDIO_QUEUE1000Buffered stdio tool-call queue size before mcp-go falls back to synchronous handling.
FIGMA_MCP_SPILL_BYTES25000Response size threshold. Larger responses spill to .figma-mcp-cache/.
FIGMA_MCP_TIMEOUT120Inactivity ceiling in seconds for lightweight ops. Resets on each progress heartbeat.
FIGMA_MCP_READ_TIMEOUT600Inactivity ceiling in seconds for heavy reads and batch. Resets on each progress heartbeat.
FIGMA_MCP_STALL_THRESHOLD45Seconds an op may hold a channel's serial slot with no progress before a new call on that channel is fast-rejected.

More docs

  • TOOLS.md for the full tool catalog
  • ARCHITECTURE.md for queueing, routing, spill-to-disk, and recovery behavior
  • DEV-SETUP.md for local build, rebuild, and test instructions

Credits

The original bridge architecture and implementation underlying this project were created by GETHOPP LTD in gethopp/figma-mcp-bridge@82b28bc and released under the MIT License.

figma-mcp-express was initially created from an intermediate fork without knowing this earlier provenance. After learning the full lineage, we restored GETHOPP LTD's copyright notice and now credit the original project directly. We value a healthy, transparent open-source ecosystem and aim to make authorship and derivation explicit.

Required third-party copyright notices are preserved in LICENSE. figma-mcp-express is MIT-licensed and permits commercial use.

Ask PopNx