Figma Devmode MCP doesn't work

Hi ​@welsewool, thanks for reaching out!
Could you share what error you’re seeing when it fails? even a quick screenshot or the error description can help us understand what might be going wrong.

In general, there are a few common reasons the MCP might not behave as expected.. here are some quick things to check:

1. Selection size - does the issue happen with all selection sizes? Can you try calling the MCP on a smaller selection and see if it behaves the same?

2. Figma <> IDE connection - can you make sure the MCP is still enabled in the Figma file you're working in, and that the tools are loading properly in your IDE?

3. Refresh both environments - Try refreshing Figma and restarting your IDE. That often helps resolve temporary sync issues.

4. Update Figma - Make sure you're running the latest version of the Figma desktop app.

Let us know if any of these helped, we’d be happy to help troubleshoot further!

Hi ​@Yarden K, 
I am trying to reach Figma via Cursor (which worked week ago) and currently I just receive that it’s a connection problem. 
I have tried all you mentioned - turning on / off, reinstalling, updating, different files, different sizes… Still no conversation between Cursor and Figma (but MCP is connected to it). 

I also tried in other IDEs and same issue. 

same problema with VS Code!

Same here I’m seeing 

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

Same problem. Claude code simply cant connect to Figma MCP. Figma, you are now a public company with billions in raised capital. Would you please fix your mcp server. this is such a pain.

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

Same problem, the SSE endpoint works, I don’t know where that is installed. I tried uninstalling Figma and install the latest and still the same issue.

I have been facing the same issue, when I try to ask cursor to access the Figma MCP it’s having connection issues. Any updates on how to fix this?
I’m getting the following message: 
MCP endpoint not available - Local server returns 404 for all endpoints

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

is there any update on this?

Figma customer service reached out to me directly after creating a ticket. They tried to help me troubleshoot but the best they could suggest was to keep both Cursor and Figma if both programs have the latest version.
I found a hack, I check in Cursor the MCP settings and if the Figma MCP is orange or red I just switch off the toggle and the switch it on again. Maybe try that it might work for you too. 

Im having issues  with creating a token to connect figma MCP server to our org account, Im an admin  on the account. when I go to settings and security and create a new token the button is greyed out and wont let me create a token. it did a few days ago but for some reason i can not get claude to work with that token. I go into claude setting and the connection shows toggled on and running but claude doesn’t have the tool icon it tells me to look for. and this is the same issue I am having with my personal pro account. I cannnot create a token in that one either. the button is greyed out. I have deleted old figma and downloaded a new version. I did the same to claude and nothing has changed. Im dead in the water and can’t get anything to work. I have checked all permissions and everything is turned on  so there should be no restrictions. I ahve been trying to get this to work for for 5 days now (off and on). nothing is working and i need someone smaarter than me to help trouble shoot. I asked claude but everything he has had me try hasn’t worked either… help

Hi ​@Scott Mackenzie, thanks for chiming in here! 

Apologies for the delayed reply. If I’m understanding correctly, you’re having trouble generating a new Personal access token. Is that correct? 

And under Personal access tokens, the link to Generate new token is greyed out for you:

This issue may be related to a service disruption we’re experiencing, but I saw that you also reached out to support directly on ticket#1756701. If you could reply to Clara’s last email, our technical support team can continue investigating this issue with you directly.