Bitbucket Server MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_URL | Yes | Bitbucket Server base URL | |
| BITBUCKET_TOKEN | No | Personal access token | |
| BITBUCKET_PASSWORD | No | Password (if not using token) | |
| BITBUCKET_USERNAME | No | Username (if not using token) | |
| BITBUCKET_DEFAULT_PROJECT | No | Default project key | |
| BITBUCKET_DEFAULT_REVIEWERS | No | Comma-separated reviewer usernames |
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_repositoriesB | List all repositories in a Bitbucket project |
| list_pull_requestsC | List all pull requests for a repository in a Bitbucket project |
| list_branchesB | List all branches in a repository |
| get_repository_detailsC | Get details of a repository |
| create_pull_requestC | Create a new pull request |
| get_pull_requestB | Get pull request details |
| merge_pull_requestC | Merge a pull request |
| decline_pull_requestC | Decline a pull request |
| add_commentC | Add a comment to a pull request |
| get_diffB | Get pull request diff |
| get_reviewsC | Get pull request reviews |
| add_inline_commentB | Add an inline comment to a file in a pull request |
| suggest_code_changeC | Add a code suggestion comment to a file in a pull request |
| delete_pull_requestC | Delete a pull request by declining it |
| approve_pull_requestB | Approve a pull request |
| unapprove_pull_requestB | Unapprove (reject approval for) a pull request |
| get_repository_archiveB | Download the entire repository as a zip or tar archive |
| get_pull_request_commentsA | Get all comments on a pull request |
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 18 tools
Most tools are distinct, but add_comment and add_inline_comment have overlap (inline is a subtype), and get_pull_request_comments vs get_reviews may confuse an agent. Overall, clear boundaries for most.
All tool names follow a consistent verb_noun pattern in snake_case, e.g., list_repositories, get_pull_request. No mixing of styles or irregularities.
18 tools is well-scoped for a Bitbucket server MCP, covering repositories, branches, and pull requests with comments and reviews. Neither too few nor excessive.
Core PR lifecycle is covered (create, get, list, approve, merge, decline), but missing update_pull_request and branch management beyond listing (create, delete branch). Archive and details are present, but some operations are absent.