Cursor MCP shows "Client closed" and "No tools available" — how to fix?
Using grab/cursor-talk-to-figma-mcp in Cursor and following the video demo steps, the MCP connection shows "Client closed" and "No tools available". What setup steps make the tools appear? The thread doesn't state OS or versions, so the answer is setup-level only.
Originally asked on GitHub: https://github.com/grab/cursor-talk-to-figma-mcp/issues/61
3 answers
Status: Fixed for the reporter — the issue is closed as completed and the reporter confirmed it worked on a later attempt ("This time it works"), possibly due to startup order. No root cause or code fix was identified in the thread.
The only troubleshooting advice came from a commenter:
- Use
localhostfor the MCP server connection. - Run the MCP server in a terminal.
- Keep three things running at the same time: Cursor, the terminal with the MCP process, and Figma.
The reporter replied that they were already doing these steps, and on that attempt the tools appeared. They suspected the order in which things were started made the difference. The thread does not include the exact
.mcp.jsonconfig, CLI flags, or version-specific details.General advice not from the thread: in Cursor, "Client closed" usually means the MCP server process exited or failed to stay running, so if the problem persists, check the terminal output where the MCP server runs for the actual error message.
Did this work for you?- Use
What a GitHub user tried on GitHub (Didn't work)
The reporter followed the video demo steps for grab/cursor-talk-to-figma-mcp and saw "Client closed" and "No tools available" in Cursor.
Source: https://github.com/grab/cursor-talk-to-figma-mcp/issues/61 (opens external site)
Did this work for you?What @eonist tried on GitHub (Worked)
A commenter suggested using localhost, running the MCP server in a terminal, and keeping Cursor, the terminal, and Figma running at the same time. The reporter confirmed doing this and said it worked that time, likely because of the startup order.
Did this work for you?
Related questions
- cursor-talk-to-figma-mcp: 'Unexpected token C, "Connecting"... is not valid JSON' error
- How to fix "Client closed" / "Sending message to client: undefined" in cursor-talk-to-figma-mcp?
- cursor-talk-to-figma-mcp stuck at "joining channel" in Cursor?
- Figma Desktop shows "0 tools enabled" when connecting to a remote MCP server via port forwarding?
- Talk-to-Figma MCP "Client closed" on Cursor Windows + WSL2: how to fix?