figma-ui-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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| figma_statusA | Check whether the Figma plugin bridge is connected. Always call this first to confirm the plugin is running before any other tool. |
| figma_writeA | Execute JavaScript code to CREATE or MODIFY designs in Figma. ⚠️ MANDATORY: Call figma_docs BEFORE writing any design code. Skipping figma_docs causes hardcoded colors, wrong sizing, broken layouts, and low-quality UI. Use the |
| figma_readA | READ design data from Figma — extract node trees, colors, typography, spacing, and screenshots. Use to understand an existing design before generating code, or to inspect what's on the canvas. |
| figma_docsA | Get the API reference and design rules for figma_write. Call with no args first — returns quick-start guide + critical rules. Then load specific sections as needed: section='rules' (design principles, token rules, layer order, component-first), section='layout' (auto-layout, button/card/badge/progress/mobile rules), section='api' (create/modify/delete/clone/batch/read operations + workflow), section='tokens' (variables, multi-mode, paint styles, text styles), section='icons' (loadImage, loadIcon, loadIconIn, icon libraries, coloring, sizing). Always call figma_docs BEFORE any figma_write code. |
| figma_rulesA | Generate a design system rule sheet from the current Figma file — aggregates color tokens, typography styles, variables (all modes), and component catalog into a single markdown block. Equivalent to official Figma MCP's create_design_system_rules. Call once at the start of a design-to-code session to give the AI full context: what tokens to use, what text styles exist, which components are available. Re-run when the design system changes. |
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 5 tools
Each tool has a clearly distinct purpose: documentation retrieval, reading design data, generating rule sheets, checking connection status, and executing write operations. The slight overlap between figma_docs and figma_rules is mitigated by their different scopes (general reference vs. file-specific aggregation), so no ambiguity exists.
All tools follow a consistent 'figma_verb' pattern (docs, read, rules, status, write). The verbs are clear and indicative of each tool's function, making the set predictable and easy to understand.
With 5 tools, the server covers the essential operations for Figma interaction (status, read, write, documentation, rule generation) without unnecessary bloat. The count is well-scoped and each tool earns its place.
The tool set covers the primary use cases: reading design data, writing/modifying designs via code, generating design rules, checking connection, and accessing documentation. While the write tool is extremely versatile, dedicated tools for specific operations like deleting or listing components are missing, but the JavaScript execution fills that gap. Minor gaps remain for very specialized tasks.