figma-opencode-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_pingA | Check if the MCP server is alive and the Figma plugin bridge is connected. |
| figma_get_selectionB | Get the list of currently selected nodes in the active Figma file. |
| figma_get_current_pageB | Get information about the current page in the active Figma file. |
| figma_get_node_treeC | Get the node tree starting from the current page or a specific node. |
| figma_export_selection_jsonA | Export the current selection as structured JSON (geometry, layout, typography, colors, spacing, auto layout). |
| figma_create_frameB | Create a new frame node in the current page. |
| figma_create_textB | Create a new text node in the current page. |
| figma_audit_selectionB | Audit the current selection for design system issues (spacing, colors, typography, auto layout, accessibility). |
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 8 tools
Each tool has a clearly distinct purpose: ping for health, getters for page/selection/tree, creators for frame/text, audit for design issues, and export for JSON. No overlap.
All tools follow a consistent 'figma_verb_noun' snake_case pattern, making them predictable and easy to navigate.
8 tools is well-scoped for a Figma design assistant, covering essential reading, creation, auditing, and health checking without being excessive.
Missing update/delete operations for nodes, lack of shape variety (only frame and text), and no style manipulation tools, leaving notable gaps for full design workflows.