Atlassian Remote MCP Server beta now available for desktop applications

[Avneet Saxena]

[20172] [20172] Connecting to remote server: https://mcp.atlassian.com/v1/sse
[20172] Using transport strategy: http-first
Could not load OAuth Protected Resource metadata, falling back to /.well-known/oauth-authorization-server Error: Resource server does not implement OAuth 2.0 Protected Resource Metadata.

Getting this now on starting the Jira MCPd. It was working on June 6th . Any idea anyone ?

[Jose Martinez]

Looks like they removed compass from the OAUTH scopes.

This is working for me today 🥳.

[Satheesh Balachandran]

Hi, What are the available authentication mechanism available? Will be only via 3LO OAuth, where we have to open the URI in browser and authenticate to the server?

To connect this MCP with agents, are there options to connect via PAT or API Tokens on a headless service?

[Jitendra Vyas]

I m getting this message when I try to use it in our company. We are not able to find solution for it 

[henriquevalcanaia]

Started getting this from Cursor:

```log

2025-06-19 12:09:22.853 [info] user-atlassian: Handling CreateClient action

2025-06-19 12:09:22.854 [info] user-atlassian: Starting new stdio process with command: npx -y mcp-remote https://mcp.atlassian.com/v1/sse

2025-06-19 12:09:23.399 [error] user-atlassian: file:///Users/henrique/.npm/_npx/705d23756ff7dacc/node_modules/open/index.js:7

import fs, {constants as fsConstants} from 'node:fs/promises';

^^^^^^^^^

SyntaxError: The requested module 'node:fs/promises' does not provide an export named 'constants'

at ModuleJob._instantiate (node:internal/modules/esm/module_job:128:21)

at async ModuleJob.run (node:internal/modules/esm/module_job:194:5)

at async Promise.all (index 0)

at async ESMLoader.import (node:internal/modules/esm/loader:385:24)

at async loadESM (node:internal/process/esm_loader:88:5)

at async handleMainPromise (node:internal/modules/run_main:61:12)

2025-06-19 12:09:23.405 [info] user-atlassian: Client closed for command

```