Bitbucket

Bitbucket Cloud

This connector works with Bitbucket Cloud through the REST API 2.0 (https://api.bitbucket.org/2.0): workspaces, repositories, branches, commits and files, pull requests with diffs, comments, approvals and merges, Bitbucket Pipelines runs, steps and logs, and deployment environments. It acts as the user (or access token) behind the token: the AI sees and changes exactly what that token can.

Setup (about 3 minutes)

1. Open https://id.atlassian.com/manage-profile/security/api-tokens and click Create API token with scopes. Name it (for example AnythingMCP), pick an expiry and choose the app Bitbucket.
2. Tick the scopes: read:user:bitbucket, read:workspace:bitbucket, read:repository:bitbucket, read:pullrequest:bitbucket and read:pipeline:bitbucket. To create pull requests, comment, approve and merge add write:pullrequest:bitbucket; to start pipelines add write:pipeline:bitbucket.
3. Copy the token (it starts with ATATT) and paste it into BITBUCKET_API_TOKEN. It is sent as Authorization: Bearer <token>, so your Atlassian email is not needed.
4. Check the setup with bitbucket_get_current_user, then bitbucket_list_workspaces.

App passwords no longer work. Bitbucket stopped creating app passwords on 9 September 2025 and switched off the remaining ones on 28 July 2026. Use an API token with scopes as above. A repository, project or workspace access token (Repository settings > Access tokens; project and workspace tokens need a Premium plan) also works in the same field: it acts as a bot limited to that repository, project or workspace, so bitbucket_get_current_user and bitbucket_list_workspaces may be refused and tools outside its scope answer 403 or 404.

How to work

1. bitbucket_list_workspaces gives the workspace slug, bitbucket_list_repositories the repo slug (both are in the URL bitbucket.org/<workspace>/<repo>).
2. Code: bitbucket_get_repository (main branch), bitbucket_list_branches, bitbucket_list_commits, bitbucket_get_commit, bitbucket_get_file (a file's text or a folder listing).
3. Reviews: bitbucket_list_pull_requests, bitbucket_get_pull_request, bitbucket_get_pull_request_diffstat, bitbucket_get_pull_request_diff, bitbucket_list_pull_request_commits, bitbucket_list_pull_request_comments.
4. Pipelines: bitbucket_list_pipelines then bitbucket_get_pipeline, bitbucket_list_pipeline_steps and bitbucket_get_pipeline_step_log for the failing step. Pipeline and step uuids include curly braces; pass them as returned.
5. Deployments: bitbucket_list_environments and bitbucket_list_deployments.

Writes always need the user's confirmation: bitbucket_create_pull_request, bitbucket_add_pull_request_comment, bitbucket_approve_pull_request, bitbucket_merge_pull_request (changes the destination branch for everyone and can start deployments) and bitbucket_run_pipeline (uses build minutes and runs deploy steps). Describe what will happen first and call only after the user agrees. Nothing here deletes branches, repositories or comments, except that a merge with close_source_branch removes the source branch.

Pagination: list answers carry next when there is another page. Call again with page set to the page value in that link (a number for most lists, an opaque token for commit lists). pagelen sets the page size.

Filtering: q takes Bitbucket's query language, for example name ~ "api", state = "OPEN" or destination.branch.name = "main"; sort takes a field, with a minus for descending.

Issues and wikis: Bitbucket removed its built-in issue tracker and wiki on 20 August 2026 (the API answers 410). Use a Jira connector for issues.

Errors: 401 means the token is wrong, expired or revoked (or an old app password). 403 means a scope is missing (the message names it) or the user lacks permission. 404 means the workspace, repository or item does not exist or the token cannot see it. 429 means the hourly rate limit is reached; wait and retry.

Out of scope here: creating or deleting repositories and branches, editing files or pushing commits, declining pull requests, stopping pipelines, repository variables and settings, and administration.