Atlassian
The TrueFoundry MCP Server for Atlassian enables secure, scalable integration between LLMs and Atlassian products (Jira, Confluence, etc.) using OAuth2.0.
Prerequisites
- Deploy your MCP Server and note the endpoint URL.
- Create an Atlassian App in the Atlassian Developer Console.
Step 1: Deploy the Atlassian MCP Server
- MCP Server code: Atlassian MCP Server Repository
- 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
- App name: e.g.,
- 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:
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
| Scope | Description |
|---|---|
org:read | Read organization details |
read:jira-user | View user profiles |
write:issue:jira | Create and update issues |
offline_access | Refresh tokens |
read:confluence-space.summary | Read Confluence space summary |
read:confluence-props | Read Confluence properties |
read:confluence-content.all | Read all Confluence content |
read:confluence-content.summary | Read Confluence content summary |
read:confluence-content.permission | Read Confluence content permissions |
read:confluence-user | Read Confluence users |
read:confluence-groups | Read Confluence groups |
read:jira-work | View Jira issue data |
manage:jira-project | Manage project settings |
manage:jira-configuration | Manage Jira global settings |
write:jira-work | Create/manage Jira issues |
manage:jira-webhook | Manage Jira webhooks |
manage:jira-data-provider | Manage Jira data provider |
read:servicedesk-request | Read Jira Service Management requests |
report:personal-data | Report user accounts storing personal data |
- For a full, up-to-date list of available scopes and their descriptions, see the Atlassian OAuth 2.0 Scopes documentation.
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
- Go to the MCP Server tab in your AI Gateway.
- Find and select your Atlassian MCP Server.
- Click Connect Now to start authorization.
- Authorize with your Atlassian credentials in the popup.
- Once connected, your MCP Server will show up in the list.
- Select the tools you want and click Select Tools.
- 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.