The TrueFoundry MCP Server for Atlassian enables secure, scalable integration between LLMs and Atlassian products (Jira, Confluence, etc.) using OAuth2.0.

​
Prerequisites

  1. Deploy your MCP Server and note the endpoint URL.
  2. Create an Atlassian App in the Atlassian Developer Console.

​
Step 1: Deploy the Atlassian MCP Server

  • MCP Server code: Atlassian MCP Server Repository
  • Refer atlassian-mcp/truefoundry.yaml for the deployment configuration on TrueFoundry.
  • Deploy the MCP server as a service on your preferred infrastructure.
  • Note the deployment Endpoint URL—you’ll need it for the AI Gateway.

Deploying the Atlassian MCP Server

​
Step 2: Create an Atlassian App

  • Go to Atlassian Developer Console
  • Click Create app > OAuth 2.0 integrations
  • Fill out the form:
    • App name: e.g., demo-test-atlassian
    • Agree to Atlassian’s developer terms
    • Click Create
  • After creation, you’ll be redirected to your app’s overview page.

Creating an Atlassian App

​
Step 3: Update Distribution Status to ‘Sharing’

  • In your app’s settings, find the Distribution status section.
  • Change the status from Not sharing to Sharing.
  • Fill in the required vendor and security details:
    • Vendor name (your company or your name)
    • Privacy policy URL
    • Terms of service URL
    • Customer support contact (email or URL)
    • Personal Data Declaration (select Yes/No as appropriate)
  • Save your changes.
Setting the app to ‘Sharing’ allows others to install and use your app. If you stop sharing, it may affect existing users. See Atlassian documentation for more details.

Updating Distribution Status to 'Sharing'

​
Step 4: Configure Redirect URL, OAuth2 Settings & Scopes

  • Go to your app’s Settings page in the Atlassian Developer Console.
  • Note the following:
    • Client ID
    • Client Secret
    • Authorization URL: https://auth.atlassian.com/authorize
    • Token URL: https://auth.atlassian.com/oauth/token

Client ID and Client Secret

​
Add Callback URL

  • In the left sidebar, go to Authorization.
  • Under OAuth 2.0 authorization code grants (3LO) for apps, configure the callback URL:
https://<your-control-plane-base-url>/api/svc/v1/llm-gateway/mcp-servers/oauth2/callback
Replace <your-control-plane-base-url> with your platform’s control plane URL.
  • Click Save changes after entering the callback URL.
You must add the callback URL exactly as shown, or the OAuth2 flow will not work. This is required for Atlassian to redirect users back to your app after authentication.

​
Add Required Scopes

  • Go to Permissions > Add and configure your app’s API scopes.
  • Add the required scopes for your use case. Atlassian recommends using classic scopes where possible. For example:

Recommended Scopes

ScopeDescription
org:readRead organization details
read:jira-userView user profiles
write:issue:jiraCreate and update issues
offline_accessRefresh tokens
read:confluence-space.summaryRead Confluence space summary
read:confluence-propsRead Confluence properties
read:confluence-content.allRead all Confluence content
read:confluence-content.summaryRead Confluence content summary
read:confluence-content.permissionRead Confluence content permissions
read:confluence-userRead Confluence users
read:confluence-groupsRead Confluence groups
read:jira-workView Jira issue data
manage:jira-projectManage project settings
manage:jira-configurationManage Jira global settings
write:jira-workCreate/manage Jira issues
manage:jira-webhookManage Jira webhooks
manage:jira-data-providerManage Jira data provider
read:servicedesk-requestRead Jira Service Management requests
report:personal-dataReport user accounts storing personal data
Only request the minimum scopes needed for your use case. Jira permissions also control access to data and aren’t overridden by scopes. For example, if a user does not have the Browse projects permission, the app cannot access project data even with the correct scope.

​
Step 5: Register MCP Server on AI Gateway

  • Go to the MCP Server tab in your AI Gateway
  • Click Add New MCP Server Group (if needed)
  • Add a new MCP Server:
    • Endpoint URL: Your deployed MCP Server URL
    • Authentication Type: OAuth2
    • Client ID: Your Atlassian app’s Client ID
    • Client Secret: Your Atlassian app’s Client Secret
    • Scopes: The permissions you set above

Adding Atlassian MCP Server to AI Gateway

For security, store OAuth2 credentials as secrets using FQN references instead of plain text values.

​
Step 6: Test Your MCP Server

  1. Go to the MCP Server tab in your AI Gateway.
  2. Find and select your Atlassian MCP Server.
  3. Click Connect Now to start authorization.
  4. Authorize with your Atlassian credentials in the popup.
  5. Once connected, your MCP Server will show up in the list.
  6. Select the tools you want and click Select Tools.
  7. You can now use the Atlassian MCP Server and its tools in the AI Gateway Playground to interact with Atlassian via LLMs.
You can revoke your OAuth2 authorization at any time through the AI Gateway.