What is figma-console?

An MCP connection that gives a coding agent access to Figma, a collaborative design application, through its plugin interface. The listing says it supports design files and related design-management tasks.

Use it for Figma-related work such as design tokens, variables, components, version-history comparisons, accessibility checks, FigJam, and Slides. The listing says it can run through a local desktop bridge or a remote setup.

It connects coding-agent work with Figma so design information can be accessed and handled from the agent’s tools.

figma-console — MCP server by noemuch

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add mcp/noemuch/bridge/figma-console

Clone the repo

git clone --depth 1 https://github.com/noemuch/bridge

Made for: Claude Code, Codex, Cursor, Gemini CLI, OpenCode.

Or install bridge, the plugin that ships this one along with the rest of its 5 skills, 1 hook, 1 MCP server.

Per session not measured What this adds to a session before it is invoked.

When invoked not measured Not applicable: nothing here is loaded into a session.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Security

Grade A, and why

figma-console scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.mcp.json · 13 lines

What it actually says

{
  "figma-console": {
    "command": "npx",
    "args": [
      "-y",
      "figma-console-mcp@latest"
    ],
    "env": {
      "FIGMA_ACCESS_TOKEN": ""
    },
    "description": "Figma Console MCP — gives Claude native access to Figma Desktop via Plugin API. Required for design generation."
  }
}

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

3d ago First seen · 13 lines scan A 4cc999d4d553

Subscribe to this mod's changes

figma-console is an MCP server published in the GitHub repository noemuch/bridge (156 stars, last pushed 3mo ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Design and UX claude-code design-system figma figma-mcp mcp

figma-console

Getting it into your agent

Grade A, and why

Nothing flagged

What it actually says

What this file has done since we first saw it

Other mcp servers, from other repositories

figma-mcp-bridge

figma-desktop

canicode

figma

figma-ui-mcp

figwright