atlassian.com
Atlassian builds cloud and self-managed software for project tracking, documentation, source control, service management, and AI-assisted teamwork. Its products include Jira, Confluence, Bitbucket, Jira Service Management, Rovo, and the Teamwork Graph platform.
Atlassian exposes Jira, Confluence, and Jira Service Management Cloud REST APIs; a cross-product Atlassian GraphQL Gateway; the OAuth-protected Rovo MCP server; and the `twg` Teamwork Graph CLI.
- Atlassian Rovo MCP serverdetected
- Confluence Cloud REST API v2discovered
- Jira Service Management Cloud REST APIdiscovered
- Jira Cloud REST APIdiscovered
- Atlassian GraphQL Gatewaydiscovered
- Teamwork Graph CLIdiscovered
Create an API token in Atlassian account security. Use it together with your Atlassian account email in HTTP Basic auth for direct calls to Jira, Confluence, Jira Service Management, and tenanted GraphQL endpoints such as https://<site>.atlassian.net/gateway/api/graphql. Atlassian documents this as suitable for scripts and manual calls.
In the Atlassian developer console, create an app, open Authorization, configure OAuth 2.0 (3LO), add your callback URL and product scopes, then use the app's client_id and client_secret from Settings. Users authorize the app in the browser, and you send the resulting bearer access token to Atlassian APIs via Authorization: Bearer.
$ twg loginAcquired by the CLI — running twg login opens the auth flow and stores the credential.
For TWG CLI admin commands, run twg admin auth login --email <your-email> --org <your-org-id>. The docs state site/org admin auth uses an Atlassian Admin API key limited to your organization and stores it separately from normal user auth.
$ twg setup bitbucketAcquired by the CLI — running twg setup bitbucket opens the auth flow and stores the credential.
Use an MCP client that supports OAuth. Atlassian's MCP server publishes OAuth metadata with a registration_endpoint, so the client can register itself automatically and start the browser consent flow. The user just signs in to Atlassian and approves access; no pre-created developer app is required for normal MCP onboarding.
conventions · 1/8 published
- integrations.json✗
/.well-known/integrations.json - llms.txt✓https://atlassian.com/llms.txt
- API catalog✗
/.well-known/api-catalog - OpenAPI document✗
/api/schema/, /openapi.json, /swagger.json, /api/openapi.json, or /v1/openapi.json - MCP server card✗
/.well-known/mcp/server-card.json - OAuth protected resource✗
/.well-known/oauth-protected-resource - Agent card✗
/.well-known/agent-card.json - Agent skills✗
/.well-known/agent-skills/index.json
Publish these signals → /publishing