Overview
What Atlassian Rovo MCP Server does
Atlassian Rovo MCP is a managed bridge between AI clients and Atlassian Cloud. It can search and fetch work and knowledge, then perform supported create or update actions such as producing Jira work items from notes or editing a Confluence page. Requests run with the signed-in user's permissions and organization controls, while OAuth avoids placing Atlassian credentials directly in the client configuration.
Best for
- Joining Jira work and Confluence knowledge in one conversation
- Turning meeting notes or specifications into trackable work
- Retrieving cross-product Atlassian context from an IDE or chat client
Not ideal for
- Atlassian Data Center or Server deployments
- Organizations requiring FedRAMP or HIPAA support for this connection
- Background automation without an authorized user context
Capabilities
What an agent can do
- 01
Rovo search and fetch across connected work
- 02
Jira and Jira Service Management issue operations
- 03
Confluence page search and editing
- 04
Bitbucket repository context
- 05
Natural-language summaries across Atlassian products
- 06
OAuth 2.1 and organization admin controls
Representative tools and operations
searchAtlassianfetchAtlassiangetJiraIssuecreateJiraIssueeditJiraIssuesearchConfluenceUsingCqlgetConfluencePagecreateConfluencePage
Installation
Connect Atlassian Rovo MCP Server
Use the publisher’s current instructions as the source of truth. The examples below were checked on .
Claude CodeConnect to Atlassian's official endpoint
claude mcp add --transport http atlassian https://mcp.atlassian.com/v1/mcp/authv2Run /mcp after opening Claude Code and complete Atlassian sign-in.CodexAdd the remote server
codex mcp add atlassian --url https://mcp.atlassian.com/v1/mcp/authv2Confirm the hostname and complete the OAuth flow in the trusted browser window.Trust and access
Authentication and security notes
Authentication: OAuth 2.1 browser authorization is the standard route and preserves the user's existing Atlassian permissions. Atlassian also documents an optional API-token authentication path for supported configurations.
Review before connecting
- Connect only to Atlassian's documented mcp.atlassian.com endpoint.
- All actions inherit the signed-in user's product permissions; reduce user access at the source when necessary.
- Organization administrators can manage trusted AI domains and other connection controls.
- Review write operations such as issue creation, transitions, comments, and page edits.
Known limitations
- The official server targets Atlassian Cloud rather than self-managed Data Center products.
- Site-level call limits vary by Jira and Confluence plan.
- FedRAMP and HIPAA support are not currently offered for the service.
- Available products and tools depend on the user's licenses, permissions, and connected Teamwork Graph data.
Evidence
Sources used for this guide
Facts were checked against primary publisher material. Descriptions and guidance are original Graphify summaries.
FAQ
Questions about Atlassian Rovo MCP Server
Does Atlassian Rovo MCP work with Jira Data Center?
The official managed server is documented for Atlassian Cloud. Data Center deployments need a different integration approach.
Does the server bypass Atlassian permissions?
No. Tools operate within the signed-in user's existing product access and any controls applied by the organization.
