Subchapter 27.1
references/setup.mdMarkdown3 KBView on GitHub
The Figma MCP server is not bundled with this plugin. It is Figma’s own product, and the user installs and authenticates it themselves. This reference is for the moments when something isn’t working and a quick check helps unblock the work.
Figma exposes the MCP server in two flavors:
Confirm with the user which one they’re using when troubleshooting — the tool surface differs.
The client (Claude Code in this plugin’s context) must support MCP servers, and the user must have configured the Figma server in their client’s MCP settings. Configuration lives in the user’s environment (not in this plugin) — refer them to Figma’s setup guide if the tools are absent from the session.
Before starting any Figma-dependent work, verify the MCP is present:
whoami-style tool is available in the session’s MCP list, that confirms the connection
and tells you which seat type the user has.whoami and escalate to
their Figma admin if needed.-; the MCP expects :. Always convert. If a tool
responds with “node not found”, check the ID format first.help.figma.com/hc/en-us/articles/32132100833559-Guide-to-the-Dev-Mode-MCP-Serverdevelopers.figma.com/docs/figma-mcp-server/tools-and-prompts/