Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.truefoundry.com/llms.txt

Use this file to discover all available pages before exploring further.

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: 
https://<tfy-control-plane-base-url>/**
Atlassian handles dynamic client registration for allowlisted domains, so you do not need to create a separate OAuth client.

​
Register in TrueFoundry

In MCP Gateway, add a remote MCP server for the Atlassian Rovo endpoint documented in your Atlassian admin page. Choose OAuth2 with per-user authorization, add collaborators, and save. Users should open the server’s Tools section and click Connect Now; after OAuth 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.