Bitbucket MCP integration for AI agents.
Connect AI agents to Bitbucket through 41 structured actions, including get branch, approve pull request, delete branch, and decline pull request. Review aut…
- ACTION CONTRACTS
- 41
- AUTHENTICATION
- OAuth 2.0
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Bitbucket integration exposes
The Bitbucket Agent App exposes 41 provider-backed actions for developer tools work. Its current contract lets an authorized agent get a branch in a bitbucket repository, approve a bitbucket pull request, and delete a branch from a bitbucket repository. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses OAuth 2.0. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Bitbucket account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Bitbucket capabilities.
Showing 12 of 41 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_branchREADGet a branch in a Bitbucket repository.
INPUTS: workspace / repository / branch
approve_pull_requestWRITEApprove a Bitbucket pull request.
INPUTS: workspace / repository / pullRequestId
delete_branchHIGH IMPACTDelete a branch from a Bitbucket repository.
INPUTS: workspace / repository / branch
decline_pull_requestREVIEWDecline a Bitbucket pull request.
INPUTS: workspace / repository / pullRequestId
create_branchWRITECreate a branch from a commit hash or existing revision in a Bitbucket repository.
INPUTS: workspace / repository / name / target
create_issueWRITECreate an issue in a repository that still supports the deprecated Bitbucket issue tracker.
INPUTS: workspace / repository / title / content / kind
create_issue_commentWRITECreate an issue comment in a repository that still supports the deprecated Bitbucket issue tracker.
INPUTS: workspace / repository / issueId / content
create_pipeline_variableWRITECreate a repository-level Bitbucket Pipelines variable.
INPUTS: workspace / repository / key / value / secured
create_pull_requestWRITECreate a pull request in a Bitbucket repository.
INPUTS: workspace / repository / title / sourceBranch / destinationBranch
create_pull_request_commentWRITECreate a comment on a Bitbucket pull request.
INPUTS: workspace / repository / pullRequestId / content
delete_pipeline_variableHIGH IMPACTDelete a repository-level Bitbucket Pipelines variable.
INPUTS: workspace / repository / variableUuid
delete_repositoryHIGH IMPACTPermanently delete a Bitbucket repository.
INPUTS: workspace / repository
INPUT CONTRACTS
Know what the action needs before it runs.
get_branch
workspaceOPTIONAL- The workspace slug or UUID.
repositoryOPTIONAL- The repository slug or UUID.
branchOPTIONAL- The branch name.
approve_pull_request
workspaceOPTIONAL- The workspace slug or UUID.
repositoryOPTIONAL- The repository slug or UUID.
pullRequestIdOPTIONAL- The pull request ID.
delete_branch
workspaceOPTIONAL- The workspace slug or UUID.
repositoryOPTIONAL- The repository slug or UUID.
branchOPTIONAL- The branch name.
decline_pull_request
workspaceOPTIONAL- The workspace slug or UUID.
repositoryOPTIONAL- The repository slug or UUID.
pullRequestIdOPTIONAL- The pull request ID.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Branch
Get a branch in a Bitbucket repository. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_branchControl Approve Pull Request
Approve a Bitbucket pull request. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
approve_pull_requestVerify with Approve Pull Request
Approve a Bitbucket pull request. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
approve_pull_requestSAFETY BOUNDARY
Operate Bitbucket with explicit limits
- Authorize Bitbucket with OAuth 2.0 and grant only the provider access required by the selected actions.
- 14 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_branch`, `delete_pipeline_variable`, and `delete_repository` as high-impact operations and require an explicit approval boundary.
- The sampled contract declares provider scopes including `bitbucket.pull_request.write`, `bitbucket.repository.write`, `bitbucket.issue.interact`, and `bitbucket.pipeline.variable.write`; verify the complete action contract before execution.
- After a call, inspect the structured result and execution record before reporting that the Bitbucket task completed successfully.
CONNECTION MODEL
OAuth 2.0
Bitbucket uses OAuth 2.0. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 25
- WRITE SIGNALS
- 11
- HIGH IMPACT
- 3
- REVIEW SIGNALS
- 2
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Bitbucket.