Unified 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 |
|---|---|
| unified_statusB | Return current normalized health for Plumb and Custom backends plus active backend detection. |
| unified_backendsB | Return known Unified MCP backends and their capability summaries. |
| unified_active_backendA | Return only the currently detected active Figma backend. |
| unified_probe_backendA | Run a safe read-only diagnostic through one backend: plumb or custom. |
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 4 tools
unified_status and unified_active_backend clearly overlap—both report active backend detection, making one redundant. unified_backends and unified_probe_backend are more distinct, but boundaries between status, backends, and probing are not crisp, causing potential misselection.
All tools share the 'unified_' prefix and use snake_case, creating a predictable pattern. Minor inconsistency exists because three are noun-based (status, backends, active_backend) while probe_backend is verb+noun, but overall naming remains coherent and easily scannable.
Four tools is within the ideal range for a focused server, but the overlap between status and active_backend reduces efficiency. Still, the count is not excessive and each tool has a named purpose, even if some purposes are redundant.
The server appears scoped to backend status and diagnostic coverage; it includes health normalization, capability listing, active detection, and probing. It lacks operations like switching backends or configuration, but for a read-only status server, coverage is largely sufficient.