A server that reaches Jira, Confluence and Bitbucket at once could be alarming; what makes it ordinary is that it sees what you see. No new grant, no shared account, nothing widened. The practical value is the cross-product pass — asking a question that spans a ticket, the page that documents it and the branch that closed it, without three searches. Atlassian gates the tools behind the OAuth flow, so we could not enumerate them.
Atlassian's own remote server. One connection reaches four products, and it follows the access controls your account already has rather than adding a service identity.
- Search and summarise across Jira, JSM, Confluence and Bitbucket
- Create and update work items and pages in natural language
- Automate the repetitive passes — turning meeting notes into issues, for instance
OAuth 2.1 on first connect, with an API token as an alternative. Atlassian publishes per-client and per-IDE setup guides plus a troubleshooting page for when the connection will not verify.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen