Trouble with authenticating MCP server on Cursor

Srinath Chandrasekaran_2u6bkw

I am trying to setup Atlassian MCP on cursor code editor and I am facing the following problems

1. When I try to use the remove SSE URL using the following :
```"Atlassian-MCP-Server": { "url": "https://mcp.atlassian.com/v1/sse" }```
When I Connect for auth, I am getting the following error post redirect to cursor: 

`[error] Failed to complete OAuth exchange Invalid PKCE code_verifier`

The whole log is as follows
```

[info] Received OAuth callback with code

2025-09-09 14:09:03.442 [info] Using redirect URL {"url":"cursor://anysphere.cursor-retrieval/oauth/user-Atlassian-MCP-Server/callback"}

2025-09-09 14:09:05.526 [info] Using redirect URL {"url":"cursor://anysphere.cursor-retrieval/oauth/user-Atlassian-MCP-Server/callback"}

2025-09-09 14:09:08.930 [error] Failed to complete OAuth exchange Invalid PKCE code_verifier```

2. I have been using mcp-remote of npx to connect to the same by following 
```"mcp-atlassian-api": { "command": "npx", "args": [ "mcp-remote", "https://mcp.atlassian.com/v1/sse" ] }```

Here the issue is every window, I have to approve auth and every few hours it asks for auth again. 

Need some assistance on this as this has been really unusable.

Dr Valeri Colon (Connect Centric)

@Srinath Chandrasekaran The Atlassian Remote MCP server isn’t fully supported in Cursor yet. Its OAuth flow uses a PKCE pattern Cursor can’t complete, which causes the Invalid PKCE code_verifier error. With mcp-remote, the token isn’t durable because Atlassian hasn’t opened long-lived tokens for external MCP clients—so reauth every window is expected. There’s no stable integration path until Atlassian releases a supported auth flow.