Reqwise Figma 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 | Rich connection diagnostics for the Figma bridge (never a bare boolean): plugin connection, leader/follower mode, port, heartbeat, queue, sessions, and an ordered list of concrete next-step hints when something is off. |
| figma_readA | Read the Figma canvas with a token-frugal response. Choose an operation and pass its params. layout_audit is the structured verify tool (declared vs rendered bounds, overflow, clipping, truncation). read_selection deep-reads the current selection in one call — the entry point of the selection-first edit-in-place lifecycle (read_selection → figma_write modify → layout_audit). |
| figma_writeA | Execute modern-ES JavaScript in a sandbox against the figma.* proxy to draw/modify the canvas. |
| figma_rulesA | One-call design-system rule sheet as markdown: styles + variables + components, fetched in parallel. Read before drawing so you reuse tokens/components instead of hardcoding. |
| figma_docsA | On-demand documentation for this API and its safe-by-default rules. Sections: rules | layout | api | tokens | icons | recipes. |
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: docs for API reference, read for canvas reading, rules for design systems, status for diagnostics, and write for modifications. No overlap.
All tools follow a consistent figma_verb naming pattern (figma_docs, figma_read, figma_rules, figma_status, figma_write), making it easy to infer functionality.
5 tools is well-scoped for a Figma MCP server, covering essential operations without unnecessary bloat.
The set covers reading, writing, documentation, rules, and status. While minor operations like explicit deletion or search are missing, the core lifecycle is covered.