Guides · Claude Code
How to connect the Atlassian Rovo MCP server to Claude Code
The Atlassian Rovo MCP Server is hosted by Atlassian, so there is nothing to install locally: Claude Code connects to https://mcp.atlassian.com/v2/mcp over HTTP and acts with your own Atlassian Cloud permissions. Atlassian's README says v2 is the recommended endpoint for new setups.
Steps summarize the official docs linked below, checked 2026-10-26. Client UIs change; if a menu name differs, the linked docs win.
1. Check what you need
An Atlassian Cloud site with Jira, Confluence, Jira Service Management, Bitbucket or Compass, and a browser for the OAuth 2.1 sign-in. Headless setups can use an API token instead, but only if an org admin has enabled API-token authentication (Atlassian Administration → Rovo → Rovo MCP server → Authentication).
2. Add the server
This is the command Atlassian's README gives for Claude Code. Add --scope user to make it available in every project, or --scope project to share it through .mcp.json.
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp3. Sign in with OAuth
Start a Claude Code session and run /mcp, select atlassian and complete the browser sign-in. Until then claude mcp list shows the server as needing authentication. Access is limited to what your Atlassian account can already see.
claude /mcp4. Or share it with the team in .mcp.json
This is the entry from Atlassian's own repository. Keep "type": "http": Claude Code reads an entry with a url but no type as a stdio server and skips it. Each teammate still signs in with their own account from /mcp.
{ "mcpServers": { "atlassian": { "type": "http", "url": "https://mcp.atlassian.com/v2/mcp" } } }5. Headless: authenticate with an API token
Create a scoped personal API token, base64-encode email:api_token as Atlassian's token guide shows, and pass it as a Basic Authorization header (a service account key uses Bearer instead). Jira Service Management tools only work with token auth; some Compass tools are not available with it.
echo -n "your.email@example.com:YOUR_API_TOKEN" | base64 claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp \ --header "Authorization: Basic BASE64_ENCODED_EMAIL_AND_TOKEN"6. Keep write tools behind a prompt
The server can create and update Jira issues, Confluence pages and Bitbucket content. An ask rule in .claude/settings.json makes Claude Code confirm every Atlassian tool call, so don't add an allow rule for mcp__atlassian__* unless you trust every write it can make.
{ "permissions": { "ask": [ "mcp__atlassian__*" ] } }
Good to know
- delete_jira and manage_jira permission groups are disabled by default; an admin has to turn them on. Leave them off unless you need them.
- Tokens are not bound to one cloudId and skip the OAuth domain allowlist, so prefer OAuth for interactive use and keep tokens scoped to the projects the agent needs.
- Atlassian suggests putting your Jira project key, Confluence space and cloudId in AGENTS.md so the agent makes fewer discovery calls.
- Every tool call is recorded in your organization's audit log (Atlassian Administration → Insights → Audit log).
- The legacy SSE endpoint (/v1/sse) stopped being supported after 30 June 2026; point old configs at /v2/mcp.
Sources
- Atlassian MCP Server README (GitHub) ↗
- Atlassian Support: Configure authentication via API token ↗
- Claude Code docs: Connect Claude Code to tools via MCP ↗
- Claude Code docs: Configure permissions ↗
Catalog verdict
From the AgentTask Atlas catalog entry (verified 2026-10-26). Based on official docs, not hands-on tested. New to MCP in Claude Code? Start with the general How to add an MCP server to Claude Code.
- Atlassian Rovo MCP Server · Atlassian · needs credentials
Pick it when the agent must read or update Jira issues, Confluence pages or Bitbucket repos; the README recommends the v2 endpoint for new setups.
Ask the catalog from inside Claude Code: the AgentTask Atlas MCP server is free, read-only and needs no account.
Compare by task: Databases & SQL · Git & GitHub repos · Code review · CI/CD · Infra & deploy · Debugging & observability · Library docs & research · Web fetching & scraping · Frontend & UI · Local files · Docs & writing · Build AI apps · Planning & reasoning · Utilities
⚠ No independent security audit: entries summarize official sources only. Review permissions and code before installing.