bb-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Atlassian account email, used with the API token for Basic Auth. | |
| BITBUCKET_BASE_URL | No | API base URL override. Defaults to https://api.bitbucket.org/2.0. | https://api.bitbucket.org/2.0 |
| BITBUCKET_API_TOKEN | Yes | API token from id.atlassian.com. | |
| BITBUCKET_REPO_SLUG | No | Default repository slug, so tools can omit repoSlug per call. | |
| BITBUCKET_WORKSPACE | No | Default workspace slug, so tools can omit workspace per call. |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bb_list_pull_requestsA | Lists pull requests in a repository, optionally filtered by state or a Bitbucket query string. |
| bb_get_pull_requestA | Fetches full details of a single pull request, including its description. |
| bb_create_pull_requestB | Creates a new pull request from a source branch into a destination branch. |
| bb_update_pull_requestA | Updates an open pull request. Only the provided fields are changed; omit a field to leave it as-is. For description-only edits, prefer bb_update_pull_request_description. |
| bb_merge_pull_requestC | Merges an open pull request. |
| bb_decline_pull_requestB | Declines an open pull request. |
| bb_approve_pull_requestB | Approves a pull request as the authenticated user. |
| bb_unapprove_pull_requestA | Removes the authenticated user's approval from a pull request. |
| bb_get_pull_request_diffA | Fetches the unified diff of a pull request as raw text. |
| bb_get_pull_request_diffstatA | Fetches a per-file summary of changes (added/removed/modified, line counts) for a pull request. |
| bb_list_pull_request_commentsA | Lists all (non-deleted) comments on a pull request, including inline code comments and replies. |
| bb_get_pull_request_commentB | Fetches a single comment on a pull request by ID. |
| bb_create_pull_request_commentA | Adds a comment to a pull request. Provide |
| bb_update_pull_request_commentA | Edits the body of an existing comment. Only the comment's author can edit it. |
| bb_delete_pull_request_commentB | Deletes a comment from a pull request. |
| bb_get_pull_request_descriptionA | Fetches just a pull request's description text, as raw Markdown. |
| bb_update_pull_request_descriptionA | Replaces a pull request's description without touching its title, reviewers or destination branch. |
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 17 tools
Each tool targets a distinct action on a pull request or its comments, from core lifecycle (create, get, update, merge, decline) to diffs and comment management. The only potential overlap is between bb_update_pull_request and bb_update_pull_request_description, but the descriptions clearly delineate when to use the specific description-only variant, making misselection unlikely.
All tools follow a consistent verb_noun naming pattern with a bb_ prefix, using snake_case throughout (e.g., bb_list_pull_requests, bb_delete_pull_request_comment). Verbs are uniformly lowercase and resource names are consistently structured, with no mixing of camelCase or other conventions.
At 17 tools, the set is slightly above the typical 3-15 range for a well-scoped server, but each tool serves a distinct purpose in managing pull requests and their comments. The count is justified by the comprehensive feature set, though it edges toward the higher end.
The server provides full CRUD and lifecycle coverage for pull requests, including creation, retrieval, updates, merge, decline, approval, diffs, and comment management. Minor gaps exist, such as no direct tool for managing reviewers or listing commits, but these are peripheral to the core PR workflow and can be worked around via API query capabilities.