Schema | figma-bridge-mcp

figma-bridge-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`DAEMON_PORT`	No	Explicit port for the local daemon. Disables the automatic fallback range 3456-3460. Values outside 3456-3460 are unsupported.
`FIGMA_REST_TOKEN`	No	Optional Figma personal access token for the REST add-on (version history, comments, library metadata). Overrides the stored token file when set.
`FIGMA_WRITE_CONFIRM`	No	When set to '1', write commands require an explicit confirm:true parameter. Reads pass freely; mutations are gated.
`FIGMA_BRIDGE_EXTRA_ROOTS`	No	Colon-separated (macOS/Linux) or semicolon-separated (Windows) list of additional workspace root directories allowed for file access, in addition to the launch directory.
`DESIGN_CAPTURE_CACHE_BYTES`	No	Maximum total bytes for the in-memory Design Capture cache (default 8 MiB).	8388608
`FIGMA_BRIDGE_IMAGE_ORIGINS`	No	Comma-separated list of exact HTTPS origins allowed for remote raster images in figma_render JSX.
`DESIGN_CAPTURE_CACHE_ENTRIES`	No	Maximum number of entries in the in-memory Design Capture cache.	8
`FIGMA_BRIDGE_STORYBOOK_ORIGINS`	No	Comma-separated list of exact HTTPS origins approved for Storybook mapping (map storybook command).
`FIGMA_BRIDGE_IMAGE_PRIVATE_ORIGINS`	No	Comma-separated list of exact HTTP origins (private or loopback) allowed for remote raster images in figma_render JSX.
`FIGMA_BRIDGE_STORYBOOK_PRIVATE_ORIGINS`	No	Comma-separated list of exact HTTP origins (private network) approved for Storybook mapping.

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}
`prompts`	{}

Functions exposed to the LLM to take actions

Name	Description
figma_connectC	Connect Safe Mode; recover the plugin, create its key, or show setup.
figma_statusB	This Figma Bridge only: round-trip status, write policy, optional REST check.
figma_pairingA	Show the plugin key; rotate:true replaces it and restarts the daemon.
figma_runB	Run an approved command. See figma_reference {name:"capabilities"} or --help.
figma_renderC	Render one JSX value or roots[] batch into Figma.
figma_selectionB	Read the current Figma selection and reuse its id.
figma_historyB	Private command history, git/Figma versions and snapshot diff; payloads omitted.
figma_commentsA	REST comments: list feedback; post/reply always previews and needs confirm:true. Missing token returns setup.
figma_inspectA	Inspect node geometry, paint, effects, component and text facts as YAML.
figma_referenceB	Offline API reference plus capabilities, fidelity, variable scopes and workflows.
figma_screenshotB	MANDATORY: save/read the node PNG before comparing the build.
figma_specA	Exact layer facts; never invent. nodeIds[] batches 8 reads behind one approval.

Interactive templates invoked by user choice

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

Contextual data attached and managed by the client

Name	Description
No resources

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