Atlassian Rovo MCP Server

What it does (plain English)

The Atlassian Rovo MCP server is Atlassian’s official bridge between Claude and your Atlassian Cloud site. Once connected, Claude can search, read and write in Jira, Confluence, Jira Service Management, Bitbucket Cloud, Compass and Loom, plus Atlassian’s Goals, Projects and Teams data. An MCP server is a plug-in that gives Claude a new ability; this one is hosted by Atlassian.

Everything respects the access you already have. If you can’t see a Jira project in the browser, Claude can’t see it through MCP either.

Tools are grouped by product and intent, and admins switch groups on or off:

Product	Permission groups
Jira	read_jira, write_jira, search_jira (plus admin-only delete_jira, manage_jira)
Confluence	read_confluence, write_confluence, search_confluence
Bitbucket Cloud	read_bitbucket, write_bitbucket
Jira Service Management	read_jsm, write_jsm (API token only)
Loom	read_loom, write_loom
Compass	read_compass, write_compass (OAuth only)

To save Claude’s context, the server shows only the most-used tools up front and lets Claude discover the rest on demand.

Is it for you?

Pick it if your team runs on Jira and Confluence and you want Claude to file work, update tickets or summarise long pages.

Atlassian’s prerequisites call for an Atlassian Cloud site. If your company runs Jira or Confluence on its own servers, check with your admin before you plan around this.

What you can do with it

These come from Atlassian’s own example workflows:

• Search Jira: “Find all open bugs in Project Alpha.”
• Bulk create: “Make five Jira issues from these notes.”
• Summarise Confluence: “Summarize the Q2 planning page.”
• Move work forward: “Move PROJ-456 to ‘In Review’ and add a comment that the PR is up.”
• Cross-product: “Link these three Jira work items to the ‘Release Plan’ page,” or “Summarize this Loom walkthrough and list the action items.”

How to set it up

1. claude.ai. Open https://claude.ai/directory/connectors/atlassian and add the Atlassian connector. Sign in with your Atlassian account and approve access.

2. Claude Desktop. Atlassian’s setup table says: Settings → Extensions → Browse extensions → Plugins, then search for Atlassian.

3. Claude Code. In your terminal:

   claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp

   Then run /mcp inside a session to authenticate.

4. Pick the right URL. Atlassian says v2 is now recommended: https://mcp.atlassian.com/v2/mcp. The v1 endpoints still work, but the old SSE endpoint https://mcp.atlassian.com/v1/sse is no longer supported after 30 June 2026.

5. Save tool calls (optional). Atlassian suggests putting your defaults in an AGENTS.md file so Claude doesn’t have to look them up every time. Its template looks like this (replace the values with yours):

   ## Atlassian MCP
   
   When connected to atlassian-rovo-mcp:
   - **MUST** use Jira project key = YOURPROJ
   - **MUST** use Confluence spaceId = "123456"
   - **MUST** use cloudId = "https://yoursite.atlassian.net"
   - **MUST** use `maxResults: 10` or `limit: 10` for ALL Jira JQL and Confluence CQL search operations.

6. Need every tool listed up front? If you route through an MCP gateway, Atlassian offers https://mcp.atlassian.com/v2/mcp?tools=all, which exposes all tools as a flat list instead of on-demand discovery.

Watch out for

• Delete and admin tools are off by default. delete_jira and manage_jira must be enabled by an admin before they can be used.
• API tokens need admin approval. An org admin has to enable API-token auth (Atlassian Administration → Rovo → Rovo MCP server → Authentication). Jira Service Management tools only work this way.
• Bitbucket and Loom conditions. Bitbucket tools need a workspace linked to an organization; Loom tools need a Loom workspace linked to an Atlassian site.
• 403 after a successful login. Atlassian notes a sign-in can succeed while tool calls are blocked by IP allowlisting, missing scopes or another access policy.
• Third-party data. Teamwork Graph tools can return data from connected tools such as GitHub. Under GitHub’s “full access” mode that follows your GitHub permissions.

Alternatives

• Linear MCP if your team uses Linear instead of Jira.
• Notion MCP if your docs live in Notion.
• GitHub MCP for code and pull requests hosted on GitHub rather than Bitbucket.