How to connect the Atlassian Rovo MCP server

To connect the official Atlassian Rovo MCP server, add https://mcp.atlassian.com/v2/mcp to your MCP client as a Streamable HTTP server, then sign in with OAuth when your client prompts you. For headless use, authenticate with an API token if your admin allows it. Atlassian Rovo documents setup for VS Code, Cursor, Claude Code, Claude, Codex, Windsurf and ChatGPT.

Docs reviewed 5 Nov 2026Not a tested connection.

Try in the browser with your key →

Endpoint https://mcp.atlassian.com/v2/mcp · Registry com.atlassian/atlassian-mcp-server 2.0.0

Open in the Atlassian Rovo MCP explorer →Atlassian Rovo API profile →Markdown for agents

Add Atlassian Rovo MCP to your client

My client can't use OAuth: send a key from ATLASSIAN_ROVO_API_KEY

.vscode/mcp.json

{
  "servers": {
    "atlassian-rovo": {
      "type": "http",
      "url": "https://mcp.atlassian.com/v2/mcp"
    }
  }
}

support.atlassian.com github.com/atlassian

Connect Atlassian Rovo MCP step by step

Before you start

An Atlassian Cloud site with at least one of Jira, Confluence, Jira Service Management, Bitbucket or Compass. Actions run with your existing permissions on that site. github.com/atlassian support.atlassian.com
Using the server consumes Rovo credits. Usage limits depend on your Atlassian plan. support.atlassian.com
If your organization uses IP allowlisting, requests must come from allowed IP addresses. Hosted AI clients send requests from the provider's own IP addresses, so being on an allowed VPN may not be enough. github.com/atlassian
An organization admin controls which tool groups are available, must enable delete and manage tools for Jira, and must turn on API token authentication before anyone can use it. github.com/atlassian support.atlassian.com

Authentication

Your client → Atlassian Rovo MCP: OAuth sign-in, handled by your MCP client. support.atlassian.com github.com/atlassian modelcontextprotocol.io/specification
Atlassian Rovo MCP → Atlassian Rovo API: The server acts on your account with the access you approve. support.atlassian.com github.com/atlassian

Steps

Open Atlassian's Rovo MCP server setup instructions for your client
support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/
Add the Atlassian Rovo MCP server to your client
Add https://mcp.atlassian.com/v2/mcp as a remote MCP server that uses the Streamable HTTP transport (often labelled "http"). Atlassian also publishes plugins or extensions for Claude Desktop, Codex Desktop, Cursor and VS Code. Gateways that need every tool up front can add ?tools=all to the URL. The legacy /v1/sse endpoint is deprecated.
support.atlassian.com github.com/atlassian registry.modelcontextprotocol.io/v0.1
Sign in to Atlassian and approve access in the browser window
support.atlassian.com github.com/atlassian
For headless use, authenticate with an API token if your admin allows it
Send a personal API token as Basic authentication in the Authorization header, using your Atlassian account email and the token. For service accounts, send the service account API key as a bearer token in the Authorization header. Tokens aren't bound to one site, so clients must pass the cloud ID explicitly, and some tools aren't available with tokens. Jira Service Management supports only API token authentication, and Compass supports only OAuth.
support.atlassian.com github.com/atlassian
If you already use a v1 endpoint, expect v2 tools
On March 1, 2027 existing v1 connections start exposing v2 tools automatically. If a client fails to authenticate after the change, clear its cached client ID or .well-known credentials and connect again.
support.atlassian.com github.com/atlassian
List the server's tools
Your client should list the server's tools. That confirms the connection, not every API permission.
support.atlassian.com

What we observed

5 Nov 2026: HTTP 401 with WWW-Authenticate resource_metadata https://mcp.atlassian.com/.well-known/oauth-protected-resource/v2/mcp, which names an authorization server under https://auth.atlassian.com and Jira, Confluence and other agent-interface scopes.

Atlassian Rovo MCP questions

What is the Atlassian Rovo MCP server URL?

The official Atlassian Rovo MCP server is at https://mcp.atlassian.com/v2/mcp and uses the Streamable HTTP transport.

How do I authenticate with the Atlassian Rovo MCP server?

Sign in with OAuth when your client prompts you. For headless use, authenticate with an API token if your admin allows it: Send a personal API token as Basic authentication in the Authorization header, using your Atlassian account email and the token. For service accounts, send the service account API key as a bearer token in the Authorization header. Tokens aren't bound to one site, so clients must pass the cloud ID explicitly, and some tools aren't available with tokens. Jira Service Management supports only API token authentication, and Compass supports only OAuth.

Which AI clients can use the Atlassian Rovo MCP server?

Atlassian Rovo's documentation covers VS Code, Cursor, Claude Code, Claude, Codex, Windsurf and ChatGPT. Other clients that support remote Streamable HTTP MCP servers may also work.

What do I need before connecting Atlassian Rovo MCP?

An Atlassian Cloud site with at least one of Jira, Confluence, Jira Service Management, Bitbucket or Compass. Actions run with your existing permissions on that site. Using the server consumes Rovo credits. Usage limits depend on your Atlassian plan. If your organization uses IP allowlisting, requests must come from allowed IP addresses. Hosted AI clients send requests from the provider's own IP addresses, so being on an allowed VPN may not be enough. An organization admin controls which tool groups are available, must enable delete and manage tools for Jira, and must turn on API token authentication before anyone can use it.

Has this Atlassian Rovo MCP guide been tested?

Atlassian Rovo's documentation was reviewed on 2026-11-05. It is not a tested connection; your account and permissions decide which tools work.

Sources and review

Atlassian Rovo's documentation was checked on the dates shown. This guide follows the MCP Connect connection-guide draft, bound to the exact Registry record it describes. It is not a tested connection: your account and permissions decide which tools work.

Guide source and binding

MCP connection guide (draft 0.1) for com.atlassian/atlassian-mcp-server 2.0.0, bound to /remotes/0 of the Registry record by SHA-256 247f59b00874….

Guide JSON Source snapshot

support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ · checked 5 Nov 2026
github.com/atlassian/atlassian-mcp-server · checked 5 Nov 2026
support.atlassian.com/atlassian-rovo-mcp-server/docs/configuring-authentication-via-api-token/ · checked 5 Nov 2026
registry.modelcontextprotocol.io/v0.1/servers/com.atlassian%2Fatlassian-mcp-server/versions/2.0.0 · checked 5 Nov 2026
modelcontextprotocol.io/specification/2026-07-28/basic/authorization · checked 5 Nov 2026

All MCP connection guides →How we review MCPs →