There are a few known issues around MCP Auth and Cursor in 3.x. To determine whether this matches a known issue, could you share your mcp.json file and specify which MCP servers you’re trying to use? For example, we’ve received specific feedback about Atlassian and Webflow MCP servers.
I worked with a user yesterday who got past this issue by running Cmd + Shift + P > Cursor: Clear All MCP Tokens from the Editor window, and reconnecting their MCP server. Could you give that a try?
Hi @Colin , I’m from the same team as Karlis, are there any updates on the above issue? any timelines for the fix? it becomes critical for our project because as you can see this completely blocks further MCP integration.
so after resorting to good old network capture I figured out what’s wrong
our oAuth configuration was wrong
it was never meant to work honestly and because older Cursor versions auto-magically got around I was under impression that our setup is correct
e.g. this should probably never work and possibly even empty array
authorization_servers: [null],
Can you please add response validation for /.well-known/oauth-protected-resource response?
also please log response (at least in debug mode) and which auth URL will be tried to expedite debugging
we would have caught issue much earlier if Cursor wouldn’t try to be so nice