Skip to main content
Solved

Figma MCP not working

  • August 1, 2025
  • 40 replies
  • 17845 views

Show first post

40 replies

Gabriel Williams

This seems like an expired token or auth. I had Claude Code “Reconnect” and things started working again with /mcp.


Sivasankar M
  • New Member
  • August 19, 2025

Just for your information, guys — in my case, when I try the /mcp endpoints using the get_code tool in VS Code, I encounter a timeout error. Other tools are working fine. Could this be related to a server-side issue?  Anyone finds a solution on this. 

 


Nick Pape
  • New Member
  • August 19, 2025

This still seems broken. VSCode 1.103, fresh Figma installation, dev seat, started the MCP, get the toast that it’s running, but then see the following:

VS Code:

2025-08-19 10:31:17.945 [info] Starting server figma
2025-08-19 10:31:17.948 [info] Connection state: Starting
2025-08-19 10:31:17.949 [info] Starting server from Remote extension host
2025-08-19 10:31:17.989 [info] Connection state: Running
2025-08-19 10:31:18.062 [info] Connection state: Error Error sending message to http://127.0.0.1:3845/mcp: TypeError: fetch failed
2025-08-19 10:31:18.062 [error] Server exited before responding to `initialize` request.

 

Config:

    "figma": {
// The Figma MCP server requires you to setup the local client.
// 1. Install the rich client: https://www.figma.com/downloads/
// 2. Login with a "Dev" account
// 3. Enable the MCP: Upper left Figma menu -> Preferences -> "Enable Dev Mode MCP Server"
// 4. Click start above "figma" (above this comment).
"type": "http",
"url": "http://127.0.0.1:3845/mcp"
}

If you nav to the endpoint in a browser, you get:

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

djv
Figmate
  • Community Support
  • August 20, 2025

Hey All, thanks for following up! 

As ​@Tom Reem mentioned previously, when you’re testing using CURL or in the browser, you’ll receive the Invalid sessionId, because you’re not passing in a session ID as a parameter. While MCP clients do allow this, it’s not designed to be used directly. Again, this is an issue on the Cursor side of things. Even if it goes red after a few minutes, it should still work.

Again, for direct one on one support with this, we encourage you to reach out to our support team directly and provide screenshots of exactly where in your MCP clients the errors are popping up: https://help.figma.com/hc/en-us/requests/new


xiao99xiao
  • New Member
  • September 6, 2025

This seems like an expired token or auth. I had Claude Code “Reconnect” and things started working again with /mcp.

👍 This works for me.


Schwepps
  • New Member
  • September 8, 2025

This worked for me:
claude mcp add figma-dev -- npx -y figma-developer-mcp --figma-api-key=YOUR_API_KEY  --stdio  

You can generate an API_KEY in your account settings.


Alexei Polozov

Figma Desktop App version 125.8.6

still does NOT work with :

Version: 1.5.9 (Universal)
VSCode Version: 1.99.3
Commit: de327274300c6f38ec9f4240d11e82c3b0660b20
Date: 2025-08-30T21:02:27.236Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
 


Pedro Garcia Lopez

For anyone still running into this issue and you are using devcontainers, here’s what fixed it for me.
Update your configuration to use the following URL:

{
"mcpServers": {
"figma-desktop": {
"url": "http://host.docker.internal:3845/mcp"
}
}
}


After making this change, everything started working properly.
Hopefully, this helps others — it’d be great if the docs included this option too!
 


Lior Tabachnik

Hey i have different problem when i try to establish connection to cursor

 



loading tools for infinity time,
 

"figma" : {

"url": "http://127.0.0.1:3845/mcp",

"type": "http"

}

 


Yevhen Tienkaiev

This guide not working https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/#vs-code

 

When you click authenticate it says:

OAuth app with client id 0KZQoOxn4dVQzQ8Ugdudkh doesn't exist

 

So remote MCP not works.

Please fix this


Jason Hsieh
  • New Member
  • November 10, 2025

Hey i have different problem when i try to establish connection to cursor

 



loading tools for infinity time,
 

"figma" : {

"url": "http://127.0.0.1:3845/mcp",

"type": "http"

}

 

Same here

Figma Desktop App version 125.9.10
Version: 2.0.54 (Universal)


gund
  • New Member
  • December 1, 2025

I’m having the issue with MCP in VScode, after authenticating the logs just show `[info] Waiting for server to respond to `initialize` request...` and printing this message constantly.

Seems like the MCP server never initializes in the VSCode even after authentication was successful…

MCP config is:

```

  "figma/mcp-server-guide": {

      "type": "http",

      "url": "https://mcp.figma.com/mcp"

    },

```

Any ideas?


GregL
  • New Member
  • December 7, 2025

This works for me in cursor
 

{
"mcpServers": {
"Figma": {
"url": "https://mcp.figma.com/mcp"
}
}
}

 


BohdanS
  • New Member
  • January 7, 2026

Figma Desktop App version 125.11.6

still does NOT work:
```{"jsonrpc":"2.0","error":{"code":-32001,"message":"Invalid sessionId"},"id":null}```


Lyudmil
  • New Member
  • January 9, 2026

I’m having the issue with MCP in VScode, after authenticating the logs just show `[info] Waiting for server to respond to `initialize` request...` and printing this message constantly.

Seems like the MCP server never initializes in the VSCode even after authentication was successful…

MCP config is:

```

  "figma/mcp-server-guide": {

      "type": "http",

      "url": "https://mcp.figma.com/mcp"

    },

```

Any ideas?

I have same issue