Skip to main content
Tarek-MetaCTO
New Member
August 1, 2025
Solved

Figma MCP not working

  • August 1, 2025
  • 43 replies
  • 32634 views

I have Figma MCP enabled but whenever I go to the MCP server URL I see the following response

 

{"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}
Best answer by Tom Reem

Hi everyone,

I really appreciate you taking the time to share your updates here. I’ve passed your latest replies along to our product team to keep your experience front and center.

 

A couple of points to help clarify next steps:

  1. If you see the following error, this is coming from the Cursor side. It may turn red after 5 minutes, but it should still function. If you can see “5 tools,” it should be connected.
    Figma MCP Cursor test % curl -s http://127.0.0.1:3845/mcp || echo "Connection failed"
    {"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}
     
  2. If you’re seeing errors in your MCP clients, screenshots of where those appear will help us better understand the behavior — feel free to reply here or send those in directly.

 

If you’d like a member of our Product Support team to take a closer look at your specific file, please reach out to them directly and include:

  • the link to this Forum thread for context
  • a full-size screen recording of the issue (if possible)
  • a link to the affected file
  • edit access for support-share@figma.com

 

Thanks again for your patience — your reports are a big help in improving things

43 replies

mattcarpenter
New Member
August 1, 2025

Same issue for me. The figma desktop app showed a banner indicating that I was still using the old endpoint and suggested switching to the new sse endpoint. I did so but was unable to connect after changing it.

.mcp.json for claude code:

"figma" : {
"type": "sse",
"url": "http://127.0.0.1:3845/mcp"
}

The old /sse endpoint still works.

moontown
New Member
August 2, 2025

Same here 

Tarek-MetaCTO
New Member
August 2, 2025

Same here 

Despite being deprecated, add the URL to be /sse instead of /mcp, this will give deprecation warning inside Figma but it’ll work just fine. Hopefully they fix it soon

A.P.
New Member
August 2, 2025

This worked for me for Claude Code. Using the official instructions (with the URL set to /mcp) did not work, but changing it to /sse has made it green)

iqdda
New Member
August 3, 2025

Absolutely love how they released breaking change on Friday evening. Vibe coders all the way through!

Tom Reem
Figmate
Figmate
August 4, 2025

Hi everyone — thank you for flagging this! I’ve shared your reports with our engineering team, and they’ve identified the cause of the issue. An investigation into a fix is currently in the works, and we’ll follow up here as soon as we have more to share.

Appreciate your patience in the meantime — and don’t hesitate to reach out if anything else comes up.

James Blackwell
New Member
August 4, 2025

Also managed to get this working just by changing the URL to http://127.0.0.1:3845/sse 

Tom Reem
Figmate
Figmate
August 4, 2025

Hey everyone — good news. I checked in with the team working on this, and the issue has now been resolved. There was a problem in the setup documentation, but it’s been corrected — everything should work as expected now. ✅


💡 Next steps:

  1. If you were running into this while using the setting in Claude Code, you’ll need to remove the old MCP server config first: claude mcp remove figma-dev-mode-mcp-server.
  2. Then, re-add it using the steps with this address http://127.0.0.1:3845/mcp outlined in the updated Figma Learn guide: Guide to the Dev Mode MCP Server.

 

⚠️ Reminder: /sse is deprecated and will stop working in the future.

 

Appreciate everyone’s patience while we worked on this! Let us know how things go — and feel free to reach out if anything else comes up.

Tangtang8982
New Member
August 5, 2025

{"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}

When using  http://127.0.0.1:3845/mcp 

and when i use  http://127.0.0.1:3845/sse

 

the agent load the prompt (get_code for example) to infinity.. 

Thank’s for your help

Levi_Jones
New Member
August 6, 2025

​@Tangtang8982 check your hidden LLM instructions file. This was the fix for me with Claude Code https://x.com/Levidjones/status/1952958415086711118