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

```

[Anjan Sp]

Hello @Kun Chen I'm getting an error while creating new tickets, and it says there are some required fields missing. However, AI agent is not able to add those required fields because they are all custom fields.

Are custom fields currently supported while creating new Jira tickets through MCP?

[Jose Martinez]

@Anjan Sp - Prompt the llm to fill out the required fields, guide the llm so that it fetches the ids of the custom fields before it creates the ticket.

example:
```
Create a new ticket ...

Fill out the following required fields:
* Name
* Acceptance Criteria
* ETC

Some of the required fields are custom fields - if you do not know the custom field ids, retrieve them from JIRA before creating the ticket.
```

[S Jain_ Gokul]

When i am trying to connect to  the vs code with the settings.json as,

"MCP-Confluence": {

"command": "npx",

"args": [

"-y",

"mcp-remote",

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

]

the server is getting connected but the tools are not listed in copilot chat. Is that any authtication error .

I also tried in terminal with ,

npx -y mcp-remote https://mcp.atlassian.com/v1/sse

facing this error .

npx -y mcp-remote https://mcp.atlassian.com/v1/sse
[1466] Using existing client port: 5598
[1466] [1466] Connecting to remote server: https://mcp.atlassian.com/v1/sse
[1466] 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.
at discoverOAuthProtectedResourceMetadata (file:///Users/gsjain/.npm/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-4PNJQ7WT.js:12070:11)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async authInternal (file:///Users/gsjain/.npm/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-4PNJQ7WT.js:11959:30)
at async auth (file:///Users/gsjain/.npm/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-4PNJQ7WT.js:11944:12)
at async StreamableHTTPClientTransport.send (file:///Users/gsjain/.npm/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-4PNJQ7WT.js:13022:26)
[1466]
Please authorize this client by visiting:
https://mcp.atlassian.com/v1/authorize?response_type=code&client_id=yIexkGcsdCHrI7KK&code_challenge=t_K1_vR3jjlfk_1Uo9CKXTidWl722Kv5vUJp4j-b6p4&code_challenge_method=S256&redirect_uri=http%3A%2F%2Flocalhost%3A5598%2Foauth%2Fcallback&state=eebccdc2-cf42-4e91-b72a-f5a0e1ba4df9

[1466] Browser opened automatically.
[1466] Authentication required. Initializing auth...
[1466] Initializing auth coordination on-demand.

is there any fix to this while working on vs code .