Using the Atlassian Remote MCP Server beta

[dimitar_navushtanov]

I add MCP server to Cursor but even it is green I can only GET information for tasks, I cannot add comments for example. The token I'm using is full access. Is there config in JIRA or I'm doing something wrong ? 

[Fabian E_]

how can i set the cloudId? i can correctly start my mcp client and authorize with atlassian in vscode copilot, but when i make a request with e.g. the getJiraIssue tool, it sends `"cloudId": "YOUR_CLOUD_ID"`

[Hunter Sinclair]

Would this work for hosted Jira Server instead of Jira Cloud?  

[J_D_ Santen]

@Fabian E_  

you can pick up the cloudId from #getAccessibleAtlassianResources 

for example in vscode / github copilot, for my agent session one of the first prompts for me is:

get my cloudID from #getAccessibleAtlassianResources

then copilot has my cloudId for as long as it stays in context.

[Akeem Jenkins]

I got this working in Cursor. 

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

This uses the the mcp-remote package from here: https://github.com/geelen/mcp-remote

Specifying the port was the key here as the mcp-remote proxies the oath2 callback. 

Remove debug if you don't want to see the details.

[Henri Cook]

Is there anywhere online I can get an easy tool listing before going through the effort of implementation? I'm interested to see if this can interact with Zephyr

[Nadir Jabbarli]

is it possible to connect Data Center Jira to MCP?

[Calum Leslie]

@Nadir Jabbarli No, at present only Cloud data sources are supported for the Atlassian remote MCP server.

[malcolm stanley]

How to troubleshoot this or see if there are issues? 
Using with Cursor and a variety of models. 
Yesterday tool calls were responsive. 
Today they appear to go into a black hole. 
No obvious way to see if there is an issue on the Atlassian side,
or to report an issue for support. 
I know it is beta - wondering what the protocol is? 

EDIT - now working but still wondering how to figure out why it bumped...

[Ian Cook]

Has anyone recently had issues with the MCP tools not working? 

I have this installed in Cursor, and the check indicates that all the tools are present, the connection is good, etc. (See first image). 

However, when I ask in chat to find a document in confluence (such as our onboarding docs) with specific instructions, it uses the right tool, but throws an error. 

Any suggestions on either what might be going on, or perhaps where to look for more information on the error locally? 
 

[Cyran Eilcan]

Would love to be able to use this from the Shortwave MCP client, but cannot due to oauth callback domain allow list. Can we get this enabled so that it works regardless of which MCP client/domain its used from? Or at least allow oauth callbacks to app.shortwave.com?

[Prawin Sankar]

Thanks for this great work @Kun Chen and Team. Has anyone tried setting this with Amazon Bedrock agents?

[paramasivam]

I tried to connect Atlassian MCP-server through github copilot in VS code but not able to do it.

"mcp": {

  "servers": {

    "atlassian": {

       "url": "https://mcp.atlassian.com/v1/sse",

       "transport": "sse",

       "command": "mcp-atlassian",

       "args": [

           "--jira-url", "https://your-company.atlassian.net",

           "--jira-username", "your.email@company.com",

           "--jira-token", "your_api_token",

           "--confluence-url", "https://your-company.atlassian.net/wiki",

           "--confluence-username", "your.email@company.com",

           "--confluence-token", "your_api_token"
        ],

      "env": {},

      "disabled": false

       }
   }
}

Tried with this code but getting this following error while running the server

2025-05-24 17:57:31.858 [info] Stopping server atlassian

2025-05-24 17:57:31.863 [info] Starting server atlassian

2025-05-24 17:57:31.864 [info] Connection state: Starting

2025-05-24 17:57:31.872 [info] Starting server from LocalProcess extension host

2025-05-24 17:57:31.875 [info] Connection state: Running

2025-05-24 17:57:32.679 [info] 401 status sending message to https://mcp.atlassian.com/v1/sse, will attempt to fall back to legacy SSE

2025-05-24 17:57:33.474 [info] Connection state: Error 401 status connecting to https://mcp.atlassian.com/v1/sse as SSE: {"error":"invalid_token","error_description":"Missing or invalid access token"}

2025-05-24 17:57:33.475 [error] Server exited before responding to `initialize` request.

Can someone provide me a solution for this.

[Shehab Elhawary]

