bitbucket-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_USERNAME | No | Your Atlassian account email (required for User API tokens) | |
| BITBUCKET_API_TOKEN | No | Your User API token or Workspace/Project token | |
| BITBUCKET_WORKSPACE | No | Default workspace used when the parameter is omitted |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| repositoriesA | List repositories in a Bitbucket workspace, or get details for a single repository when |
| pull-requestsB | List pull requests for a repository, or get details for a single pull request when |
| create-pull-requestC | Create a new pull request in a repository |
| update-pr-descriptionC | Update the title and/or description of a pull request |
| get-pr-diffC | Get the diff/changes for a specific pull request |
| pr-commentsA | List comments on a pull request, or get details for a single comment when |
| create-pr-commentB | Create a comment on a pull request, or reply to an existing comment by specifying a parent comment ID |
| resolve-pr-commentC | Resolve or unresolve a pull request comment thread |
| commitsA | List recent commits for a repository, or get details for a single commit when |
| list-branchesC | List branches for a repository |
| list-issuesC | List issues for a repository |
| pipelinesA | List pipelines for a repository, or get details for a single pipeline when |
| trigger-pipelineC | Trigger a new pipeline for a repository |
| pipeline-stepsB | Pipeline step operations. Use |
| searchC | Search across repositories, pull requests, issues, and commits in a workspace |
| health-checkB | Check connectivity to Bitbucket API and validate credentials |
| get-metricsC | Get server performance metrics and statistics |
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
Most tools have clearly distinct resource/action targets, especially across PRs, pipelines, comments, and repositories. The only mild overlaps are health-check vs get-metrics and the dual list/get pattern used by repositories, pull-requests, commits, and pipelines, but the descriptions clarify parameter behavior.
All names use kebab-case, but the set mixes noun-only resource names (repositories, commits, pr-comments) with verb_noun names (create-pull-request, get-pr-diff) and an action-parameter tool (pipeline-steps). The convention is readable but not uniform.
17 tools is slightly above the ideal 3-15 range but still reasonably scoped for Bitbucket's breadth across repositories, commits, branches, PRs, pipelines, issues, and search. Each major area has coverage, with no obvious duplicate tools.
Core read and some write workflows are covered for PRs and pipelines, but there are notable gaps: no create/update issue, no PR approval or merge, no branch creation/deletion, and no source file browsing. Agents can still handle many tasks but will hit dead ends for common Bitbucket lifecycle operations.