Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_DEBUG | No | Set to 'true' to enable debug logging | |
| BITBUCKET_EMAIL | Yes | Your Atlassian account email | |
| BITBUCKET_API_TOKEN | Yes | Your Bitbucket API token. Create at https://id.atlassian.com/manage-profile/security/api-tokens | |
| BITBUCKET_DEFAULT_FORMAT | No | Default output format for all tools: text, json, or toon | text |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bb_get_repositoryB | Get detailed information about a specific repository |
| bb_list_repositoriesB | List repositories in a workspace |
| bb_list_workspacesA | List all accessible workspaces for discovery and exploration |
| bb_get_pull_requestsB | Get pull requests for a repository |
| bb_get_pull_requestB | Get detailed information about a specific pull request |
| bb_get_pull_request_commentsB | Get comments for a specific pull request |
| bb_get_pull_request_commentA | Get a single comment by ID from a pull request |
| bb_get_comment_threadA | Get a comment thread including the root comment and all nested replies |
| bb_get_pull_request_activityA | Get activity (reviews, approvals, comments) for a specific pull request |
| bb_get_pull_request_diffB | Get the raw unified diff for a pull request. Returns text/plain diff output showing all changes. |
| bb_get_pull_request_diffstatA | Get the diffstat for a pull request — per-file summary of lines added/removed and change status. |
| bb_get_diffA | Get the raw unified diff between commits. Use a single commit hash to diff against its parent, or "commit1..commit2" for comparing two commits. |
| bb_get_diffstatA | Get diffstat (per-file change summary) between commits. Use a single commit hash or "commit1..commit2". |
| bb_get_pr_commitsA | List commits that belong to a pull request |
| bb_get_pr_statusesA | Get CI/CD build statuses for a pull request (checks whether builds pass or fail) |
| bb_get_commitA | Get detailed information about a specific commit (hash, message, author, parents) |
| bb_get_commit_statusesB | Get CI/CD build statuses for a specific commit |
| bb_get_merge_baseA | Get the common ancestor (merge-base) between two commits or branches. Use "branch1..branch2" format. |
| bb_get_file_historyA | Get the commit history for a specific file — shows which commits modified the file and when. |
| bb_get_tagsA | List tags (release tags, version tags) for a repository |
| bb_get_tagA | Get detailed information about a specific tag including its target commit |
| bb_get_branchA | Get detailed information about a specific branch including target commit and merge strategies |
| bb_list_pipelinesA | List CI/CD pipeline runs for a repository. Shows build status, trigger, and duration. |
| bb_get_pipelineA | Get detailed information about a specific pipeline run |
| bb_get_pipeline_stepsA | List the steps/stages of a pipeline run with their status and duration |
| bb_get_pipeline_step_logA | Get the build log output for a specific pipeline step. Useful for diagnosing build failures. |
| bb_get_issuesC | Get issues for a repository |
| bb_get_issueB | Get detailed information about a specific issue |
| bb_get_commitsB | Get commits for a repository branch |
| bb_get_branchesC | Get branches for a repository |
| bb_get_file_contentB | Get the content of a file from a repository with pagination support |
| bb_browse_repositoryA | Browse files and directories in a repository to explore structure |
| bb_get_userB | Get public information about a Bitbucket user by username or UUID. If no user is specified, returns the authenticated user. Note: private profiles may have limited fields. |
| bb_get_current_userC | Get information about the currently authenticated user. |
| bb_search_repositoriesA | Search for repositories within a workspace by name or description. Uses Bitbucket server-side filtering to search across all repositories, not just the first page. Supports sorting with the sort parameter. |
| bb_search_codeA | Search for code content within a workspace. Supports filtering by repository, language, and file extension. |
| bb_get_workspaceC | Get information about a workspace |
| bb_get_contextA | Get a curated bundle of PR context in a single call: PR metadata, diffstat summary, build/review status, and comment previews. Accepts a Bitbucket PR URL, or workspace/repo with pull_request_id or branch. Use detail_level "full" for PR description, per-file diffstat, and last 20 comments. |
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 38 tools
Several tools have overlapping purposes, such as bb_get_diff vs bb_get_pull_request_diff, bb_get_diffstat vs bb_get_pull_request_diffstat, and bb_get_pr_commits vs bb_get_commits. While descriptions provide some clarity, an agent could easily select the wrong tool when looking for diff or commit information.
The naming follows a consistent 'bb_verb_noun' pattern, with plural nouns for list operations and singular for single items. However, there is inconsistency in abbreviation: 'pr' is used in some tools (bb_get_pr_commits) while 'pull_request' is fully written out in others (bb_get_pull_request), creating minor confusion.
With 38 tools, the server far exceeds the 25-tool threshold, making the set feel bloated. Many tools are highly specific read operations (e.g., bb_get_merge_base, bb_get_comment_thread), which may overwhelm agents and increase selection difficulty.
The tool set is entirely read-only, with no create, update, delete, or comment operations for repositories, pull requests, or issues. This is a significant gap for a Bitbucket MCP server, as agents cannot perform common workflows like creating PRs, commenting on code, or managing issues.