On this page
- Quick steps
- Remote or desktop Figma MCP server?
- How to add the Figma MCP server to Claude Code
- How to connect Figma MCP to Cursor
- How to set up Figma MCP in VS Code
- Codex, Antigravity and other clients
- Figma MCP rate limits by plan and seat
- Figma MCP not working: common errors
- MCP, Dev Mode and Figma Make
- FAQ
Quick steps
Pick the remote server
Figma recommends the remote server at https://mcp.figma.com/mcp. It has the most tools, including writing to the canvas, and needs no desktop app.
Add it to your client
In Claude Code run claude mcp add --transport http figma https://mcp.figma.com/mcp. In Cursor type /add-plugin figma in the agent chat. In VS Code add the URL to mcp.json with type http. In Codex run codex mcp add figma --url https://mcp.figma.com/mcp.
Sign in with Figma
Start the server from your client. A browser window opens. Sign in to the Figma account that can open your files and click Allow Access.
Give the agent a link
In Figma, right-click a frame and copy its link. Paste it into your prompt. The remote server works from links, not from what you have selected.
Check the tools loaded
Your client should list Figma tools such as get_design_context and get_screenshot. If it shows 0 tools, see the fixes below.
Remote or desktop Figma MCP server?
- Remote server. Hosted by Figma at
https://mcp.figma.com/mcp. Available on all plans and seats. It has the write tools:use_figmabuilds frames, components, variables and auto layout in a file, andgenerate_figma_designturns a running web page into Figma layers. You pass it a link to a file or layer. - Desktop server. Runs in the Figma desktop app at
http://127.0.0.1:3845/mcp. Needs a Dev or Full seat on a paid plan. It reads whatever you have selected, so you don't paste links. It only runs while the desktop app is open with the file active.
Pick one. If both are configured, your client may connect to the desktop server and never load the remote-only tools.
How to add the Figma MCP server to Claude Code
Figma's docs suggest the plugin first: claude plugin install figma@claude-plugins-official. It adds the server and a set of skills for common tasks. To add only the server, run claude mcp add --transport http figma https://mcp.figma.com/mcp, then type /mcp, pick figma and authenticate. Add --scope user to make it available in every project.
For the desktop server, run claude mcp add --transport http figma-desktop http://127.0.0.1:3845/mcp instead.
How to connect Figma MCP to Cursor
Type /add-plugin figma in Cursor's agent chat, or use the install link on Figma's setup page, click Connect next to Figma and authorise. For the desktop server, open Cursor Settings, go to the MCP tab and add a global server with "figma-desktop": { "url": "http://127.0.0.1:3845/mcp" }.
How to set up Figma MCP in VS Code
- Press
⇧⌘P/Ctrl+Shift+Pand run MCP: Open User Configuration. - Add a server called
figmawith"url": "https://mcp.figma.com/mcp"and"type": "http"inside"servers". - Click Start above the entry and allow access in the browser.
The desktop server in VS Code goes through MCP: Add Server, then HTTP, then the local URL. Figma notes it needs GitHub Copilot turned on.
Codex, Antigravity and other clients
For Codex, run codex mcp add figma --url https://mcp.figma.com/mcp or install Figma from the plugins list in the Codex app. Other clients connect only if they're in Figma's MCP Catalog at figma.com/mcp-catalog. The list includes Claude, ChatGPT, Google Antigravity, GitHub Copilot CLI, Kiro, Warp, Zed, Replit, Android Studio and more. If your tool isn't there, it can't use the remote server.
"Connecting Figma MCP Server with Google Antigravity" has about 58k views on the Figma forum. The people who got stuck had created their own OAuth app with a client ID and secret. Don't. Use the client's own Figma entry (in Antigravity, the MCP servers menu) and let it run the sign-in.
Figma MCP rate limits by plan and seat
- Starter plan: up to 20 tool calls a month.
- View or Collab seat on Professional, Organization or Enterprise: up to 6 tool calls a month.
- Dev or Full seat, Professional: up to 200 a day, 10 a minute.
- Dev or Full seat, Organization: up to 200 a day, 15 a minute.
- Dev or Full seat, Enterprise: up to 600 a day, 20 a minute.
- Education plans: the same as Professional.
Limits count tools that read from Figma. whoami, create_new_file and add_code_connect_map are exempt. Writing to the canvas with use_figma needs a Full seat and edit access. Dev seats are read-only. Figma says writing to the canvas is free during the beta and will later be a usage-based paid feature. For how Figma bills its other AI features, see Figma AI credits.
Figma MCP not working: common errors
- "Invalid scope: mcp:connect" or "Invalid scopes for app". You're using your own OAuth app. Figma support says the
mcp:connectscope "isn't available for general third-party OAuth apps". Use a client from the MCP Catalog and its built-in sign-in. - 0 tools, or tools not loading. For the desktop server, open the file in the desktop app, switch to Dev Mode (
⇧D) and click Enable desktop MCP server. Keep the file open. Then restart Figma and your editor. If you set up both servers, remove one. - "Invalid sessionId". Old setup instructions caused this. Remove the old entry (for Claude Code,
claude mcp remove figma-dev-mode-mcp-server) and add the server again with the/mcpURL. The old/sseendpoint is deprecated. - Tool calls fail in Cursor. Open the Command Palette, run Clear All MCP Tokens and sign in again.
- "Response exceeds maximum allowed tokens" in Claude Code. The frame is too big for one response. Set the
MAX_MCP_OUTPUT_TOKENSenvironment variable higher (for example 50000) and restart, or link a smaller frame. - Stuck, slow or "lost connection to MCP server". Usually the selection is too large. Link a card, header or sidebar instead of a whole page.
- Rate limited. You've hit your plan's limit. Wait for it to reset, or move to a Dev or Full seat or a higher plan.
MCP, Dev Mode and Figma Make
The MCP server is for agents working in your own codebase. Dev Mode is for people inspecting a design by hand. Figma Make builds an app inside Figma from a prompt. The MCP server can also read a Make project's files if you give it a Make link, which helps when you move a prototype into production. See how to export code from Figma Make.
Plugins cover other parts of the handoff, like exporting code or specs without an agent:
Ranked listThe best Figma to code plugins in 2026Frequently asked questions
Is the Figma MCP server free?
The remote server is available on every plan and seat, including Starter, but with limits: 20 tool calls a month on Starter and 6 a month on View and Collab seats. Dev and Full seats on paid plans get 200 to 600 a day.
What is the Figma MCP server URL?
The remote server is https://mcp.figma.com/mcp. The desktop server runs at http://127.0.0.1:3845/mcp while the Figma desktop app is open.
Why don't I see the MCP server option in Figma?
The desktop server toggle is in Dev Mode, in the MCP server section of the inspect panel, in the desktop app. You need a Dev or Full seat on a paid plan. You add the remote server in your code editor, not in Figma.
Can I get the mcp:connect scope for my own app?
No. Figma says the scope isn't available to general third-party OAuth apps. Only clients in the Figma MCP Catalog can connect, and there's a waitlist at figma.com/mcp-catalog.
Can the Figma MCP server edit my designs?
Yes, through the remote server's use_figma tool. It needs a Full seat and edit access to the file. It's free during the beta.
More in Figma AI & Make
- How to Use Figma MakeUse Figma Make to turn a prompt or a Figma design into a working app: write better prompts, attach frames and libraries, add custom fonts, publish and share it.
- How to Export Code from Figma MakeExport code from Figma Make as a zip or push it to GitHub, run it locally with npm, open it in VS Code or Cursor, and copy the preview into Figma as layers.
- Figma Make Not Working? How to Fix ItFix Figma Make when it's slow after many prompts, out of credits, won't import your library, shows the wrong font, breaks the preview or won't publish.
- How Figma AI Credits WorkHow Figma AI credits work: monthly credits per plan and seat, what Make prompts and image tools cost, running out, buying more and turning AI off.
- How to Open Figma in Dev ModeOpen Figma Dev Mode with Shift+D or the toolbar toggle. Which plans and seats get it, why you see "can't access Dev Mode", and how to inspect without it.
- How to Convert a Figma Gradient to CSSCopy a Figma gradient as CSS from Dev Mode or Copy as code, then fix the angles and stop positions that don't match in the browser. Linear and radial.
- Where Is the Inspect Tab in Figma?Figma's Inspect tab now lives in Dev Mode. How to see CSS and specs without a Dev seat, get a missing right sidebar back, and find what else UI3 moved.
- How to install Figma pluginsFigma plugins don't need installing: open one from the Community or run it inside a file. Steps for Figma Design, Dev Mode, FigJam, Slides, saving and admins.
