figma-developer-docs-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 |
|---|---|
| read-figma-developer-docs-indexA | Read the Figma developer documentation index. Returns all documentation sections (Plugin API, Widget API, REST API, Code Connect, Embeds, Figma MCP Server, Code/Make) with page listings. Use this first to discover what documentation is available, then use read-figma-developer-docs-pages to read specific pages. |
| read-figma-developer-docs-pagesA | Read specific pages of the Figma developer documentation. Provide page paths from the index (e.g., '/docs/plugins/api/TextNode', '/docs/rest-api/authentication'). Returns the full markdown content of each requested page. You can request multiple pages at once. |
| search-figma-developer-docsA | Search across all Figma developer documentation for a keyword or phrase. Returns matching page paths and relevant excerpts. Useful when you know what you're looking for but not which page it's on. |
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 3 tools
Each tool has a clearly distinct purpose: one reads the index to discover available documentation, one reads specific pages for detailed content, and one searches across all documentation. There is no overlap in functionality, making it easy for an agent to select the right tool based on the task.
All tool names follow a consistent verb_noun pattern with hyphens: 'read-figma-developer-docs-index', 'read-figma-developer-docs-pages', and 'search-figma-developer-docs'. This predictability enhances usability and reduces confusion.
Three tools are well-scoped for the server's purpose of accessing Figma developer documentation, covering discovery, reading, and searching. While slightly minimal, each tool earns its place, and there is no bloat or obvious missing functionality for this focused domain.
The tool set provides complete coverage for the domain of accessing documentation: it allows agents to discover available docs via the index, read specific pages for detailed information, and search across all content when needed. There are no gaps that would cause agent failures in typical documentation workflows.