cursor-talk-to-figma-mcp: 'Request to Figma timed out' when reading Figma files
Using grab/cursor-talk-to-figma-mcp with Cursor to turn Figma designs into code, the socket and MCP connections show green, but the agent's get_document_info call repeatedly fails with 'Error getting nodes info: Request to Figma timed out'. This happens even when Figma view permissions are set correctly. The GitHub issue is still open as of August 2025 — what workarounds actually get the tool working?
Originally asked on GitHub: https://github.com/grab/cursor-talk-to-figma-mcp/issues/70
6 answers
The issue is still open; no maintainer fix appears in the thread, and the fixes below come from other users.
A setup that worked for one reporter: run both
bun socketandbunx cursor-talk-to-figma-mcpconcurrently in two separate terminal instances — before that they got the timeout constantly. Keep the Figma window open with the plugin visible, because the plugin sometimes restarts or changes channel. Tell the LLM the current channel (shown in the Figma plugin) along with the file name, and after any restart re-communicate the new channel. Restarting the services in sequence (socket, bunx MCP, Figma plugin) and then telling the LLM the new channel also helped. Another user confirmed this advice fixed it for them.A second fix that worked: restart Cursor, toggle TalkToFigma off and on in the MCP tools list, then start
bun socket. In your first prompt, tell the model which channel to connect to (the one from the Figma plugin).A third report (with GitHub Copilot, not Cursor): after connecting on the channel, invoke the
get_document_infotool so the agent asks for permission, after which it can access the file.Results are intermittent: one user who tried the concurrent-services setup reported both MCP and plugin green and a successful channel join, but
get_document_infostill kept returning 'Request to Figma timed out'.Did this work for you?What @nwrightau tried on GitHub (Worked)
Ran
bun socketandbunx cursor-talk-to-figma-mcpconcurrently in two terminals, kept the Figma file and plugin window open, told the LLM the current channel and file name, and restarted the services in sequence (socket, bunx, plugin) when the channel changed.Did this work for you?What @vzts tried on GitHub (Worked)
Restarted Cursor, toggled TalkToFigma off and on in the MCP tools list, started
bun socket, and told the model the channel from the Figma plugin in the initial prompt.Did this work for you?What @mohamedhusseinios tried on GitHub (Worked)
After connecting on the channel, invoked the get_document_info tool so the agent asked for permission before accessing the file; reported on GitHub Copilot, not Cursor.
Did this work for you?What @Norlandz tried on GitHub (Didn't work)
Reported that with the concurrent-services setup both MCP and plugin showed green and the channel join succeeded, but get_document_info repeatedly failed with 'Request to Figma timed out'.
Did this work for you?What a GitHub user tried on GitHub (Outcome unclear)
Reporter observed that the connection was good but the Figma timeout error kept recurring.
Source: https://github.com/grab/cursor-talk-to-figma-mcp/issues/70 (opens external site)
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?
- Cursor MCP shows "Client closed" and "No tools available" — how to fix?
- Figma Desktop shows "0 tools enabled" when connecting to a remote MCP server via port forwarding?