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.

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

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)

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

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.

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

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.

{"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

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

This has not been resolved - got it to work once randomly but then getting: 

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}                   

Edit: Figured this out. Just had to remove the mcp and install the mcp in the correct directory. 

Im still getting a “failed to connect” error using the /mcp or /sse commands. I removed the mcp multiple times and it seems to be running the figma desktop app. I wish there were more ways to debug this. 

Not sure whats happening. Anyone have any suggestions? (on Mac OS, using Claude Code) 

Hey everyone i’ve fix it with this config . By changing not just the link but the type too from sse to http
in claude-code.
● Update(..\.claude.json)
       600          "mcpContextUris": o],
       601          "mcpServers": {
       602            "figma-server": {
       603 -            "type": "sse",
       603 +            "type": "http",
       604              "url": "http://localhost:3845/mcp"
       605            }
       606          },
 

I still have the problem 

 Figma + Cursor. can’t connect it 

I’m using vsCode, my configuration is good but always the same problem.

I tried using Cursor and have the same…

 

only http://127.0.0.1:3845/sse works. http://127.0.0.1:3845/mcp still returns 

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

(Figma Desktop App version 125.6.5)

Anyone had any luck here? I get stuck in calling_get_code:

{

"clientLanguages": "typescript,javascript,html,css",

"clientFrameworks": "react,next.js",

"nodeId": ""

}

Visiting the URL gives me: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}

I also don’t understand why the indicator keeps going red no matter home many times i turn it off and on.

​@Tom Reem - Exact same issue for me as posted above - this is not fixed. I have tried everything and when I close and open Figma it says that the MCP server is running on the url that I have in Cursor.

For those stuck until Figma can figure things out. Try: https://github.com/GLips/Figma-Context-MCP

Please be careful of setting up third party MCPs and sharing your Figma token with them.

Figma MCP Endpoint Issue - /mcp endpoint not working, only /sse works

SUMMARY
Despite Figma Desktop indicating that the MCP server is running at the /mcp endpoint, only the /sse endpoint is functional. The /mcp endpoint consistently returns JSON-RPC errors.

ENVIRONMENT DETAILS
- Figma Version: 125.7.5 (latest as of August 12, 2025)
- Operating System: macOS
- MCP Server Port: 3845 (confirmed running)
- Installation: Fresh reinstall to ensure no version conflicts
 

What Works:
- SSE Endpoint (http://127.0.0.1:3845/sse):
  - Returns HTTP 200 OK
  - Content-Type: text/event-stream
  - Proper security headers
  - Establishes connection successfully
  - MCP tools function correctly through this endpoint

What Doesn't Work:
- MCP Endpoint (http://127.0.0.1:3845/mcp):
  - Returns various JSON-RPC errors depending on request format
  - Common errors encountered:
    {"jsonrpc": "2.0", "error": {"code": -32001, "message": "Invalid sessionId"}, "id": null}
    {"jsonrpc": "2.0", "error": {"code": -32000, "message": "Invalid request body for initialize request"}, "id": null}

TECHNICAL INVESTIGATION

Server Status Verification:
I confirmed that Figma is running the MCP server on port 3845 and VS Code can connect to it via the SSE endpoint.

Endpoint Testing Results:
- SSE Endpoint: curl -v http://127.0.0.1:3845/sse returns HTTP 200 OK with proper event-stream content
- MCP Endpoint: curl -X POST http://127.0.0.1:3845/mcp with standard JSON-RPC requests returns error messages

TROUBLESHOOTING STEPS ATTEMPTED

1. Clean Installation:
   - Completely uninstalled and reinstalled Figma Desktop
   - Downloaded latest version (125.7.5) from official website
   - Verified no old MCP installations remained

2. Configuration Cleanup:
   - Removed all third-party MCP installations
   - Cleared MCP-related caches and configurations
   - Ensured no port conflicts

3. Multiple Request Formats Tested:
   - Standard MCP initialize requests
   - Various JSON-RPC parameter combinations
   - Different HTTP headers and content types

4. Process Verification:
   - Confirmed Figma process is running the MCP server
   - Verified port 3845 is correctly bound to Figma
   - Established that VS Code can connect via SSE endpoint

CURRENT WORKAROUND

The SSE endpoint (/sse) works perfectly and provides full MCP functionality. MCP configuration that works:

```json

"Figma Dev Mode MCP": {

"url": "http://127.0.0.1:3845/sse"

}

```

QUESTIONS FOR FIGMA TEAM

1. Is the /mcp endpoint fully implemented in version 125.7.5?
   - The endpoint exists but returns errors for standard MCP requests
   - Are there specific authentication or session requirements?

2. What is the expected request format for the /mcp endpoint?
   - Standard JSON-RPC 2.0 requests fail with "Invalid request body"
   - Is there additional metadata or headers required?

3. Should we continue using the /sse endpoint?
   - It works reliably but may be deprecated
   - What is the migration timeline if any?

4. Are there any known issues with the MCP endpoint in the current version?
   - This could help other developers experiencing similar issues

Please clarify the expected behavior and provide guidance on:
1. Proper usage of the /mcp endpoint
2. Whether /sse will remain supported
3. Any additional configuration required for /mcp endpoint functionality

Thank you for your attention to this matter. The MCP integration is valuable for design-to-code workflows, and clarifying this endpoint behavior would help the developer community.

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

Of course. But I still need to get work done. The /sse and /mcp endpoints don’t work. I also use motiff.com and their MCP server works perfectly fine.

Until Figma fixes this, I’m actually getting work done using the tool above. If it’s not fixed before I’m done then I’ll just use the tools that actually work.

1. Only http://127.0.0.1:3845/sse can access，and http://127.0.0.1:3845/mcp can’t access

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

2. Although http://127.0.0.1:3845/sse's OPTIONS, GET responds normally, tools such as get_code report errors，error code：500

            - "OPTIONS /openapi.json HTTP/1.1" 200 OKTom ReemTom Reem

            - "GET /openapi.json HTTP/1.1" 200 OK

            - INFO - Calling endpoint: get_code, with args: {'clientLanguages': 'xml', 'clientFrameworks': 'android'}
            - INFO - Unexpected error calling get_code

            - "POST /get_code HTTP/1.1" 500 Internal Server Error

Please help to check it, thanks~

​@Tom Reem 

1. Only http://127.0.0.1:3845/sse can access, http://127.0.0.1:3845/mcp still can’t access.

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

2. Although http://127.0.0.1:3845/sse's OPTIONS, GET responds normally, tools such as get_code report errors. error code: 500

           - "OPTIONS /openapi.json HTTP/1.1" 200 OK

            - "GET /openapi.json HTTP/1.1" 200 OK

            - INFO - Calling endpoint: get_code, with args: {'clientLanguages': 'xml', 'clientFrameworks': 'android'}
            - INFO - Unexpected error calling get_code

            - "POST /get_code HTTP/1.1" 500 Internal Server Error

Please help to check it, thanks~