Chat does not work anymore after connecting to mcp

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

After my project was connected to figma mcp, the chat has not been working anymore. The chat keeps trying to reconnect and eventually return internal error, even when the prompt is irrelevant from figma. When looking at devtool it gives [composer] No first token received within x.

Tried change from auto to other models, disabling all mcps and removing them, tried --disable-extensions flag and tried reinstalling, still not work. Tried on my windows machine but results and errors are the same. I can see it did consume tokens but because of error it didn’t count in my usage.

However this only affect the project that connected to figma, the chat works normally on other project.

Steps to Reproduce

  1. add figma mcp
  2. connect and auth the cursor to figma
  3. anything submit to chat will keep it reconnects to the server

Expected Behavior

consume credit and return responses

Operating System

Linux

Version Information

Version: 2.4.35
VSCode Version: 1.105.1
Commit: d2bf8ec12017b1049f304ad3a5c8867b117ed830
Date: 2026-02-10T02:46:56.793Z
Build Type: Stable
Release Track: Default
Electron: 39.5.1
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Linux x64 6.18.8-zen2-1-zen

For AI issues: which model did you use?

Auto, composer 1.5, grok code

For AI issues: add Request ID with privacy disabled

Request ID: cb8aa3fe-cf6e-472e-84d7-45b7c7df8e76
[internal] Failed to run step, exceeded max retries
OTe: [internal] Failed to run step, exceeded max retries
    at cpf (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:38348)
    at opf (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:37251)
    at _pf (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:5088)
    at Tva.run (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:9098)
    at async Vyt.resume (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34206:60624)
    at async mgc.streamFromAgentBackend (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34255:7835)
    at async mgc.getAgentStreamResponse (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34255:8576)
    at async qTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9180:14965)
    at async Xi (vscode-file://vscode-app/usr/share/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:33004:3808)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report.

Since the issue only shows up in this specific project (even after removing MCP and reinstalling), it looks like there might be some corrupted cache or state left in the project directory. Could you try this:

  1. Make sure the .cursor/mcp.json file in the project folder is either deleted or completely empty (with no Figma mentions).
  2. Try deleting the entire .cursor folder in this project (back it up first if it has rules or other config), then reopen the project.
  3. If that still doesn’t help, try opening the project in a brand new Cursor window using cursor --new-window /path/to/project.

Also, when you said you removed MCP, did you remove both the project config .cursor/mcp.json and the global config ~/.cursor/mcp.json?

Let me know how the steps above go.

Thanks for the reply. It is working now!

Both .cursor/mcp.json and ~/.cursor/mcp.json were removed but the error still occurs. However when I removed the entire .cursor folder, open cursor in a new window and open a new chat, it works.

So I guess there is something to do with rules in .cursor that makes the chat unusable.
Thanks for your help! Really appreciate that.

1 Like

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.