figma-mcp
Figma MCP
Use the official remote server https://mcp.figma.com/mcp through each host's native registration. Authentication belongs to that host's OAuth flow. The user only remembers /figma-mcp ($figma-mcp in Codex); handle host discovery, OAuth state, identity, and readiness internally. On failure, report one failing layer and one required action.
Pick the proof before calling a tool
Most invocations are /figma-mcp <figma URL> <UI task> on the current account in one host, whether that task is inspecting the design or implementing/matching it. That is the read-only fast path: the first requested official read proves server discovery, tool availability, and authentication, so a separate whoami only adds a round trip.
| Invocation payload | Proof |
|---|---|
Figma URL or fileKey, current account, one host, read-only — inspecting, implementing, or matching a design |
First requested read (below); no whoami |
Bare /figma-mcp (readiness only) |
One whoami; reply only FIGMA_MCP_READY |
| Named account, account switch, recovery, write, or multi-host acceptance | One whoami; compare privately when an account is named |
File needed but no URL/fileKey |
Stop; ask for the URL (FILE_ACCESS: UNVERIFIED) |
On task success, continue the requested work; do not emit FIGMA_MCP_READY or identity details mid-task. Server configuration, an OAuth page, a callback, and a tool list are separate evidence layers; none of them replaces the required call.