Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_USERNAME | Yes | Your Bitbucket username or email address. | |
| BITBUCKET_WORKSPACE | No | Default Bitbucket workspace slug (optional). | |
| BITBUCKET_APP_PASSWORD | Yes | Your Bitbucket App Password. Requires permissions for Account (Read), Workspace (Read), Repositories (Read/Write), and Pull Requests (Read/Write). |
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 |
|---|---|
| list_workspacesB | List all available Bitbucket workspaces |
| list_repositoriesC | List all repositories in a workspace |
| get_repositoryC | Get details of a specific repository |
| list_branchesC | List all branches in a repository |
| get_branchC | Get details of a specific branch |
| list_pull_requestsC | List pull requests in a repository |
| get_pull_requestC | Get details of a specific pull request |
| create_pull_requestC | Create a new pull request |
| approve_pull_requestC | Approve a pull request |
| merge_pull_requestC | Merge a pull request |
| add_pull_request_commentC | Add a comment to a pull request |
| list_commitsC | List commits in a repository |
| get_commitC | Get details of a specific commit |
| get_file_contentC | Get the content of a file from a repository |
| search_codeC | Search for code in a workspace |
| compare_branchesC | Compare two branches |
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 16 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Bitbucket domain. There is no overlap or ambiguity between tools like 'get_branch', 'list_branches', 'compare_branches', or 'get_pull_request', 'list_pull_requests', 'merge_pull_request'.
All tools follow a consistent verb_noun pattern throughout (e.g., 'list_repositories', 'get_commit', 'create_pull_request'). The naming is uniform with clear action prefixes and descriptive resource names, making the set predictable and readable.
With 16 tools, the count is slightly on the higher side but reasonable for a comprehensive Bitbucket server covering repositories, branches, commits, pull requests, and workspaces. It's well-scoped, though it might feel heavy compared to simpler servers.
The tool surface provides complete CRUD/lifecycle coverage for the Bitbucket domain, including listing, getting, creating, merging, and commenting on pull requests, along with repository, branch, commit, and workspace operations. There are no obvious gaps, ensuring agents can handle full workflows without dead ends.