Connections are added inside an Access bundle. At
claude.ai/admin-settings/claude-tag, open Access bundles in the left navigation, click into a bundle (or Create one), and go to its Credentials tab.Create the credential in Atlassian
Create a dedicated Atlassian account for Claude (for exampleclaude@yourcompany.example.com) and add it to the Jira projects and Confluence spaces it should reach. The connection can read whatever this account can read, so a dedicated account keeps Claude’s reach to exactly what you grant it.
Sign in as that account and create an API token at id.atlassian.com/manage-profile/security/api-tokens. Atlassian shows the token once; store it somewhere you can retrieve it.
Add the connection to a bundle
On the bundle’s Credentials tab, click Connect another tool.
Atlassian Cloud’s REST APIs authenticate with HTTP Basic, where the username is the account email and the password is the API token. An API token sent as a Bearer header is not accepted on Atlassian Cloud; pick Basic, not Bearer.
The Agent Proxy injects the credential at the network boundary; the model and the sandbox are not given the key. See how Agent Proxy works.
Atlassian Data Center (self-hosted) uses a personal access token sent as a Bearer header instead of Basic auth. For a Data Center instance, pick Bearer as the credential type and add your instance’s hostname under Allowed websites. The instance must be reachable from the public internet.
Verify the connection
In a channel under the bundle’s scope, in a new thread, ask Claude to fetch one issue or page by key or URL. The call lands under the dedicated account in Atlassian’s audit log.Related resources
- Custom connection: the form fields and credential types in full
- Give Claude access: the full connection model and how to scope a dedicated account