Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
I added my custom MCP server under “Tools & MCP”.
The settings are as follows:
{
"mcpServers": {
"weegloo": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://{my-remote-mcp-server}/mcp",
"--header",
"Authorization:Bearer XXXXX"
]
}
}
}
The MCP server was successfully registered.
However, when I try to talk to the Agent afterward, the following error appears:
We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.
(Request ID: 11d29f24-7912-4aef-b66c-bf517c799b7b)
After logging out and signing in as a Free Plan user, it works normally.
However, when logging in again as a Pro Plan user, the same error still occurs.
The issue occurs on both Windows and macOS.
Steps to Reproduce
- Add MCP Server
- Ask something to AI
Screenshots / Screen Recordings
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.54 (system setup)
VSCode Version: 1.99.3
Commit: 5c17eb2968a37f66bc6662f48d6356a100b67be0
Date: 2025-10-21T19:07:38.476Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Windows_NT x64 10.0.26100
For AI issues: add Request ID with privacy disabled
Request ID: 11d29f24-7912-4aef-b66c-bf517c799b7b
Request ID: 11d29f24-7912-4aef-b66c-bf517c799b7b
{“error”:“ERROR_OPENAI”,“details”:{“title”:“Unable to reach the model provider”,“detail”:“We’re having trouble connecting to the model provider. This might be temporary - please try again in a moment.”,“additionalInfo”:{},“buttons”:,“planChoices”:},“isExpected”:false}
ConnectError: [unavailable] Error
at t7l.$endAiConnectTransportReportError (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7337:375292)
at TMr._doInvokeHandler (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:489:35946)
at TMr._invokeHandler (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:489:35688)
at TMr._receiveRequest (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:489:34453)
at TMr._receiveOneMessage (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:489:33275)
at cEt.value (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:489:31369)
at _e._deliver (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:2962)
at _e.fire (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:49:3283)
at cdt.fire (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7322:12154)
at MessagePort. (vscode-file://vscode-app/c:/Program%20Files/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9402:18292)
Does this stop you from using Cursor
No - Cursor works, but with this issue
