Atlassian MCP connect: browser can't open URI cursor://

Support Help
,
1

Hello

On a linux redhat 8 server. cursor 2.3.26
I have added a MCP config for our atlassian site.

When i hit connect, the browser opens the first configuration page: Atlassian ROVO MCP server, to select the apps (i click approve),

then the page where Atlassian MCP requests access to my Atlassian account.
On this page when i click accept i get the following behaviors:

  • if i configure cursor to use chromium: an error popup: Failed to open URI The specified location is not supported: cursor://anysphere.cursor-mcp/oauth/callback?code=…&state=…
  • if i configure cursor to use firefox: the page waits indefinitely for an answer but the request response contains NS_ERROR_UNKNOWN_PROTOCOL

I’m stuck here. Can anyone help with this issue ? (PS: i’m not an admin on the server but i can request help from the IT if some admin actions are necessary)

3

Hi @cc_aip ,

My Cursor setup:

Version: 2.3.29 (user setup)
VSCode Version: 1.105.1
Commit: 4ca9b38c6c97d4243bf0c61e51426667cb964bd0
Date: 2026-01-08T00:34:49.798Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.22621

Using this Atlassian MCP config…

{
  "mcpServers": {
    "forge-knowledge": {
      "url": "https://mcp.atlassian.com/v1/forge/mcp"
    },
    "Atlassian-MCP-Server": {
      "url": "https://mcp.atlassian.com/v1/sse"
    }
  }
}

With "Google Chrome” set as the default browser, I can successfully login to the Atlassian MCP Server (see attached).

image
image808Ă—425 18.1 KB

For the 2nd page you mention I successfully get to the permissions acceptance page, click “Accept”, it asks me if I want to return to Cursor.

image
image552Ă—1011 31 KB

At this point I wait a bit, it seems like it is stuck, but the authorisation eventually goes through.

Please note, I am not behind any corporate firewall here though. This is an independent (public) test.

Perhaps there’s a little digging with IT about how your authentication and authorisation gets passed back to Cursor?

HTH (a bit),

Justin

4

Hi Justin,

Thanks a lot for your answer. I have some colleagues who completed the connection process successfully on windows (like you) but it seems i’m the only one trying to do it on linux.
From suggestions by another colleague i tried a different configuration:

"Atlassian": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.atlassian.com/v1/sse"
      ],
      "env": {}
    }

and indeed, it authenticates succesfully and goes back to cursor. However still have an error and no tool is loaded:
image

image
image973Ă—506 114 KB

5

Hi @cc_aip ,

That’s Cursor running with WSL2, so for example I would ask the agent to contribute to the “codebase / whatever” from the agent chat using the Atlassian MCP.

One thing I have found with the Atlassian MCP tools is that sometimes they are loaded even though Cursor MCP connections in settings might be showing an error.

Did you take the extra step to ask an agent to specifically use the knowledge bases of the MCP connection(s) or that they could “see” them? :slight_smile:

Justin

7

I didn’t try, I will.
Thanks for the help

8

Hey! This is a known issue with registering the cursor:// protocol on Linux.

Fix: Switching from the AppImage to the .deb version of Cursor fixes the OAuth callback issue. Download the .deb installer here: Download · Cursor

If you need an .rpm build for Red Hat, it’s also available on the downloads page.

Why this works: The .deb and .rpm builds correctly register cursor-url-handler.desktop with the --open-url flag, so the browser can pass the OAuth callback back to Cursor.

Alternative (if you can’t install the .deb): Use the npx approach like you tried in post #4. If MCP shows an error but auth worked, try asking the Agent to use the Atlassian tools. Sometimes they work even if Settings still shows an error.

Let me know if this helped!

1 Like
9

Thanks a lot Dean, i’ll try that and post the result here.

10

it works flawlessly with the .rpm and this config:

"Atlassian-MCP-server": {
      "url": "https://mcp.atlassian.com/v1/sse",
      "type": "sse"
    }

thanks a lot to both of you for your help