Welcome to the community @Aaron Liang That error usually happens because Cursor’s MCP client still expects the /v1/sse endpoint, not /v1/mcp. Atlassian’s remote MCP server won’t complete the auth flow through /v1/mcp, which leads to the “something went wrong” message after approval.
Try: npx -y mcp-remote https://mcp.atlassian.com/v1/sse
Also ensure a browser window opens for OAuth and that you approve with the same Atlassian account used in Cursor. If it still fails, retry in a clean browser profile—cached sessions can break the redirect.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.