Atlassian MCP server: Rovo access for every agent

Rovo is a combined product connection. A single authorization can bring Jira issue context and Confluence documentation into a task, while the live server decides the available operations. Check the discovered tool descriptions before assigning a job. The same vendor may add or change tools without this article becoming a complete inventory.

A good first request asks for one Jira issue and its supporting Confluence page, with links to both. Have the agent distinguish the issue’s current status from the wiki’s intended behavior. That prevents a stale design note from being presented as a delivered feature.

AIPx currently connects the vendor’s supported v1/mcp route. Atlassian now recommends v2/mcp for new direct setups; the older route remains supported and receives updated tools. Follow the vendor’s current direct instructions when configuring a client without AIPx.

Atlassian Rovo MCP server vs AIPx

The official Atlassian MCP documentation owns vendor access requirements. The mcp-atlassian repository is a distinct community route. AIPx does not replace Rovo’s server or claim to supply every resource, prompt or subscription primitive the upstream protocol supports.

If you want explicit REST operations rather than the Rovo surface, use the separate Jira adapter and Confluence adapter. Direct Rovo is simpler for a single client. A gateway is useful when several agents should see different portions of the same connection, but it adds another service processing their requests.

Connect Atlassian to Claude, Claude Code, Cursor or Codex

Choose Atlassian Rovo in AIPx and complete Atlassian OAuth. Do not paste the REST adapter API token here: Jira REST and Confluence REST are separate connection choices.

1. Open the AIPx dashboard, choose Atlassian under Integrations and complete its connection form or authorization.
2. Create an MCP agent, enable that connection and choose the tools this particular agent needs. Save the rules before opening your AI client.
3. Copy the agent’s complete URL. The examples below use AGENT_ID; replace it with the actual value from your dashboard.

An endpoint identifies the AIPx agent, not a provider API key. Client authentication to AIPx is separate from connecting Atlassian; adding the URL does not grant extra provider permissions. Our MCP gateway guide explains how several approved connections can share that endpoint.

Connect Claude to Atlassian

In Claude, open Customize → Connectors and add a custom connector with your AIPx URL. Continue through AIPx sign-in, then check the tools available in a conversation. Custom connector access depends on account and workspace policy; administrators can restrict it. The Claude MCP setup guide covers the current controls. A direct vendor connection can be simpler when Atlassian is the only service you need.

Atlassian MCP in Claude Code

claude mcp add --transport http aipx https://dash.aipx.run/mcp/AGENT_ID

Use /mcp to authorize the AIPx connection, then inspect the discovered Atlassian catalog. Fetch one Jira issue and its wiki link before granting writes. The Claude Code guide covers login and scope.

Atlassian MCP in Cursor

Add this server to .cursor/mcp.json for the project or ~/.cursor/mcp.json for your user:

{
  "mcpServers": {
    "aipx": { "url": "https://dash.aipx.run/mcp/AGENT_ID" }
  }
}

Complete Cursor OAuth and inspect which Jira and Confluence tools your Rovo account exposes. Try reading one linked specification before enabling edits. Cursor MCP setup explains server discovery.

Atlassian MCP in Codex

codex mcp add aipx --url https://dash.aipx.run/mcp/AGENT_ID
codex mcp login aipx
codex mcp list

Codex uses the HTTP endpoint and browser OAuth; it does not need a copy of the Atlassian credential in its config. See Codex MCP setup for TOML configuration and project trust requirements.

A ChatGPT workspace with custom MCP access can add this agent URL for Atlassian context. Product and tool availability still comes from the authorized Rovo account. Check the ChatGPT MCP guide for current client and policy requirements.

Scope Jira and Confluence separately per agent

A ticket triage agent can have Jira reads enabled while Confluence page edits stay hidden. A documentation assistant can read issues and propose wiki updates without being able to transition tickets. Assign modes to the concrete tools discovered from your connection; product labels alone do not isolate access.

Keep cross-product search only where the agent needs that breadth. General read tools default to Allow and writes to Confirm, but your task may justify hiding a read tool that returns sensitive wiki content. Confirm relies on client approval behavior. MCP access control describes how Hide removes visibility and callable access.

Add Atlassian MCP to Claude Code

Use the command in the Claude Code subsection below with the AIPx URL, not a copied direct Atlassian URL. The client signs in to AIPx; Atlassian authorization has already occurred at the connection step. Verify that /mcp shows the intended server before asking for Jira or wiki context.

Atlassian MCP in Cursor and Claude

Both clients use the same agent endpoint. You can choose different AIPx agents if Cursor should only read issues while Claude is allowed to propose page writes. Notion and GitHub can supply additional sources, but they do not inherit Atlassian permissions.

Connect Atlassian to ChatGPT

Use custom MCP only when your ChatGPT account and workspace permit it. A vendor Atlassian connector and a custom AIPx endpoint are separate setup paths; choose the latter for AIPx tool rules. The client guide linked below describes current access restrictions.

Atlassian permissions and discovered-tool limits

A prompt cannot reduce the OAuth scopes you granted upstream. Atlassian account and product permissions remain the outer boundary; AIPx tool visibility is a further restriction within it. If Confluence data must be inaccessible, use appropriate Atlassian authorization as well as hiding Confluence tools.

Vendor changes can affect discovery, supported products and available features. When a tool is missing, inspect the actual authenticated catalog and the account’s product access. Do not assume a similarly named tool from an old setup guide must still exist. AIPx’s tool highlights describe capabilities rather than inventing stable names for unavailable metadata.

Browse all MCP integrations to choose another connection for this agent.

The Atlassian connection can use AIPx Free with 3 active accounts and 1 agent; check AIPx pricing for gateway plans and keep provider or client charges separate.