MODEL CONTEXT PROTOCOL SERVER · ALWAYS-ON, EDGE-HOSTED

Figma's docs, spoken fluently by your AI.

A free, unofficial MCP server that lets Claude, ChatGPT, Copilot, or any MCP-capable assistant search and read Figma's live developer documentation — REST API, Plugin API, Widget API, Code Connect, Figma Make/Sites — instead of guessing from stale training data.

See the tools ↓
Connect your AItools/call · streamable-http
// request
tools/call figma_docs_search
{ "query": "Plugin API FrameNode properties", "limit": 5 }
// response (truncated)
{ "count": 5, "results": [
  { "title": "FrameNode", "url": "developers.figma.com/docs/plugins/api/FrameNode/" },
  …
] }
…
TOTAL TOOL CALLS
3
MCP TOOLS EXPOSED
280
DOCS PAGES INDEXED
10
SECTIONS COVERED
0
AUTH REQUIRED
The problem

Documentation drifts. Model weights don't follow it.

Figma's platform moves fast — Code Connect, Figma Make, Figma Sites, and Figma's own Dev Mode MCP server are all newer than most models' training cutoffs, and the Plugin/Widget API surface keeps growing underneath them.

Every assistant answering a REST API or Plugin API question is really answering from a snapshot — often a stale, subtly wrong one. Parameter names shift, endpoints get added, node properties change.

This server sits in front of developers.figma.com and exposes three tools that let an assistant search the real docs, fetch a page's full text on demand, and cite the source URL — instead of reciting a half-remembered API shape.

It runs as a stateless service: a fresh MCP session per request, no accounts, nothing about you retained between calls — the only thing persisted is an aggregate count of how many tool calls it has served.

TRAINING DATA"Widgets use useSyncedState… I think it takes two args" — half right, missing the reset behavior.
TRAINING DATA"Code Connect supports React and…" — silently misses Compose, SwiftUI, HTML.
LIVE DOCSfigma_docs_search → figma_docs_get_page returns the current widgets API reference, verbatim, with a citable URL.
LIVE DOCSfigma_docs_list_sections surfaces Code Connect, Figma Make/Sites, and the Embed Kit as real, browsable categories.
What's inside

Three tools. That's the whole surface.

No config, no OAuth screen, no rate-limit key. Point a client at the endpoint and these become callable immediately.

01 SEARCH

figma_docs_search

Ranked search across the full catalog — titles, URLs, descriptions, and section. The first call in almost every conversation.

{ "query": "widget useSyncedState", "limit": 10 }
02 FETCH

figma_docs_get_page

Fetches a page's readable content (40,000 char cap), restricted to developers.figma.com — REST endpoints, Plugin API node types, Widget API components, guides.

{ "url": "https://developers.figma.com/docs/rest-api/variables/" }
03 BROWSE

figma_docs_list_sections

Lists the top-level categories — REST API, Plugin API, Widget API, Code Connect, Figma Make/Sites, Embeds — for browsing without a query.

{ } → { "sections": [ … ] }
Coverage

Every corner of the Figma developer platform.

280 curated pages across 10 sections — sourced from developers.figma.com's sitemap and verified page fetches.

  • 01
    Getting StartedDeveloper portal home, API comparison, and quickstart guides for the Plugin and Widget APIs.
  • 02
    REST APIFigma's HTTP API: authentication, files, comments, variables, webhooks, components, dev resources, activity/developer logs, payments, discovery, SCIM, and errors.
  • 03
    Plugin API GuidesConceptual guides for building Figma plugins: manifest, UI, publishing, working with text/images/variables, FigJam/Slides/Dev Mode support.
  • 04
    Plugin API ReferenceReference for the Plugin API: the figma global object, node types, shared node properties, and data types.
  • 05
    Widget API GuidesConceptual guides for building FigJam widgets: setup, state & multiplayer, events, prototyping widget UI.
  • 06
    Widget API ReferenceReference for the Widget API: the widget global object, JSX-like components (AutoLayout, Frame, Text, etc), hooks, and types.
  • 07
    Code ConnectLinking Figma design components to their real codebase counterparts (React, SwiftUI, HTML, Compose, Storybook) so Dev Mode shows real code.
  • 08
    Figma Make & Sites (Code in Figma)Building AI-generated code layers, apps, and published sites directly inside Figma (Figma Make, Figma Sites).
  • 09
    Figma's Dev Mode MCP ServerDocs for Figma's own official MCP server, which gives AI coding agents live access to a Figma file's design context (not this docs server).
  • 10
    Embed KitEmbedding Figma files and prototypes in external websites, and the Embed Kit 2.0 JS API.
Get connected

Add it to whatever you already use.

Streamable HTTP, no authentication. Pick your client below.

// .vscode/mcp.json
{
  "servers": {
    "figma-docs": {
      "type": "http",
      "url": "https://figmadocsmcp.mcpbuilders.net/mcp"
    }
  }
}
claude mcp add --transport http figma-docs https://figmadocsmcp.mcpbuilders.net/mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "figma-docs": {
      "url": "https://figmadocsmcp.mcpbuilders.net/mcp"
    }
  }
}
Settings → Connectors → Add custom connector
Name: figma-docs
URL: https://figmadocsmcp.mcpbuilders.net/mcp
Settings → Connectors → Advanced → Add custom connector
URL: https://figmadocsmcp.mcpbuilders.net/mcp
Authentication: None
{
  "tools": [
    {
      "type": "mcp",
      "server_label": "figma-docs",
      "server_url": "https://figmadocsmcp.mcpbuilders.net/mcp",
      "require_approval": "never"
    }
  ]
}
Transport: Streamable HTTP
URL: https://figmadocsmcp.mcpbuilders.net/mcp
Auth: none

Most clients: Command Palette → "MCP: Add Server" → HTTP → paste the URL. Or add the config file manually.