Atlassian Rovo MCP server
Atlassian's official cloud server for Jira, Confluence, Compass and other Atlassian Cloud products, respecting each user's existing permissions. Authorize through OAuth 2.1 or an admin-enabled API token.
Remote (HTTP)OAuth
Set up Atlassian Rovo
Configuration examples, not tested connections. Replace placeholders and review the upstream documentation before use.
Claude Code
Run in your terminal.
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp
Cursor
Merge into ~/.cursor/mcp.json
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
Codex
Run in your terminal.
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp
codex mcp login atlassian
Gemini CLI
Merge into ~/.gemini/settings.json
{
"mcpServers": {
"atlassian": {
"httpUrl": "https://mcp.atlassian.com/v2/mcp"
}
}
}
OpenCode
Merge into ~/.config/opencode/opencode.jsonc
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"atlassian": {
"type": "remote",
"url": "https://mcp.atlassian.com/v2/mcp",
"enabled": true
}
}
}
VS Code
Merge into .vscode/mcp.json
{
"servers": {
"atlassian": {
"type": "http",
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}
Using more than one server?Add to a config with other servers
Step-by-step setup guides: Claude Code and Codex CLI, Cursor and VS Code. In Claude Desktop, add the URL as a custom connector. This is a remote server with OAuth sign-in; see remote vs local servers and authentication and security basics.
Overview
The Atlassian Rovo MCP Server is Atlassian's official, cloud-hosted bridge between Atlassian Cloud and external AI tools. It is documented in atlassian/atlassian-mcp-server, which had commits on 7 October 2026. New setups should use the v2 endpoint at https://mcp.atlassian.com/v2/mcp. The legacy SSE endpoint is no longer supported after 30 June 2026.
The server covers Jira, Confluence, Bitbucket Cloud, Jira Service Management, Compass, Loom and Atlassian's Goals, Projects and Teams. Typical calls include getAccessibleAtlassianResources to find your site, searchJiraIssuesUsingJql, getJiraIssue and createJiraIssue for Jira, and searchConfluence and getConfluenceContent for Confluence. Instead of sending every tool at connection time, it exposes a small set of frequently used tools and lets the client discover the rest. Gateways that need a flat list can add ?tools=all.
Authentication is OAuth 2.1 through a browser by default. For headless setups, an admin can enable API-token authentication. Jira Service Management tools only work with API tokens. Access is limited to data the user can already see, and admins control which permission groups are enabled. Delete and manage operations for Jira are off by default. In Claude Code, run /mcp to finish signing in, and in Codex use codex mcp login atlassian.
Example tools
getAccessibleAtlassianResourcessearchJiraIssuesUsingJqlgetJiraIssuecreateJiraIssuesearchConfluencegetConfluenceContent
Tool names are upstream examples. The server's live tool list can differ.
Related Productivity servers
Sources
This page was written from the upstream documentation below and last reviewed on 11 October 2026. Listing is not a security or compatibility endorsement. Report a correction through the contact page.