bitbucket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BB_URL | No | Fallback base URL of the Bitbucket instance, used when BITBUCKET_URL is not set. | |
| BB_USER | No | Fallback Bitbucket username, used when BITBUCKET_USER is not set. | |
| BB_TOKEN | No | Fallback personal access token or app password, used when BITBUCKET_TOKEN is not set. | |
| BITBUCKET_URL | No | Base URL of the Bitbucket Server / Data Center instance, e.g. https://bitbucket.example.com. Takes precedence over BB_URL when both are set. | |
| BITBUCKET_USER | No | Bitbucket username. Takes precedence over BB_USER when both are set. | |
| BITBUCKET_TOKEN | No | Personal access token or app password. Takes precedence over BB_TOKEN when both are set. |
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 |
|---|---|
| bitbucket_list_pull_requestsA | List pull requests in a repository. Optional state (OPEN/MERGED/DECLINED/ALL) and page size. |
| bitbucket_get_pull_requestB | Get one pull request by id (title, description, branches, reviewers, draft flag). |
| bitbucket_get_merge_statusA | Get the merge state of a pull request: canMerge, conflicted, and the list of veto reasons. |
| bitbucket_get_activitiesB | Get the activity stream of a pull request (comments, approvals, updates) for reading the discussion thread. |
| bitbucket_get_blocker_commentsA | List the tasks (blocker comments) on a pull request with their OPEN/RESOLVED state and ids. |
| bitbucket_add_commentB | Post a comment on a pull request. Pass parentId to thread the comment as a reply under an existing comment; omit it for a top-level comment. |
| bitbucket_resolve_taskB | Resolve a task (blocker comment) on a pull request by its comment id. Fetches the comment version first, then flips state to RESOLVED. |
| bitbucket_set_draftA | Turn a pull request's draft flag on or off. Preserves title, description and the full reviewer list across the required PUT (Bitbucket PUT replaces the whole resource). |
| bitbucket_merge_pull_requestA | IRREVERSIBLE: merge a pull request. Requires confirm:true. Uses the current PR version unless one is given. Optional message and strategyId (merge-commit/squash/fast-forward). |
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 9 tools
Each tool targets a distinct pull-request operation: listing, fetching, merge status, activity stream, blocker comments, commenting, resolving tasks, draft flag, and merging. Boundaries between get_activities and get_blocker_comments are clear from their descriptions, and add_comment versus resolve_task is unambiguous.
All tools use a consistent bitbucket_ prefix followed by a clear verb_noun snake_case pattern. The convention is predictable throughout, with no mixing of styles.
Nine tools is well-scoped for a pull-request-focused Bitbucket server. Each tool earns its place by covering a distinct review, discussion, or merge operation.
The set covers reviewing, commenting, task resolution, draft management, and merging existing pull requests well. However, it lacks obvious PR lifecycle operations such as creating, updating, approving, or declining pull requests, and has no repository or branch tools, which are notable gaps for a Bitbucket MCP server.