Skip to main content

Hi everybody –

I’m using VS Code with Claude Code and I’m trying to setup my Access Token. Inside my Figma Settings panel, the token states it was used and appears to be connected, but Claude (via VS Code) is showing a failed connection when using prompt “/mcp” to see the Manage MCP servers readout.

On the other hand, my Figma Dev MCP Server, directly from my Project, is showing Connected.

I connected the API before I connected the Dev MCP, though – does that make a difference? Do I need to connect the Access Key for additional functionality or will just the Figma Dev MCP do the same thing?

UI/UX is my primary field so I’m in the depths of this learning curve for back-end stuffs.

Any insight is greatly appreciated!

👋🏻 Hey ​@Viorbit — welcome to Figma Forum! A few other folks recently ran into a similar issue, and there’s an ongoing discussion here that might help connect the dots: Figma MCP not working. When you have a moment, could you check that thread and see if it lines up with your experience?

If not, or if you’d like someone to dig into your setup more closely, feel free to reach out to our Product Support team directly via this secure form: Submit a request. Either way, looking forward to hearing more from you!

Hi Tom, thank you for your reply! 

I think I figured out what I did wrong. I was setting up the Personal Access Token (from browser Figma // Settings > Security) as an MCP Server inside VS Code, which I’m assuming is incorrect, since the Dev Mode MCP (from Figma Desktop) connected fine and is working.

Still mucking around with it.

Thanks!

Hi everybody –

I’m using VS Code with Claude Code and I’m trying to setup my Access Token. Inside my Figma Settings panel, the token states it was used and appears to be connected, but Claude (via VS Code) is showing a failed connection when using prompt “/mcp” to see the Manage MCP servers readout.

On the other hand, my Figma Dev MCP Server, directly from my Project, is showing Connected.

I connected the API before I connected the Dev MCP, though – does that make a difference? Do I need to connect the Access Key for additional functionality or will just the Figma Dev MCP do the same thing?

UI/UX is my primary field so I’m in the depths of this learning curve for back-end stuffs.

Any insight is greatly appreciated!

Hey, same thing happened to me recently — took me a while to figure it out.

Even though your Figma settings show the Access Token as connected, Claude Code in VS Code still needs to specifically validate it via. If the Dev MCP (direct from your Figma project) works but the API-level MCP fails, it often means the token wasn't granted the right scopes or wasn’t fully authorized before use.

A few things that helped me:

  • Make sure the token has both design access and server config scopes; if you originally created it before enabling Dev MCP, you might need to regenerate it with those permissions.

  • Revoke the old token and reconnect it using so Claude Code picks it up anew.

  • Sometimes the order does matter — so regenerate after Dev MCP is active and test again in VS Code.

Once the token is properly scoped and re-authorized, I was able to run successfully and everything synced up.

Hope this helps—loving Claude Code but those backend quirks can be confusing at first. Let me know how it goes!

Terms & ConditionsCookie settingsAccessibility statement