This guide is part of our MCP connection guides, within The MCP Guide. Steps are copied from the vendor's own documentation. Need a custom connection? See MCP development.
Connecting Claude to Figma lets Claude pull design context from your Figma files, such as layouts, variables and components, and turn prompts into FigJam diagrams like flowcharts. You point Claude at a frame by pasting its link. Figma builds the connector, and it is listed in Claude's Connectors directory.
Checked against: Figma's remote server installation guide and Claude's guide to getting started with connectors on 28 October 2026. eSEOspace did not run these steps; menus can change, so follow the vendor's page if it differs.
Key Takeaways
- Figma says only clients in its MCP catalog can connect, and the catalog lists Claude with remote and local servers and read and write access.
- Claude's directory lists Figma as "Anthropic verified," made by Figma, at
https://mcp.figma.com/mcp. - How often you can call the server depends on your Figma plan and seat. View and Collab seats get up to 20 tool calls a month.
- You can only use files you already have access to in Figma.
- In Claude, Figma says
get_screenshotreturns a description of the screenshot rather than the image.
Before you start
You need a Claude account signed in at claude.ai or in the Claude desktop app, and a Figma account. On a Claude Team or Enterprise plan, an owner adds the connector for the organization first.
Check your Figma seat. Figma's rate limits page says limits apply to tools that read data:
| Seat | Starter | Professional | Organization | Enterprise |
|---|---|---|---|---|
| View, Collab | Up to 20 per month | Up to 20 per month | Up to 20 per month | Up to 20 per month |
| Full, Dev | Not listed | Up to 200 per day, 10 per minute | Up to 200 per day, 15 per minute | Up to 600 per day, 20 per minute |
Figma says the remote server doesn't need the Figma desktop app. You sign in with your Figma account the first time you connect.
Steps
The connector URL in Claude's directory is:
https://mcp.figma.com/mcp- Go to Customize > Connectors in claude.ai. In the desktop app, select Customize in the sidebar, then Connectors.
- Select Discover, type "Figma" in Search connectors, and open the Figma listing.
- Select Connect to Claude. Team and Enterprise owners see Connect for your team. Members who can't add connectors see Request.
- Sign in to Figma when the sign-in page opens, review the access Claude asks for, and approve it.
- Check that Figma appears under Your connectors with the status Connected.
- In a chat, select + in the message box, select Connectors, and turn on Figma.
To point Claude at a design, Figma says to right-click a frame or layer and select Copy link to selection, then paste the link into your prompt. Claude doesn't open the link; it takes the node ID the server needs.
Check that it works
The Claude listing names these tools: generate_diagram, get_design_context, get_screenshot, get_metadata, create_design_system_rules, get_variable_defs, get_code_connect_map, get_figjam and whoami.
Example prompts:
- "Run whoami on Figma and tell me which plans and seats my account has." (uses
whoami) - "Here's a link to a frame: [paste link]. Describe its layout and list the variables it uses." (uses
get_design_contextandget_variable_defs) - "Create a flowchart for the user authentication flow using the Figma MCP generate_diagram tool." (Figma's own example prompt)
Permissions and safety
- Your file access only. Figma says you can use the server only with files you already have access to.
- Writes exist.
generate_diagramcreates FigJam content in your account. In Claude, open the connector under Customize > Connectors and set Tool permissions to Needs approval for tools that create content. - Rate limits and credits. Most tools don't use Figma AI credits. Figma lists exceptions such as
generate_imageandsend_prompt; neither is on Claude's listing as of October 2026. - Enterprise-managed authorization. Figma says it supports Claude through Okta Cross App Access (XAA), so members sign in once through Okta.
- Untrusted content. Text in shared files reaches Claude as input. Read MCP prompt injection and the MCP Security Center.
If it doesn't work
Figma's rate limits and access page covers these issues:
- Permission errors. Check that the link points to a Figma Design, FigJam or Figma Make file. Ask Claude to run
whoamito see the email, plans and seats you're signed in with. Make sure that account belongs to the plan that owns the file. - Rate limited. Starter plans and View or Collab seats are capped at 20 calls a month. Figma says you can raise limits by upgrading your seat or plan.
- Screenshots. In Claude,
get_screenshotreturns a description only, per Claude's listing. That's expected.
If Claude loses access later, the connector row shows Reconnect. Select it and sign in again.
Next step
The Figma MCP server profile compares the remote and desktop servers. If you build front ends, Figma also documents a plugin for Claude Code; see Claude Code with Figma. Browse more setup guides in the connection guides hub, or ask about Claude Code development for design-to-code work.
Frequently asked questions
Can I use Figma MCP with a free Figma plan?
Figma lists limits for Starter plans: up to 20 tool calls a month. Full and Dev seats on paid plans get daily limits from 200 to 600 calls. Check Figma's rate limits page for current figures.
Does Claude need the Figma desktop app?
No. Figma says the remote server connects directly to Figma and doesn't need the desktop app. Figma's catalog also lists a local server option for Claude.
Can Claude draw in Figma?
Claude's listing includes generate_diagram, which Figma says turns prompts into flowcharts, Gantt charts and other FigJam diagrams. Figma's docs name more tools that write to files, such as create_new_file and generate_figma_design, but they aren't on Claude's listing as of October 2026.
Why can't Claude see my Figma file?
You can only use files your Figma account can already open. Ask Claude to run whoami to confirm which account is connected, and check that it belongs to the plan that owns the file.
