Attlasian ROVO MCP is not fetching the details / Not Authenticating via browser

[Maniteja Varanasi]

Hello Team,

We are using Atlassian Rovo Mcp tool earlier it was working , but from last Wednesday/Thursday it was not working properly or not authenticating the atlassian instance via browser .

Below is the config server we are using 

mcpServers:

- name: "atlassian-rovo"

description: "Access Atlassian Jira and Confluence via Rovo MCP (npx-based, SSL verification disabled for corporate network)"

command: "npx"

args:

- "-y"

- "mcp-remote@latest"

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

env:

ATLASSIAN_SITE_NAME: "xxxxx"

ATLASSIAN_USER_EMAIL: "xxxxxx"

ATLASSIAN_API_TOKEN: "xxxxxx"

NODE_TLS_REJECT_UNAUTHORIZED: "0"

Can you please let me know if this right or any changes need to be done or any other mcp yaml config we need to use ?

[Dr Valeri Colon _Connect Centric_]

Welcome to the community @Maniteja Varanasi  Your config is close, but the main thing to check is whether API token auth is enabled by your org admin for Atlassian Rovo MCP. If it isn’t, browser auth is required and token-based setup will fail.

Also, NODE_TLS_REJECT_UNAUTHORIZED=0 only bypasses cert checks; it won’t fix auth. If this worked before and broke last week, it may be an auth/session issue or MCP regression. Re-auth and have your admin confirm MCP auth settings.

[Maniteja Varanasi]

@Dr Valeri Colon _Connect Centric_  Sure, thanks . But it was working for few members who are using MCP first time they are able to authenticate MCP via browser.Not sure if there is some issue but most people had issues. 

Can you please share the steps for API token auth is enabled by org admin for Atlassian Rovo MCP. Thanks ! 

[Dr Valeri Colon _Connect Centric_]

@Maniteja Varanasi  that’s helpful context—if new users can authenticate but existing ones can’t, that points more to a session/OAuth issue or partial rollout/regression, not just config.

For API token auth: this has to be enabled at the org level under Atlassian Admin → Security → API tokens / MCP settings (exact naming can vary as it’s evolving). Not all orgs have it enabled yet. If browser auth is inconsistent across users, I’d:

• Revoke + re-authenticate MCP access
• Clear cookies/session
• Check with admin if MCP auth policies changed

If still failing, likely backend → support is best next step.