bitbucket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Your Bitbucket email address | |
| BITBUCKET_API_TOKEN | Yes | Your Bitbucket API token with appropriate scopes | |
| BITBUCKET_CODE_REVIEW_CHECKLIST | No | Absolute path to a custom code review checklist file |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_bitbucket_credsA | Retrieve Bitbucket credentials from environment variables. Returns: tuple: Containing the Bitbucket email and API token. |
| parse_bitbucket_pr_urlA | Parse a Bitbucket pull request URL to extract workspace, repository, and PR ID. |
| get_pr_detailsB | Get detailed information about a Bitbucket pull request. |
| get_bitbucket_pr_diffB | Get the diff for a Bitbucket pull request. |
| get_code_review_checklistA | Get code review checklist which acts as a guideline to review pull request. LLM must call this to get repository specific review guidelines. |
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 5 tools
Each tool has a clearly distinct purpose: credentials, diff, checklist, PR details, and URL parsing. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores, e.g., get_bitbucket_pr_diff, parse_bitbucket_pr_url. No mixing of conventions.
With 5 tools, the set is slightly minimal but still reasonable for focused Bitbucket PR-related tasks. Could include more operations like listing PRs.
The tools cover credential retrieval, diff, review guidelines, PR details, and URL parsing, but lack essential CRUD operations like creating or updating PRs, listing PRs, or commenting.