Bitbucket Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_BASE_URL | No | Override API base URL (optional) | |
| BITBUCKET_READONLY | No | Set to 'true' to block all write operations (optional, default false) | |
| ATLASSIAN_API_TOKEN | Yes | Atlassian API token (required) | |
| ATLASSIAN_USER_EMAIL | Yes | Atlassian account email (required) | |
| BITBUCKET_ALLOWED_REPOS | No | Comma-separated allowlist of repositories (slug or workspace/slug) (optional) | |
| BITBUCKET_DEFAULT_WORKSPACE | No | Default workspace slug (optional) | |
| BITBUCKET_ALLOWED_WORKSPACES | No | Comma-separated allowlist of workspace slugs (optional) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bb_whoamiA | Get the currently authenticated Bitbucket user |
| bb_list_workspacesC | List Bitbucket workspaces accessible to the authenticated user |
| bb_list_repositoriesC | List repositories in a Bitbucket workspace |
| bb_get_repositoryB | Get details of a specific Bitbucket repository |
| bb_list_branchesB | List branches in a Bitbucket repository |
| bb_list_commitsC | List commits in a Bitbucket repository, optionally for a specific branch/tag/hash |
| bb_get_fileB | Get the raw content of a file from a Bitbucket repository |
| bb_create_commit_filesB | Create or update files in a Bitbucket repository by creating a new commit |
| bb_create_branchC | Create a new branch in a Bitbucket repository |
| bb_delete_branchA | Delete a branch from a Bitbucket repository (destructive action, requires confirmation) |
| bb_list_directoryB | List the contents of a directory in a Bitbucket repository |
| bb_search_codeC | Search for code in a Bitbucket workspace or repository |
| bb_list_pull_requestsC | List pull requests in a Bitbucket repository, optionally filtered by state |
| bb_get_pull_requestB | Get details of a specific pull request |
| bb_create_pull_requestC | Create a new pull request |
| bb_get_pull_request_diffB | Get the diff of a pull request |
| bb_get_pull_request_diffstatA | Get the diffstat (summary of changed files) of a pull request |
| bb_list_pull_request_activityB | List activity (comments, approvals, updates) on a pull request |
| bb_add_pull_request_commentA | Add a comment to a pull request, optionally as an inline comment on a specific file and line. Use parent_id to create a threaded reply to an existing comment. |
| bb_resolve_pull_request_commentB | Resolve a comment thread on a pull request |
| bb_unresolve_pull_request_commentA | Reopen a resolved comment thread on a pull request |
| bb_approve_pull_requestC | Approve a pull request |
| bb_request_changes_pull_requestC | Request changes on a pull request |
| bb_merge_pull_requestA | Merge a pull request (destructive action, requires confirmation) |
| bb_update_pull_requestB | Update a pull request's title, description, or reviewers |
| bb_decline_pull_requestB | Decline a pull request (destructive action, requires confirmation) |
| bb_list_issuesB | List issues in a Bitbucket repository |
| bb_get_issueB | Get details of a specific issue in a Bitbucket repository |
| bb_create_issueB | Create a new issue in a Bitbucket repository |
| bb_comment_issueA | Add a comment to an issue in a Bitbucket repository |
| bb_list_pipelinesA | List pipelines in a Bitbucket repository, sorted by newest first |
| bb_get_pipelineB | Get details of a specific pipeline in a Bitbucket repository |
| bb_trigger_pipelineB | Trigger a new pipeline run in a Bitbucket repository |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Each tool targets a distinct resource and action, with clear prefixes and specific nouns. Even within the large set of pull request tools, each has a unique purpose (e.g., approve vs. merge vs. request changes). No two tools are easily confused.
All tools follow the 'bb_verb_noun' pattern consistently, using snake_case. Verbs are well-chosen (create, get, list, delete, update, etc.) and nouns are specific (pull_request, issue, branch, etc.). No mixing of conventions.
33 tools cover a wide range of Bitbucket functionality (repos, PRs, issues, pipelines, search, etc.). While on the higher end, the count is justified by the domain's complexity. Some tools could be consolidated (e.g., diff and diffstat), but overall it's well-scoped.
Pull request coverage is thorough (CRUD, comments, diff, activity). Issues lack update/delete, and repositories lack create/delete. Pipelines are missing cancel/stop. These are notable but not critical gaps, as the core workflows are covered.