figma-custom-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| figma_statusB | Bridge/pairing status for the custom Figma MCP (separate from, and compatible with, Plumb — different port, different plugin). |
| figma_designA | Build or sync a design into Figma from a strict JSON design document (see P0-DESIGN-SCHEMA.md). Supports genuine overlapping/absolute-positioned nodes and local image assets — the two capabilities Plumb cannot provide (see PLUMB_GAP_ANALYSIS.md §5, §15). Unknown/misspelled fields are rejected, not silently ignored. Pass dryRun:true to validate + compile without touching Figma. |
| figma_nodeA | Read back a node's full structure (position, size, fills, strokes, effects, text, layout, children) for verification. Pass nodeId, or omit for the whole current page. |
| figma_patch_nodeA | Patch a subset of properties on an EXISTING node (position, size, rotation, opacity, fill, stroke, radius, effects, blendMode, clip, visible) without touching siblings or re-stating the whole subtree. |
| figma_delete_nodeC | Delete an existing node by id. |
| figma_reorder_nodeA | Change an existing node's z-order among its siblings without a full re-build. |
| figma_screenshotA | Export a node as PNG or SVG at a configurable scale (unlike Plumb's bulk-export path, scale is not hardcoded — see gap analysis §25). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Each tool targets a distinct action (delete, reorder, export, status, design/create, read, patch). The only potential overlap is between figma_design and figma_patch_node, but design is for initial creation/sync while patch is for targeted updates, so the boundary is clear.
All tools use the prefix 'figma_' followed by a descriptive verb_noun pattern (e.g. figma_delete_node, figma_reorder_node). The only minor inconsistency is the verb choice: 'screenshot' is less typical than 'export', and 'status' is a noun rather than an action, but overall the pattern is clear and predictable.
7 tools is well-scoped for a Figma design tool MCP server. Each tool covers a core operation (CRUD, reorder, export, status) without being too many to navigate or too few to be useful.
The server covers essential operations: create (via figma_design), read (figma_node), update (figma_patch_node, figma_reorder_node), delete (figma_delete_node), and export (figma_screenshot). A minor gap is the lack of a dedicated tool for listing node children or searching nodes, but the read tool with nodeId omission provides a reasonable workaround.