Skip to main content
tai42-connector-atlassian registers the atlassian connector: one Atlassian OAuth 2.0 (3LO) connection per alias, unlocking three services — Jira, Confluence, and Compass. Unlike the Google connector, every service here is a remote HTTP MCP endpoint hosted by Atlassian, so nothing is launched locally.

​
Install and register it

manifest.yml

​
Create the Atlassian app

Create an OAuth 2.0 (3LO) app in the Atlassian developer console, enable the products you intend to offer (Jira, Confluence, Compass), and grant the app the granular scopes listed below. Add this exact callback URL, where {origin} is your deployment’s public origin (or CONNECTORS_OAUTH_BRIDGE_URL when you run a shared bridge):
Then set the client credentials on the API process:
The engine-wide CONNECTORS_* settings — the key-encryption key, the state HMAC key, and the redirect-URI allowlist — are the same for every connector and are described in the Google connector page.

​
Services and scopes

Atlassian refuses an app that mixes classic and granular scopes, so every scope below is granular. The authorize request adds audience=api.atlassian.com and prompt=consent. offline_access is what makes the refresh token available, so a connection survives the access token’s expiry.
Atlassian publishes no 3LO revocation endpoint, so disconnecting removes the stored token from this deployment but cannot revoke it at Atlassian. Revoke the app’s access from the Atlassian account’s connected-apps screen when that matters.

​
Connect an account

The connect flow runs from the Studio or the CLI exactly as the OAuth provider guide describes. Each service resolves to Atlassian’s hosted MCP endpoint, authorised with the connection’s own token.

​
See also