Bitbucket Cloud MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_CLIENT_ID | No | Your Bitbucket OAuth 2.0 client ID | |
| BITBUCKET_ACCESS_TOKEN | No | Your Bitbucket app password for authentication | |
| BITBUCKET_CLIENT_SECRET | No | Your Bitbucket OAuth 2.0 client secret |
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 repositories in a workspace. Returns paginated results with repository details. |
| get_repositoryC | Get details of a specific repository including its branches, pull requests, and other metadata. |
| create_repositoryC | Create a new repository in the specified workspace. |
| delete_repositoryA | Delete a repository. This action is irreversible. |
| list_repository_forksC | List all forks of a repository. |
| list_pull_requestsC | List pull requests for a repository with optional filtering by state. |
| get_pull_requestB | Get details of a specific pull request including its source, destination, and status. |
| create_pull_requestC | Create a new pull request from a source branch to a destination branch. |
| update_pull_requestC | Update a pull request title, description, or destination branch. |
| merge_pull_requestB | Merge an open pull request. Supports merge commit, squash, and fast-forward strategies. |
| decline_pull_requestC | Decline/close a pull request without merging. |
| approve_pull_requestC | Approve a pull request. |
| request_changesC | Request changes on a pull request. |
| list_pr_commentsC | List all comments on a pull request. |
| add_pr_commentB | Add a comment to a pull request. Can be a general comment or an inline comment on a specific file/line. |
| get_pr_diffC | Get the diff for a pull request showing all changes. |
| list_branchesB | List all branches in a repository. |
| get_branchB | Get details of a specific branch including its latest commit. |
| create_branchC | Create a new branch from a specific commit or existing branch. |
| delete_branchC | Delete a branch from a repository. |
| list_commitsC | List commits in a repository with optional filtering by branch. |
| get_commitC | Get details of a specific commit including its message, author, and parent commits. |
| get_commit_diffC | Get the diff for a specific commit showing all changes. |
| list_issuesC | List issues in a repository with optional filtering. |
| get_issueC | Get details of a specific issue. |
| create_issueC | Create a new issue in a repository. |
| update_issueC | Update an existing issue. |
| delete_issueC | Delete an issue from a repository. |
| list_pipelinesC | List pipeline runs for a repository. |
| get_pipelineC | Get details of a specific pipeline run. |
| trigger_pipelineC | Trigger a new pipeline run on a branch, tag, or bookmark. |
| stop_pipelineC | Stop a running pipeline. |
| search_codeC | Search for code across all repositories in a workspace. |
| get_file_contentC | Get the content of a file from a repository. |
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 34 tools
Every tool has a clearly distinct purpose targeting specific resources and actions in the Bitbucket Cloud domain. For example, 'get_pull_request' retrieves details while 'approve_pull_request' performs an action, and tools like 'list_pr_comments' vs 'add_pr_comment' handle different aspects of PR comments without overlap.
All tools follow a consistent verb_noun pattern with snake_case throughout, such as 'create_branch', 'list_issues', 'update_pull_request'. There are no deviations in naming conventions, making the set highly predictable and readable.
With 34 tools, the count is borderline high for a single server, potentially feeling heavy and overwhelming for agents. While it covers many Bitbucket Cloud operations, a more modular approach might improve usability without sacrificing functionality.
The tool surface provides comprehensive CRUD and lifecycle coverage for repositories, branches, commits, issues, pull requests, pipelines, and code search. It includes all essential operations like create, get, list, update, delete, and specific actions such as merge, approve, and trigger, with no obvious gaps for the domain.