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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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/Rachit0-glitch/FIGMA-CUSTOM-MCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server