Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_TOKEN | No | Your Bitbucket HTTP access token (for Bitbucket Server) | |
| BITBUCKET_BASE_URL | No | The base URL of your Bitbucket Server instance (e.g., https://bitbucket.yourcompany.com) | |
| BITBUCKET_USERNAME | No | Your Bitbucket username (for Bitbucket Cloud) or full email address (for Bitbucket Server, e.g., john.doe@company.com) | |
| BITBUCKET_APP_PASSWORD | No | Your Bitbucket App Password (for Bitbucket Cloud) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_pull_requestA | Get details of a Bitbucket pull request including merge commit information |
| list_pull_requestsC | List pull requests for a repository with optional filters |
| create_pull_requestC | Create a new pull request |
| update_pull_requestA | Update an existing pull request. When updating without specifying reviewers, existing reviewers and their approval status will be preserved. |
| add_commentA | Add a comment to a pull request. Supports: 1) General PR comments, 2) Replies to existing comments, 3) Inline comments on specific code lines (using line_number OR code_snippet), 4) Code suggestions for single or multi-line replacements. For inline comments, you can either provide exact line_number or use code_snippet to auto-detect the line. |
| merge_pull_requestC | Merge a pull request |
| list_branchesB | List branches in a repository |
| delete_branchC | Delete a branch |
| get_pull_request_diffB | Get the diff/changes for a pull request with optional filtering |
| approve_pull_requestC | Approve a pull request |
| unapprove_pull_requestA | Remove approval from a pull request |
| request_changesB | Request changes on a pull request |
| remove_requested_changesB | Remove change request from a pull request |
| get_branchA | Get detailed information about a branch including associated pull requests |
| list_directory_contentA | List files and directories in a repository path |
| get_file_contentB | Get file content from a repository with smart truncation for large files |
| list_branch_commitsB | List commits in a branch with detailed information and filtering options |
| list_pr_commitsB | List all commits that are part of a pull request |
| search_codeA | Search for code across Bitbucket repositories with enhanced context-aware search patterns (currently only supported for Bitbucket Server) |
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 19 tools
Each tool has a distinct purpose with clear boundaries. For example, list_pull_requests retrieves a list, get_pull_request gets details, create_pull_request creates new ones, and update_pull_request modifies existing ones. There is no functional overlap between tools like approve_pull_request, request_changes, and remove_requested_changes, which all handle different review states.
All tool names follow a consistent verb_noun pattern using snake_case. Verbs like list, get, create, update, delete, add, approve, merge, remove, request, search, and unapprove are used predictably. There are no deviations in naming conventions across the 19 tools.
With 19 tools, the count is slightly high but reasonable for a comprehensive Bitbucket server covering repositories, branches, pull requests, and code operations. It includes core CRUD and lifecycle management without being excessive, though it borders on the upper limit of typical scopes.
The tool set provides complete coverage for Bitbucket operations, including full pull request lifecycle (create, get, list, update, approve, request changes, merge, comment), branch management (list, get, delete), repository navigation (list directory, get file), and code search. No obvious gaps exist for the domain.