Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@figma-developer-docs-mcp How do I create a TextNode using the Figma Plugin API?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
An MCP (Model Context Protocol) server that provides AI coding assistants with structured access to the complete Figma developer documentation.
Section | Pages | Content |
Plugin API | 450 | Node types, properties, methods, guides |
Widget API | 78 | Components, hooks, types, guides |
REST API | 51 | Endpoints, authentication, webhooks, SCIM |
Figma MCP Server | 23 | Setup, tools, troubleshooting |
Code (Figma Make) | 19 | Code layers, properties, guidelines |
Code Connect | 18 | React, SwiftUI, Compose, CI/CD |
Embeds | 8 | Embed kit, security, API |
Total | 649 |
Related MCP server: Figma MCP Server
claude mcp add figma-developer-docs -- npx figma-developer-docs-mcpAdd to your claude_desktop_config.json:
{
"mcpServers": {
"figma-developer-docs": {
"command": "npx",
"args": ["figma-developer-docs-mcp"]
}
}
}npx figma-developer-docs-mcpThe server communicates over stdio using the MCP protocol.
read-figma-developer-docs-indexReturns the full documentation index — all sections and page listings. Use this first to discover what's available.
read-figma-developer-docs-pagesReads specific documentation pages by path. Accepts an array of paths from the index.
paths: ["/docs/plugins/api/TextNode", "/docs/plugins/working-with-text"]search-figma-developer-docsFull-text search across all documentation. Returns matching pages with excerpts.
query: "createImage"
section: "plugins" // optional: limit to a section
maxResults: 10 // optional# Install dependencies
npm install
# Build
npm run build
# Re-scrape documentation (requires internet)
npm run scrape
# Run locally
node dist/index.jsThe documentation is scraped from developers.figma.com and converted to Markdown files organized by section. The MCP server reads these files on demand and serves them through three tools: index, read, and search.
The scraped docs are included in the npm package so the server works offline with no network requests.
MIT
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.
Inputs: no named parameters.
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.
Inputs: paths (required).
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.
Inputs: query (required), section, maxResults.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Access and search Branch's official API documentation directly within any AI agent or client.
Tailor Platform for AI assistants: search, list and read the platform documentation.
Provides AI assistants with direct access to Mapbox developer APIs and documentation.
Find, write, publish and check pages and API references in your DeveloperHub docs from an AI client
