The Atlassian Rovo MCP server securely brings Atlassian context into external AI tools. It is an integration layer, not an AI model, exposing Rovo search and fetch tools. It does not store or cache Jira or Confluence content per Atlassian's page.
What it does
Where Atlassian Rovo MCP Server runs and what it adds, from its documentation
Search and fetch Jira and Confluence content
Create Jira work items and Confluence pages, including in bulk
Connect from Cursor, VS Code, ChatGPT and Claude
OAuth authentication with admin domain controls
A2A gateway for external agents
When to use it
Good fit
Pulling Jira and Confluence context into an AI client
Teams on Atlassian Cloud
Not for
FedRAMP or HIPAA needs: not currently supported
Beyond site rate limits (Free 500 calls/hour)
How to install Atlassian Rovo MCP Server
You need: Atlassian Cloud site; AI client supporting remote MCP
Choose your AI client on atlassian.com/platform/remote-mcp-server
Use the add-to-client option (Cursor, VS Code, ChatGPT, Claude)
Authorize with OAuth
Admins can control allowed domains
Permissions and security
What it can access
Acts within the signed-in user's Atlassian permissions
Security notes from the maintainers
Admins can add or block AI domains
Does not store or cache Jira or Confluence content
Review the source before granting an agent access to credentials or production systems. We document what the maintainers state; we do not audit code.
Limitations
Rate limits: Free 500, Standard 1000, Premium/Enterprise 1000 plus per-user calls/hour
Not stated by the maintainers: No GitHub repo; repo_url is the Atlassian page; Endpoint URL and tool names not captured; License not applicable; last_release date not visible in the checked README.