for integrate with Cursor follow this recourse

https://github.com/sooperset/mcp-atlassian

[paramasivam]

@Shehab Elhawary Thanks for the info but I'm working with github copilot so I need solution for that.

[Dhruv Bhavsar]

I want to configure it in existing JIRA tools. But I am receiving this : 

GET https://mcp.atlassian.com/v1/sse "HTTP/1.1 401 Unauthorized"

Currently using the same headers I am able to access : 
https://api.atlassian.com/ex/jira/<client_id>/rest/api/3/project,

https://api.atlassian.com/ex/jira/<client_id>/api/3/search, etc. 

But using it like :: 

async with MCPServerSse(

        params=MCPServerSseParams(

            url='https://mcp.atlassian.com/v1/sse',

            headers=headers

        )

    ) as server:
Gets <401 error>

[Matthew Buchanan]

This is such a welcome development - big thank you to the team for enabling this - I had previously been looking at bridging GitHUb Copilot and Atlassian by means of Copilot extensions and Rovo which is fine to an extent, but the experience can be a bit clunky. Bringing this right into agent mode is a great integration - I was testing this last week and had a great experience where Copilot was keeping Jira tickets up to date whilst updating documentation in Confluence right from the same place I was making changes. 

I ran into one issue and I'm not sure if this is a bug or limitation, or something I'm doing wrong - I couldn't figure out how to create a task as a child of another task - so specifically creating subtasks which I believe cannot be created without specifying the parent. It looks like the create issue tool won't allow the agent to specify arbitrary fields like parent - I'm wondering if there could be a generic "fields" property in the same way that there appears to be in the edit Jira issue tool?

[Akshay Bhanderi]

How do I set it up for Q CLI?

[Carpusher Wu]

This is how I successfully configured in VSCode GitHub Copilot.

```settings.json

"mcp": {

    "servers": {

        "Atlassian": {

            "command": "npx",

            "args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse"]

        }

    }

}

```

[Mugur Marculescu]

Both mcp-remote and mcp-atlassian are community packages. I would strongly prefer to not have to use an intermediary, especially thinking about the nature of having an Atlassian hosted remote endpoint

mcp-remote assumes browser access for Oauth (acting as the user) this is a very personal use case and not well suited for any type of running service.

mcp-atlasian has *very limited tools* compared to the remote Atlassian MCP... when people point the mcp-atlassian package to the real endpoint, you are still not getting any of the benefits because it doesn't expose the rich toolset present in the real remote endpoint.

Please add support for API TOKEN based access to enable MCP Clients on a server to connect to the remote MCP server.

[Miguel Caballero]

The next command worked for me:

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

Basically it redirected me to an Oauth page and I accepted the permissions:

 

[buksy]

I tried both approaches mentioned here in `.vscode/mcp.json`

```

"atlassian2": {

"command": "npx",

"args": ["-y", "mcp-remote", "https://mcp.atlassian.com/v1/sse", "51328", "--debug"],

},

```

and

```

"atlassian1": {

"url": "https://mcp.atlassian.com/v1/sse",

"transport": "sse",

"command": "mcp-atlassian",

"args": [

"--jira-url", "https://XY.atlassian.net",

"--jira-username", "X",

"--jira-token", "Z",

"--confluence-url", "https://XY2.atlassian.net/wiki",

"--confluence-username", "X",

"--confluence-token", "Z"

],

"env": {},

"disabled": false

}

```

but none of them works with Copilot in VSC. The Copilot does not recognize the server. It can try to use them as tool when instructed but it hangs up and never finishes.

[Roger Abelenda]

When I try to integrate Atlassian MCP in my tool and the permission access is cancelled in the Oauth atlassian page, I get a redirect to https://mcp.atlassian.com/v1/callback?error=access_denied instead of the url of my app (which is correctly invoked when user accepts permissions).



I am missing some configuration or parameter in initial oath request to Atlassian MCP? Or is this a known bug?

Thank you

[Oleksii Golikov]

Please add support for Managing Issue Links at the moment agents tries to use editJiraIssue tools but failing, seems like a new Tool is needed for that purpose

[Dominic Utz]

Hi, 

out of a data security pov: is it possible to restrict the global API Key with an Security scheme? If I connect the MCP with Cursor, all personal data would be available, or not? 

Best
Dominic