Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_URL | Yes | Bitbucket base URL, such as https://api.bitbucket.org or https://bitbucket.example.com/bitbucket | |
| BITBUCKET_TOKEN | Yes | API token, app password, or personal access token | |
| BITBUCKET_USERNAME | No | Username paired with the token for basic auth (required if BITBUCKET_AUTH_TYPE is basic) | |
| BITBUCKET_AUTH_TYPE | No | bearer or basic | bearer |
| BITBUCKET_MAX_DIFF_BYTES | No | Maximum UTF-8 byte size returned in rawDiff | 1000000 |
| BITBUCKET_ENABLE_WRITE_TOOLS | No | Set to true to allow tools that modify Bitbucket, currently PR comment creation | false |
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_pull_requestA | Retrieves metadata, description, state/status, author, reviewers, source branch, destination branch, timestamps, and links for a specific Bitbucket pull request. |
| get_pull_request_diffA | Retrieves the raw diff and, when available, a structured list of changed files for a specific Bitbucket pull request. |
| add_pull_request_commentA | Creates a general, file, or inline line comment on a Bitbucket pull request. This is a write operation and requires BITBUCKET_ENABLE_WRITE_TOOLS=true. |
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 3 tools
Each tool targets a distinct aspect of pull requests: commenting, metadata retrieval, and diff retrieval. No functional overlap, making selection clear.
All tool names follow a consistent verb_noun snake_case pattern (add_*, get_*, get_*), which is predictable and easy to follow.
Three tools is minimal for a Bitbucket server; it covers only basic pull request read operations and commenting, missing core CRUD operations, but it is not extreme.
The toolset lacks essential operations like listing, creating, updating, or merging pull requests. Agents cannot perform a full workflow, leaving significant gaps.