Atlassian Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_URL | Yes | Your Bitbucket instance URL (e.g., https://bitbucket.org or your self-hosted URL) | |
| BITBUCKET_TOKEN | Yes | Personal Access Token for Bitbucket authentication | |
| BITBUCKET_CACHE_ENABLED | No | Enable/disable caching | true |
| BITBUCKET_ALLOWED_ACTIONS | No | Comma-separated list of allowed tool actions | |
| BITBUCKET_CACHE_TTL_REPOS | No | Repository cache TTL in seconds | 3600 |
| BITBUCKET_DEFAULT_PROJECT | Yes | Default project key for Bitbucket operations |
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 |
|---|---|
| bitbucket_list_pull_requestsB | List pull requests for a repository |
| bitbucket_get_pull_requestB | Get detailed pull request information |
| bitbucket_get_pr_diffB | Get pull request diff/changes |
| bitbucket_get_pr_commitsB | Get commits in a pull request |
| bitbucket_get_pr_activitiesB | Get pull request comments and activities |
| bitbucket_add_pr_commentC | Add a general comment to a pull request |
| bitbucket_add_pr_inline_commentB | Add inline code comment on a pull request |
| bitbucket_reply_to_commentC | Reply to a comment on a pull request |
| bitbucket_resolve_commentB | Resolve a comment thread on a pull request |
| bitbucket_update_commentB | Edit a comment on a pull request |
| bitbucket_approve_prA | Approve a pull request |
| bitbucket_list_projectsB | List accessible Bitbucket projects |
| bitbucket_list_repositoriesC | List repositories in a project |
| bitbucket_get_repositoryB | Get repository details |
| bitbucket_get_branchesC | List repository branches |
| bitbucket_get_commitsC | Get commit history for a repository |
| bitbucket_get_file_contentC | Get file content at a specific ref |
| bitbucket_search_codeB | Search code across repositories in a project |
| bitbucket_search_commitsB | Search commits by message |
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 19 tools
Each tool has a clearly distinct purpose. The action-noun pattern (e.g., 'add_pr_comment' vs 'add_pr_inline_comment') ensures no ambiguity between similar operations.
All tools follow the 'bitbucket_<verb>_<noun>' pattern using snake_case. The naming is perfectly uniform and predictable.
With 19 tools, the set is well-scoped for a Bitbucket server. It covers projects, repositories, pull requests, and comments without being overwhelming.
The tool set heavily focuses on reading and commenting on pull requests and repositories, but lacks create/update/delete operations for repositories and projects, as well as merge/decline for pull requests. This leaves notable gaps for full lifecycle management.