Skip to main content
Glama
KaiUweHella

figma-bridge-mcp

by KaiUweHella

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
figma_connectA

Connect to Figma in Safe Mode (never Yolo). Generates the plugin access key if needed and returns it with plugin import instructions.

figma_statusA

Show bridge/plugin/file/key state. Performs a real plugin round-trip by default; REST validation is opt-in.

figma_pairingA

Show the Figma plugin access key (paste it into the Figma Bridge plugin). Pass rotate:true to generate a fresh key (requires reconnect).

figma_runA

Run a Capability Catalog-approved engine command. Discover commands with figma_reference {name:"capabilities"}. Append --help to any command for its syntax. Note: node tree defaults to depth 3 — pass -d for deeper trees.

figma_renderB

Render JSX into the open Figma design.

figma_selectionB

Read the current Figma selection and reuse its id.

figma_historyA

Local change history of this machine's Figma sessions, from the audit log every figma_run/figma_render is recorded in. Filter by nodeId to see everything that touched a node. Optionally merges git history of generated code files for a combined design+code changelog. Note: node-id matching is text-based, so numbers like "12:30" in free text can match too.

figma_commentsA

Read or post Figma comments via the optional REST layer (design review feedback lives here — read it, act on it, reply with what you changed). action:'list' returns all comments with ids, authors, node anchors and resolved state. action:'post' needs message (+ optional nodeId anchor or replyTo thread id) and ALWAYS requires confirm:true after a preview — comments are visible to other people. Without a configured REST token this tool only explains the setup.

figma_inspectA

Inspect one node's geometry, paint, effects, component context and text style as YAML.

figma_referenceB

Offline Plugin API reference. Special topics: capabilities, variable-scopes, workflow, workflow:design-to-code, workflow:code-to-figma.

figma_screenshotA

MANDATORY first step: save/read the node PNG, then compare the finished build to it.

figma_specB

Exact per-layer text, identity, layout, native CSS, paint, token and asset facts. Copy; never invent. Map structure, then pull style by node id.

Prompts

Interactive templates invoked by user choice

NameDescription
design-to-codeImplement a Figma node faithfully in the current project with scoped reads, source assets and pixel verification.
code-to-figmaCreate or update a componentized Figma view from code with semantic capture, token bindings and visual verification.
create-figma-componentCreate or update a reusable Figma component set from code with variants, properties, tokens and durable identity.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/KaiUweHella/figma-bridge-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server