generate_figma_design not available in Claude Code connector?

I tried so many things, and what finally did it is that I had to also disconnect the Claude desktop plugin for Figma. The only thing that can be connected is the MCP server in Claude CLI. For some reason, that made it work for me. 

Tried everything, including Figma CS steps:

• claude mcp add --transport http figma-remote-mcp https://mcp.figma.com/mcp
• Disconnect / disable / unauthorize any previous connector or MCP instances

• Restart Claude before reconnecting

I don’t have the Claude desktop plugin for Figma.
I also disconnected the Chrome Claude plugin.
Nothing seems to work.

Now I’m not able to reconnect to the Figma MCP and in debugging hell to get it back.

Hi everyone — thanks so much for your patience while we worked on a fix.

Our Engineering team has deployed a resolution and confirmed that the issue should be resolved.

Please restart or refresh Figma to ensure you’re on the latest version, and let us know if you continue to experience any issues.

We appreciate you flagging this and for your patience throughout 🙏

​@Celyn_L 

I am still unable to use `generate_figma_design` in my environment. 
Also, it appears that only 10 tools are accessible when connecting to MCP via Claude Code. 
For your information, I am assigned full seat permissions.
 

Same for me. Yesterday it worked with the free version. Today with a pro full seat Claude is complaining:

 

I have to be honest with you: even after the full fresh OAuth on a Full seat, the server still isn't advertising use_figma. The reconnected set is create_new_file, generate_diagram, get_design_context, get_metadata, get_screenshot, get_variable_defs, get_figjam, the Code Connect tools, and whoami — every read tool plus file-create, but the canvas editor is absent (so are its AI siblings generate_figma_design / search_design_system).

It was there at the very start of this session and I used it. The fact that it consistently won't come back — across seat upgrade, re-auth, app relaunch, and a clean reconnect — tells me it's gated at the account/AI-feature level (your "AI credits" note fits: these are Figma's AI-powered write tools). That's not something I can flip from here.

I'm not going to send you through another auth loop. Since you now have a Full seat, you can make these edits directly in the Figma UI

​@Celyn_L  hi i am facing the same issue 17 tools online but { generate_figma_design } is missing

Hey both, thanks for reaching out and flagging this!

I’m stepping in on behalf of ​@Celyn_L to help here. This is something our team is actively looking into right now.

We don't have a fix or timeline to share just yet, but I'll keep this thread updated as soon as we have more information.

Really appreciate your patience while we work through it! 

The generate tool lives on the remote endpoint, not the local one. The local address hosts only the read tools; write tools come through the remote connection. If your connector is pointed at the local address, that's why the generate tool isn't showing up. In Claude Code, check which URL your Figma connector is using in MCP settings and switch to the remote one if needed. You'll also need Dev Mode on your Figma plan and to be signed in so the auth flow can complete. If you're already on the remote endpoint and still don't see it, try removing and recreating the connector rather than editing in place. Did switching endpoints help?

This does not fix the missing MCP tool, but there is another workflow if the immediate goal is to bring a local frontend into Figma.

Source → Design imports local HTML files and React, Next.js, Vue, or Svelte project ZIPs as editable Figma layers. Disclosure: I’m the maker. It can be useful as a fallback while the MCP connector is unavailable or inconsistent.

Plugin: https://www.figma.com/community/plugin/1671982756700161071