Skip to main content
Atlassian’s Rovo MCP server gives agents access to Jira, Confluence, and Compass for searching issues, reading pages, creating tickets, and working across Atlassian products. Atlassian uses an allowlist model, so an organization admin must allow your TrueFoundry domain before users connect.

​
Prerequisites

  • A TrueFoundry account with permission to add MCP servers.
  • An Atlassian Cloud organization with Jira, Confluence, or Compass.
  • Organization admin access in admin.atlassian.com.

​
Allow TrueFoundry in Atlassian

In Atlassian Admin, select your organization and open Apps > AI settings > Rovo MCP server. Under Allowed domains, add your TrueFoundry control plane domain, for example:
Atlassian handles dynamic client registration for allowlisted domains, so you do not need to create a separate OAuth client.

​
Register in TrueFoundry

1

Add the Atlassian MCP server

In TrueFoundry, open MCP Gateway, click Add MCP Server, and select Atlassian.
2

Configure the server

Use the following values:Turn on Auth Data and select the OAuth2 tab. Because your TrueFoundry domain is allowlisted in Atlassian, you do not need to enter a separate OAuth client ID or secret.
3

Add collaborators

Add the users or teams that should use Atlassian tools. Assign MCP Server Manager to administrators and MCP Server User to consumers.
4

Save and authorize

Click Add MCP Server. Each user should open the server’s Tools section and click Connect Now to complete Atlassian OAuth. After authorization succeeds, Atlassian tools appear and can be tried from the Agent Playground.

​
Security Notes

Each user operates with their existing Jira, Confluence, and Compass permissions. Removing the TrueFoundry domain from Atlassian’s allowlist revokes new OAuth connections. If Atlassian IP allowlisting is enabled, allow traffic from the environment where TrueFoundry connects to the remote MCP server.