Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_USERNAME | Yes | Your Bitbucket username | |
| BITBUCKET_WORKSPACE | Yes | Your Bitbucket workspace name (typically your username or organization name) | |
| BITBUCKET_APP_PASSWORD | Yes | Your Bitbucket app password with Repository Read permissions |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_repositoriesB | List all repositories in the configured Bitbucket workspace |
| get_repository_detailsC | Get detailed information about a specific repository including latest commit info |
| list_commitsC | Get commit information for a specific repository |
| get_commitC | Get a single commit by its hash. |
| update_repository_branching_model_settingsC | Update the branching model configuration for a repository. |
| update_project_branching_model_settingsC | Update the branching model configuration for a project. |
| list_branch_restrictionsC | List all branch restrictions for a repository. |
| get_branch_restrictionC | Get a single branch restriction by its ID. |
| get_projectB | Get a single project by its key. |
| list_default_reviewersC | List default reviewers for a project. |
| list_pull_requestsC | List all pull requests in a repository. |
| get_pull_requestC | Get a single pull request by its ID. |
| create_pull_requestC | Create a new pull request. |
| update_pull_requestC | Update an existing pull request. |
| list_workspacesB | List all workspaces accessible by the current user. |
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 15 tools
Each tool has a clearly distinct purpose targeting specific resources and actions, such as get_commit for retrieving commits, list_pull_requests for listing PRs, and update_project_branching_model_settings for configuration updates. There is no overlap or ambiguity between tools, making it easy for an agent to select the correct one.
All tool names follow a consistent verb_noun pattern with snake_case, such as get_commit, list_repositories, and update_pull_request. This uniformity enhances readability and predictability, allowing agents to easily understand and navigate the toolset without confusion.
With 15 tools, the server is well-scoped for Bitbucket operations, covering repositories, commits, pull requests, projects, workspaces, and branching models. Each tool serves a distinct and necessary function, avoiding bloat while providing comprehensive coverage for typical workflows.
The toolset offers strong coverage for core Bitbucket operations, including CRUD-like actions for pull requests, repositories, and projects, along with listing and updating functionalities. A minor gap exists in the lack of tools for creating or deleting repositories, projects, or commits, but agents can still handle most workflows effectively.