- Per-user OAuth (recommended). Each person authorizes with their own Bitbucket account, so every tool call runs under that user’s identity and permissions.
- API token with your Atlassian email (Basic auth). A single API token and the Atlassian account email that owns it authenticate everyone as one shared identity.
- Bearer token. A single API token, or a repository, project, or workspace access token, authenticates everyone as one shared identity.
How C1 connects to Bitbucket
C1 hosts the Bitbucket MCP server, so your users’ AI clients only ever see MCP tools — they never call Bitbucket directly. When an AI client calls one of these tools, C1 makes the matching request to the Bitbucket API using the credentials you configure here, then returns the result to the AI client. The credentials you set up below are what C1 uses to call Bitbucket on your users’ behalf.Before you begin
- AI access management must be enabled for your tenant. See Enable AI access management.
- For per-user OAuth, permission to create an OAuth consumer in your Bitbucket workspace settings.
- For an API token with your Atlassian email, the Atlassian account email address and an account whose access the token should carry.
- For a Bearer token, a Bitbucket API token or a repository, project, or workspace access token.
If you don’t see Bitbucket in your MCP server catalog, contact the C1 support team to enable it for your tenant.
Option 1: Set up per-user OAuth
With per-user OAuth, you register one Bitbucket OAuth consumer and each user authorizes individually. This keeps every action attributable to the user who took it, with only the access that user already has in Bitbucket.Create a Bitbucket OAuth consumer
Create an OAuth consumer in your Bitbucket workspace so C1 can prompt each user to authorize their own account.1
In Bitbucket, go to your Workspace settings > OAuth consumers and select Add consumer. For the full procedure, see Bitbucket’s Use OAuth on Bitbucket Cloud documentation.
2
Fill in the registration form:
- Name — a recognizable name such as
C1. - Callback URL — set this exactly to whichever matches your C1 tenant’s domain:
- Default instance:
https://accounts.conductor.one/auth/callback - EU data residency instance:
https://accounts.c1eu.ai/auth/callback
- Default instance:
3
Under Permissions, check the boxes below. C1 requests these read scopes automatically, so grant each one on the consumer:
- Account: Read
- Projects: Read
- Repositories: Read
- Pull requests: Read
- Pipelines: Read
4
Save the consumer, then open it to copy the Key (client ID) and Secret (client secret).
Register the server with OAuth
With your OAuth consumer ready, register the server and provide its credentials.1
Follow Register an MCP server and select Bitbucket from the catalog.
2
When you configure authentication, choose per-user OAuth and enter your consumer’s client ID (key) and client secret.
3
Save your changes. The first time a user calls a Bitbucket tool from their AI client, they’re prompted to connect their Bitbucket account.
Option 2: Use an API token with your Atlassian email
An API token authenticates every user as one shared Bitbucket identity. Bitbucket accepts it with the email address of your Atlassian account as the username. This is not your Bitbucket username. Use this when per-user attribution in Bitbucket isn’t required.Create an API token
Create an API token in your Atlassian account so C1 can authenticate to the Bitbucket API.1
Open Atlassian API tokens and select Create API token with scopes. For details, see Bitbucket’s Create an API token documentation.
2
Enter a name such as
C1 and an expiry date, then select Next.3
Select Bitbucket as the app, then select Next.
4
Select these scopes, then select Next:
read:user:bitbucketread:workspace:bitbucketread:pipeline:bitbucketread:project:bitbucketread:pullrequest:bitbucketread:repository:bitbucket
write:, admin:, or delete: scopes, such as write:pullrequest:bitbucket. A write scope doesn’t include the matching read scope, so keep the read scopes selected. For the full list, see Bitbucket’s API token permissions.5
Review the token, select Create token, then copy it. Bitbucket shows it only once.
Register the server with an API token and email
With your API token ready, register the server and provide its credentials.1
Follow Register an MCP server and select Bitbucket from the catalog.
2
When you configure authentication, choose Basic auth. Enter your Atlassian account email as the username and paste the API token as the password.
3
Save your changes. C1 runs tool discovery against Bitbucket.
Option 3: Use a Bearer token
A Bearer token authenticates every user as one shared identity. It can be a Bitbucket API token, or a repository, project, or workspace access token. With an API token, you don’t provide the Atlassian email.Get a token
Get a token that Bitbucket accepts as a Bearer token.1
To use an API token, follow the steps in Create an API token with the same scopes, then copy the token.
2
To use an access token instead, create a repository, project, or workspace access token in Bitbucket and select the permissions you need. For details, see Bitbucket’s Access tokens documentation.
Register the server with a Bearer token
With your token ready, register the server and provide its credentials.1
Follow Register an MCP server and select Bitbucket from the catalog.
2
When you configure authentication, choose Bearer token and paste your token.
3
Save your changes. C1 runs tool discovery against Bitbucket.
How Bitbucket credentials are shared
How Bitbucket sees your users’ activity depends on the method you chose:- Per-user OAuth. Each user authorizes with their own Bitbucket account, so tool calls run under that user’s Bitbucket identity and inherit only the access they already have. Bitbucket attributes each action to the individual user.
- API token with email, or Bearer token. Every user’s tool calls use the one credential you provided, so Bitbucket sees a single shared identity. C1 still attributes each call to the individual user in the AI tool usage audit log.
Discover and govern tools
After you register the server, C1 runs tool discovery against Bitbucket. Discovered tools appear on the server’s Tools tab. Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCPs > Settings. See Require tool approval and Default tool classification. Before anyone can call a Bitbucket tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.Tool discovery runs even if your credentials are incorrect, so seeing discovered tools doesn’t confirm that authentication is working. You confirm your Bitbucket credentials when an approved user successfully calls a Bitbucket tool from their AI client.
Manage your Bitbucket credentials
- Rotate the OAuth client secret by regenerating the secret on your Bitbucket OAuth consumer under Workspace settings > OAuth consumers, then update it on the server’s authentication settings in C1.
- Rotate an API token or access token by creating a new token in Bitbucket and updating it in C1, then revoking the old one. Create the new token before the current one expires.
- Adjust access by editing the consumer’s permissions in Bitbucket, or by creating a replacement token with different scopes or permissions.