Skip to main content

Set up the Atlassian Rovo MCP server

Atlassian's Rovo MCP server lets AI agents work across Jira, Confluence, and Compass — searching and reading content, creating and updating issues and pages, and running searches that span products. This guide covers adding MintMCP to your Atlassian organization's domain allowlist and approving the server in MintMCP, so your team can connect with their own Atlassian accounts.

Prerequisites​

Add MintMCP to your Atlassian allowlist​

Atlassian's Rovo MCP server uses a domain allowlist to control which AI tools can connect to your organization over OAuth. MintMCP isn't one of Atlassian's default-allowed domains, so add it yourself before approving the connector.

  1. Go to admin.atlassian.com and select your organization.
  2. Go to Atlassian Administration > Rovo > Rovo MCP server. (On older consoles this lives under Apps > AI settings > Rovo MCP server.)
  3. Under Allowed domains, click Add domain.
  4. Enter https://app.mintmcp.com/** and save.

You don't create a custom OAuth app or paste any credentials. MintMCP connects over OAuth 2.1, and allowlisting its domain is what authorizes it to request access on each user's behalf.

Tool capabilities reference​

Over this OAuth connection, the Rovo MCP server exposes read and write tools across three products:

ProductWhat you can do
JiraSearch issues with JQL, read issue details, create and update issues, add comments and worklogs, transition issues
ConfluenceSearch pages with CQL, read pages and comments, create and update pages and comments
CompassRead components, create components and relationships
Cross-product searchSearch and fetch content across products through Teamwork Graph

Note: Cross-product search runs on Teamwork Graph, which is in beta and currently free to use.

Jira Service Management and Bitbucket Cloud tools authenticate with API tokens instead of OAuth, so they aren't reachable through this connection.

These tools don't grant access on their own. Every call runs as the signed-in user and respects their existing Jira, Confluence, and Compass permissions, so a user can only act on what they could already see in Atlassian.

Add Atlassian Rovo to MintMCP​

Atlassian Rovo is pre-listed as a recommended server in the MintMCP MCP store.

  1. In MintMCP, go to MCP store > Manage store.
  2. Find Atlassian Rovo in the recommended servers list.
  3. Click Install.

Each team member signs in with their own Atlassian account on first use, so all tool calls are tied to their individual permissions.

Security considerations​

  • Each user authenticates individually, so Jira issues, Confluence pages, and Compass components are only accessible based on that user's existing Atlassian permissions.
  • Removing MintMCP from the allowed domains list immediately revokes OAuth access for all users.
  • A tool call only succeeds when it comes from an allowlisted domain and an allowed IP. If your organization runs an IP allowlist in Atlassian, add MintMCP's egress IPs or calls will be blocked even with the domain allowlisted.

Troubleshooting​

  • Connection rejected during sign-in — the MintMCP domain isn't allowlisted. Confirm https://app.mintmcp.com/** is saved under Allowed domains, including the trailing /**.
  • Sign-in succeeds but calls fail — your organization's IP allowlist is blocking MintMCP's egress IPs. Add them in Atlassian's IP allowlist settings.
  • A product's tools return nothing — the signed-in user lacks access to that Jira project, Confluence space, or Compass component. Tools never widen a user's existing permissions.
  • Cross-product search tools are missing — these Teamwork Graph tools are in beta and may not be enabled for your organization yet.

Next steps​