Skip to main content

How to Connect Atlassian

🔧 Tools · MCP

The Atlassian Rovo MCP Server at https://mcp.atlassian.com/v1/mcp/authv2 exposes Jira (read/write issues, search), Confluence (pages, comments, spaces, search), and Compass. Every tool call runs with the connecting user's own Atlassian permissions.

Atlassian does not accept pre-registered OAuth apps for this server, so there is no app to create. The platform registers its OAuth client through Dynamic Client Registration (DCR, RFC 7591) on first connect. Atlassian identifies MCP clients by the domain of their redirect URI, and an organization admin controls which domains may connect.

1. Allow the Platform Domain in Atlassian Administration​

An organization admin of the Atlassian Cloud organization that owns the Jira/Confluence data must:

  1. Go to admin.atlassian.com and select the organization.
  2. Open Rovo → Rovo MCP server and make sure the MCP server is enabled for the organization.
  3. Select Add domain and add the platform API host as a URL pattern, e.g. https://api.zeta-alpha.com/** (see The Platform Callback URL for the host of your tenant).

See Control Atlassian Rovo MCP server settings for the full admin reference.

2. Add the Server to the Tenant​

Add a server under the tenant's MCP Servers (see Adding a Server to the Tenant):

FieldValue
Nameatlassian
URL, OAuth resource URLhttps://mcp.atlassian.com/v1/mcp/authv2

Leave the client ID and secret empty: the platform registers a client with Atlassian through DCR and caches it per tenant.

3. Mount It and Connect​

Mount atlassian on the agent (Mounting a Server on an Agent). The first connect runs endpoint discovery and client registration inside the MCP initialize call, which takes longer than the default 2-second setup timeout. Raise it next to the mount:

{
  "mcp_tools_provider_configuration": {
    "enabled": true,
    "client_session_timeout_seconds": 15,
    "mounts": [{ "name": "atlassian" }]
  }
}

Each user then connects Atlassian from Connected apps in the chat, or through the Authorize atlassian button the agent shows when a request needs it (e.g. "Find the Confluence page about onboarding"), and approves the requested scopes. See Connecting from the Navigator.

Troubleshooting​

SymptomCause
Atlassian login shows "Access to this domain is restricted"The redirect domain is not on the organization's allowed-domains list (step 1). If it was just added and the error persists, delete the entry and add it again; see Atlassian's KB.
Logs show Request 'initialize' timed out and the server never connectsclient_session_timeout_seconds is too low for the discovery and registration handshake (step 3).
Authorization succeeds but tools return permission errorsTokens carry the end user's own Atlassian permissions; the user lacks access to the requested project/space.