Get started with the Atlassian Rovo MCP Server
Atlassian recently released v2 of Atlassian Rovo MCP, introducing more tools and products which you can now interact with from your agents. Need help upgrading from v1? How to upgrade from Atlassian Rovo MCP v1 to Atlassian Rovo MCP v2
On March 1, 2027 any existing utilization of v1 will automatically start to expose and utilize v2 tools. Any incompatible clients will need to clear cached clientIds or .well-known credentials to support continued authentication.
In browser and desktop agents, Atlassian Rovo MCP connects your AI agent to your Atlassian apps and work, all accessible in one conversation – powered by your Teamwork Graph.
Supported clients and IDEs
The Atlassian Rovo MCP Server supports any app with MCP support, including:
How it works
With Rovo MCP, you can:
Summarize and search Jira, Jira Service Management, Confluence, Bitbucket, Projects, Goals, and more without switching tools.
Retrieve and review recordings of videos and meetings from Loom
Create and update work items or pages using natural language commands.
Automate repetitive tasks, such as generating work from meeting notes or specs.
Connect once, then describe what you want:
"What's the status of PROJ-1234?"
"Summarize the Q2 planning page."
"Create five Jira work items from these meeting notes."
“Move PROJ-456 to 'In Review' and add a comment that the PR is up.”
No tab switching. No copy-pasting. Your AI selects and runs the right actions.
How Rovo credit usage works with MCP
When an AI client calls via MCP to retrieve data or generate insights, it consumes Rovo credits. These credits come from the same shared pool used by Rovo Chat, Studio, Agents, and the Teamwork Graph, across your organization.
Credit usage is based on the complexity of the request:
Context volume: Larger amounts of data pulled from your site require more credits.
Reasoning depth: Complex queries that require more processing power consume more credits than lightweight lookups.
Usage cap: To help you manage costs, credit usage is per call.
For thresholds, plan-level allowances, and what happens when you approach your usage limit, see Rovo usage limits.
Get started
For full setup instructions, see the clients and IDEs guides.
Step 1: Connect your client
Most AI coding agents can install, authenticate, and set up Rovo MCP from a prompt. Copy and paste this prompt into your agent:
Set up Atlassian Rovo MCP for this agent using the official setup guide at https://support.atlassian.com/atlassian-rovo-mcp-server/docs/getting-started-with-the-atlassian-remote-mcp-server/ and the MCP server URL https://mcp.atlassian.com/v2/mcp. Then start the Atlassian MCP authentication flow so I can sign in.Alternatively, select your client and add the Atlassian Rovo MCP Server.
VS Code / GitHub Copilot
Quick install: Add to VS Code
Or add manually:
Open the Extensions view and enter
@mcp Atlassianin the search field.Select the Atlassian MCP server from the gallery.
Select Install.
Cursor
Quick install: Add to Cursor
Or add manually:
Go to Atlassian plugin for Cursor with MCP on the Cursor Marketplace.
Select Add to Cursor.
Claude Code
Run the following command in your terminal:
claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcpRun
/mcponce you’ve opened a Claude Code session to authenticate.
Claude Desktop
Open Claude Desktop.
Go to Settings > Extensions.
Select Browse extensions, then select Plugins.
Search for Atlassian and install it.
Or, add it to your config file:
{
"mcpServers": {
"atlassian": {
"url": "https://mcp.atlassian.com/v2/mcp"
}
}
}Codex Desktop
Open Codex Desktop.
Go to Plugins or Connectors.
Find Atlassian Rovo.
Install the app.
Codex
Run the following command in your terminal:
codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcpWindsurf
Open your Windsurf settings
Go to Cascade > MCP servers
Select Add Server > Add custom server
Add the following:
{
"mcpServers": {
"atlassian": {
"serverUrl": "https://mcp.atlassian.com/v2/mcp/"
}
}
}Other MCP-compatible clients
Use this server URL:
https://mcp.atlassian.com/v2/mcpMCP Gateways
If you’re utilising an MCP gateway, you may want to expose all tools available in Atlassian Rovo MCP, rather than utilising the discovery and execute methods. In these circumstances, use the following override to expose all tools in a paginated flat tool list.
https://mcp.atlassian.com/v2/mcp?tools=allStep 2: Authenticate
After setup, sign in when your agent or MCP client starts the Atlassian authentication flow.
Atlassian Rovo MCP is powered by secure OAuth 2.1 authorization, which ensures all actions respect users' existing access controls and permissions.
Authentication via API token is also available as optional.
Disclaimer
MCP clients can perform actions on all connected products (such as Jira, Confluence, Bitbucket) with your existing permissions. Use least privilege, review high‑impact changes before confirming, and monitor audit logs for unusual activity. Understanding the security risks of MCP clients
Enriched Teamwork Graph (TWG) API and tool calls, including unified search and context tools called via Rovo MCP, consume Rovo credits. These include but are not limited to: getTeamworkGraphContext,twg rovo search, searchAtlassian, search.
Find out how Rovo credits work for enriched TWG API and tool calls.
Was this helpful?