MCP & CONNECTED TOOLS
Figma MCP for Claude Code Setup and File Checks
For Claude Code and Cursor, Figma recommends its plugin where available. Manual remote MCP connects the server, but does not install the same skills and rules.
On this page
Connect Figma, select a frame, inspect context
01Remote Figma MCP does not require the desktop app.
02Plugin setup and manual endpoint setup install different packages.
03Connected status and access to the intended file are separate checks.
Start with one practical task
Choose one Figma file and a specific frame you can access. Confirm the client can read that frame and match the result to the file before expanding the design task.
Use the recommended client route
For Claude Code, the official guide installs figma from claude-plugins-official, followed by sign-in through the plugin manager. Cursor’s guide uses /add-plugin figma, then Connect in Tools & MCP. Organization policy can affect whether plugin installation is available.
Understand the manual fallback
Both clients can configure the remote mcp.figma.com/mcp endpoint. The Figma guide says manual setup does not add its skills, and Cursor’s fallback also omits the plugin’s rules. Desktop setup is separate.
Verify a small file task
Confirm connected status and access to the intended file, then ask for one frame’s context before requesting implementation or canvas changes. Distinguish file permission, missing tool, unsupported client and an overly broad selection when diagnosing failure.
A few more details
Does manual MCP setup include the Figma skills?
No. The official guide links separate skill setup for manual connections.
Can I start from a whole large design file?
A bounded frame and clear task make troubleshooting and output review easier; expand after confirming access and context.
Sources & maker notes
This guide is based on the cited documentation and maker sources. vibeforthat has not run an independent installation or end-to-end product test for this article.