The Atlassian Rovo MCP Server connects your AI agent to your Atlassian apps and work in a single conversation, powered by your Teamwork Graph. Once connected, your AI client can summarize and search Jira, Jira Service Management, Confluence, and Bitbucket without switching tools, retrieve Loom recordings, create and update work items or pages using natural language, and automate repetitive tasks such as generating work from meeting notes or specs.

The server is powered by secure OAuth 2.1 authorization, which ensures all actions respect users' existing access controls and permissions.

Step 1. Connect your client

Connect your MCP client to:

1
2
https://mcp.atlassian.com/v2/mcp

If you're connecting through an MCP gateway that requires a complete, paginated tool list rather than dynamic discovery, use:

1
2
https://mcp.atlassian.com/v2/mcp?tools=all

Set up with your AI coding agent

Many AI coding agents can install, authenticate, and configure Rovo MCP for you. Paste a prompt like the following into your agent, asking it to use the official setup guide and the MCP server URL https://mcp.atlassian.com/v2/mcp, then start the Atlassian MCP authentication flow so you can sign in.

Set up manually in common clients

Alternatively, select your client and add the Atlassian Rovo MCP Server:

VS Code and GitHub Copilot: Open the Extensions view, enter @mcp Atlassian in the search field, select the Atlassian MCP server from the gallery, and select Install.
Cursor: Go to the Atlassian plugin for Cursor with MCP on the Cursor Marketplace and select Add to Cursor.
Claude Code: Run /mcp once you've opened a Claude Code session to authenticate.
Claude Desktop: Go to Settings > Extensions, select Browse extensions, then Plugins, search for Atlassian, and install it.
Codex Desktop: Go to Plugins or Connectors, find Atlassian Rovo, and install the app.
Windsurf: Add the Atlassian Rovo MCP Server URL to your MCP server configuration.

Step 2. Authenticate

After setup, sign in when your agent or MCP client starts the Atlassian authentication flow. OAuth 2.1 is the recommended method and ensures all actions respect your existing access controls and permissions. If your organization admin has enabled it, authentication via API token is available as an alternative for non-interactive scenarios.

Your AI then selects and runs the right actions for you - no tab switching and no copy-pasting.

Rovo credit usage

Some tools consume Rovo credits. Consumption depends on the volume of context retrieved, the reasoning depth of the query, and per-call usage caps. For example, Teamwork Graph and Rovo Search tools consume up to 10 credits per call.

Network allowlist

Some tools, such as those for whiteboards and attachments, need your agent to reach additional Atlassian domains. If your agent runs in a sandboxed or network-restricted environment, allowlist these domains for those tools to work:

api.media.atlassian.com
*.frontend.public.atl-paas.net

If you're using Claude Code, add these domains to the network.allowedDomains setting. See the Claude Code sandbox settings for details.

Security guidance

MCP clients can perform actions across your Atlassian apps with your existing permissions. Use least privilege, review high-impact changes before confirming, and monitor audit logs for unusual activity.