bitbucket-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Your Bitbucket email address used for authentication. | |
| BITBUCKET_API_TOKEN | Yes | Your Bitbucket API token (app password) with required scopes for repositories, pull requests, and pipelines. |
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 |
|---|---|
| listPullRequestsC | List pull requests in a repository, filtered by state |
| getPullRequestC | Get details of a specific pull request |
| createPullRequestB | Create a new pull request |
| updatePullRequestB | Update a pull request (title, description, reviewers, destination branch) |
| getPullRequestCommitsC | List commits on a pull request |
| createDraftPullRequestC | Create a draft pull request |
| publishDraftPullRequestA | Publish a draft pull request (mark it as ready for review) |
| convertToDraftB | Convert an open pull request back to draft |
| getPullRequestCommentsC | List all comments on a pull request |
| addPullRequestCommentB | Add a comment to a pull request (general or inline on a specific file/line) |
| updatePullRequestCommentC | Update an existing comment on a pull request |
| deletePullRequestCommentB | Delete a comment from a pull request |
| getPullRequestDiffC | Get the raw diff of a pull request |
| getPullRequestDiffStatC | Get file-level change statistics for a pull request (files added/modified/removed, lines changed) |
| listPipelineRunsC | List recent pipeline runs, optionally filtered by status or branch |
| getPipelineRunB | Get details of a specific pipeline run (state, duration, result) |
| runPipelineB | Trigger a new pipeline run on a branch, tag, or custom pipeline |
| stopPipelineA | Stop/abort a running pipeline |
| getPipelineStepsB | List steps within a pipeline run and their results |
| getPipelineStepLogsA | Get stdout/stderr logs from a specific pipeline step |
| getPullRequestActivityB | Get the activity log for a pull request (comments, approvals, pushes, status changes) |
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 21 tools
Each tool targets a distinct resource and action, and the pull request and pipeline namespaces are clearly separated. Minor overlap exists between getPullRequestComments and getPullRequestActivity, and between getPullRequestDiff and getPullRequestDiffStat, but the descriptions are clear enough to resolve ambiguity.
Tool names consistently use camelCase and follow a clear verb_noun pattern, with list/get/create/update/delete verbs and PR or pipeline context prefixes. There are minor inconsistencies like addPullRequestComment vs createPullRequest and convertToDraft, but the naming remains predictable overall.
At 21 tools, the server is on the heavy side and covers two fairly broad domains: pull requests and pipelines. The count feels borderline; some tools like getPullRequestDiff and getPullRequestDiffStat could potentially be consolidated, though each still serves a distinct use case.
The pull request lifecycle covers creation, updating, drafts, comments, diffs, commits, and activity, but core Bitbucket actions like merge, decline, and approve are missing. Pipeline coverage is solid with run, stop, steps, and logs, but the PR gaps prevent full workflow completion.