Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
It seems cursor is either not following DCR procedure properly or there is something else wrong. Cursor MCP is fundamentally broken. Multiple problems:
- Redirect after authentication opens a new cursor agent window - doesn’t get registered.
- npx mcp-remote based servers: get client not found error.
Goose desktop client doesn’t have these issues with the same configuration. It is fundamentally something that is going wrong with oauth authentication flow in cursor. It is not working correctly. Only thing that works right now is running local server and authenticating through mcp-remote with it.
Steps to Reproduce
Try connecting to any mcp server without mcp remote. With mcp remote sometimes it does sometimes it doesn’t. Try for example atlassian mcp.
Expected Behavior
Authentication flow should terminate with cursor having the token. It doesn’t.
Operating System
Linux
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.7.33
VSCode Version: 1.99.3
Commit: a84f941711ad680a635c8a3456002833186c4840
Date: 2025-10-03T03:28:06.574Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Linux x64 6.14.0-33-generic
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor