Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_URL | Yes | Your Bitbucket Server URL (e.g., https://bitbucket.example.com) | |
| BITBUCKET_TOKEN | Yes | Personal Access Token (PAT) for authentication |
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 |
|---|---|
| list_projectsA | List all projects the user has access to in Bitbucket Server |
| get_project_detailA | Get detailed information about a specific Bitbucket Server project |
| list_repositoriesB | List repositories in a specific Bitbucket Server project |
| search_repositoriesA | Find repositories by name or description across all accessible projects |
| get_repo_branchesB | List branches in a Bitbucket Server repository |
| create_branchB | Create a new branch in a Bitbucket Server repository |
| delete_branchB | Delete a branch from a Bitbucket Server repository |
| get_repo_commitsB | List recent commits in a Bitbucket Server repository |
| get_commit_detailA | Get details of a specific commit: commit metadata, changed file list, or full unified diff. Use detail level to control output size. |
| get_repo_tagsB | List tags in a Bitbucket Server repository |
| get_pull_requestsC | Get pull requests for a repository |
| create_pull_requestB | Create a new pull request in a Bitbucket Server repository |
| get_pull_request_detailB | Get detailed information about a specific pull request |
| merge_pull_requestC | Merge a pull request in a Bitbucket Server repository |
| decline_pull_requestB | Decline/reject a pull request in a Bitbucket Server repository |
| get_pull_request_commentsC | Get comments on a specific pull request |
| get_pull_request_diffB | Get the diff of a pull request for code review |
| list_pr_commitsA | List commits on a specific pull request with pagination |
| set_review_statusA | Set review status on a pull request: APPROVED, NEEDS_WORK, or UNAPPROVED. One call, mutually exclusive states. |
| update_pull_requestA | Update an existing pull request (title, description, reviewers). Accepts version from a prior read for conflict prevention; auto-refetches and retries once on 409 conflicts. |
| add_commentA | Add a comment (general, reply, inline, or blocker task) to a pull request in Bitbucket Server |
| manage_commentB | Manage a comment or task on a pull request (edit, delete, resolve, reopen, convert to task, convert to comment) |
| get_file_contentB | Get the raw content of a file from a Bitbucket Server repository |
| get_directory_listingC | List files and directories at a given path in a Bitbucket Server repository |
| get_file_diffA | Get the diff between two commits or branches for a specific file or all files |
| search_codeC | Search for code in a Bitbucket Server repository |
| grepA | Regex search file contents across a repository, like ripgrep on a local clone. Supports content/files/count modes, filename glob, path filtering, context lines, and case-insensitive search. One archive download per repo+commit, streamed in constant memory, cached in-process. |
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 27 tools
Most tools have distinct purposes, but a few like 'grep' and 'search_code' could be confused as both perform code searches. Also, 'add_comment' vs 'manage_comment' are well-separated, but the distinction might not be immediately obvious.
The naming generally follows a verb_noun pattern in snake_case, e.g., create_branch, get_repo_commits. However, 'grep' deviates from the pattern, and 'list_pr_commits' uses an abbreviation instead of 'pull_request', creating minor inconsistency.
With 27 tools, the server covers a wide range of Bitbucket operations. While this is on the higher side, each tool has a specific purpose, and the count is justified for a comprehensive MCP server, with no obvious redundancies.
The server covers core developer workflows: branches, commits, pull requests, files, and search. However, it lacks tools for creating/deleting projects or repositories, and tag management is limited to listing only. Notable gaps exist for full lifecycle management.