Cursor 1.4.4 Cannot load remote mcp tools

Bug Reports
1

Describe the Bug

Cannot load tools from given url , works with 1.3 but not 1.4.4

Steps to Reproduce

Install any remote mcp via mcp.json config

Expected Behavior

Should ask for login with oauth and show tools like before

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.4.4 (Universal)
VSCode Version: 1.99.3
Commit: dd05130a0bf8d5f1a5372e6e6bb7c4184786eaa0
Date: 2025-08-10T22:39:50.197Z
Electron: 34.5.1
Chromium: 132.0.6834.210
Node.js: 20.19.0
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

2 Likes
2

Hey, thanks for the report. Could you let me know which MCP servers you are using?

3

It is a custom remote mcp server I made in python with fastmcp library, works well with oauth on cursor 1.3

4

Could you please share the repository of your server so the team can take a look?

5

@deanrie @BuiDGr8 could you post the solution here once found as it will help me as well. I am facing the same issue

1 Like
6

Seeing the same issue. Custom MCP server with OAuth and was working previously, but errors now with the message below. Claude code authenticates fine and shows all tools, so looks like something broke with your implementation.

You’re also still hanging onto old client ids even after uninstall, which requires a full cursor reinstall to get around.

2025-08-20 16:27:21.922 [info] Creating streamableHttp transport
2025-08-20 16:27:21.922 [info] Connecting to streamableHttp server
2025-08-20 16:27:21.953 [info] OAuth provider needs auth callback during connection
2025-08-20 16:27:21.953 [error] Error connecting to streamableHttp server, falling back to SSE: Unauthorized
2025-08-20 16:27:21.954 [warning] Unauthorized error connecting to streamableHttp server, returning transport
2025-08-20 16:27:21.954 [info] Successfully connected to streamableHttp server
2025-08-20 16:27:21.954 [info] Storing streamableHttp client
2025-08-20 16:27:21.954 [info] Connected to streamableHttp server, fetching offerings
2025-08-20 16:27:21.954 [info] Found 0 tools and 0 prompts
2025-08-20 16:27:27.909 [info] Received OAuth callback with code
2025-08-20 16:27:27.953 [error] Failed to complete OAuth exchange An unknown error occurred. Please consult the log for more details.

This is on 1.4.5

Version: 1.4.5 (Universal)
VSCode Version: 1.99.3
Commit: af58d92614edb1f72bdd756615d131bf8dfa5290
Date: 2025-08-13T02:08:56.371Z
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.5.0
7

@deanrie I’m not seeing a client_id or client_secret in the request body to my token exchange request at /oauth/tokenand suspect that could be the source of the issue

Here’s a comparison of the payloads I see from the Claude Code vs. Cursor

// Claude code (works)

[DEBUG] OAuth token request body: {
  "grant_type": "authorization_code",
  "client_id": "aucl:v5PDzgHsbqxBqevqL4Ea0lzA",
  "code": "...",
  "code_verifier": "...",
  "redirect_uri": "http://localhost:55093/callback",
  "client_secret": "...",
  "resource": "http://localhost:8080/"
}

// Cursor (does not work)
[DEBUG] OAuth token request body: {
  "grant_type": "authorization_code",
  "code": "....",
  "code_verifier": "...",
  "redirect_uri": "cursor://anysphere.cursor-retrieval/oauth/user-mymcp/callback",
  "resource": "http://localhost:8080/"
}
8

Still seeing no client_id or client_secret on 1.5.5

9

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