Bitbucket Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_TOKEN | Yes | Bitbucket Cloud app password | |
| BITBUCKET_WORKSPACE | No | Default workspace (can be overridden per request) |
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 |
|---|---|
| get_bb_pull_requestA | Get pull request details from Bitbucket Cloud |
| get_bb_diffB | Get pull request diff from Bitbucket Cloud |
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 2 tools
The two tools, 'get_bb_diff' and 'get_bb_pull_request', have distinct purposes: one retrieves a pull request diff, the other retrieves pull request details. There is no overlap or ambiguity between them.
Both tools follow a consistent 'get_bb_{resource}' pattern, using snake_case and a clear prefix 'get_bb'. The naming is predictable and uniform.
With only 2 tools, the server feels thin for a Bitbucket Cloud integration. While not extremely mismatched, it is below the typical 3-15 range and borders on insufficient.
The tool surface is severely incomplete for a Bitbucket Cloud server. It only provides read operations for pull requests, lacking CRUD operations for repos, branches, commits, and other essential resources.