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.
/v1/mcp
Try: npx -y mcp-remote <a href="https://mcp.atlassian.com/v1/sse" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/sse</a>
npx -y mcp-remote <a href="https://mcp.atlassian.com/v1/sse" target="_blank" rel="nofollow noopener noreferrer">https://mcp.atlassian.com/v1/sse</a>
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.
It looks like you're new here. Sign in or register to get started.
