Bitbucket MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Your Atlassian account email | |
| BITBUCKET_API_TOKEN | Yes | Bitbucket App Password (from account → App passwords) | |
| BITBUCKET_WORKSPACE | Yes | Full workspace URL or slug (e.g. my-workspace) |
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 |
|---|---|
| search_by_jira_idA | Search Bitbucket for PRs and commits related to a Jira issue ID. Finds PRs where the ID appears in the title or source branch name, and commits where it appears in the message. |
| search_by_pr_titleA | Search pull requests by keyword in the title. Returns PR details, description, comments, and changed files. |
| get_changed_filesB | Get the list of files changed in a pull request or commit, with per-file line add/remove counts. |
| get_diffA | Get the full unified diff for a pull request or commit. Diffs larger than 50,000 characters are truncated at a line boundary. |
| get_file_contentA | Get the full content of a file at a given branch name or commit hash. If no ref is given, the repository's default branch is used. |
| get_commit_history_for_fileB | Get the commit history for a specific file, showing who changed it and how frequently. |
| get_related_prsA | Find other pull requests that touched the same files as a given PR or commit. Useful for discovering related work and potential conflict areas. |
| list_reposB | List all repositories in the configured Bitbucket workspace. |
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 8 tools
Each tool has a clearly distinct purpose: get_changed_files, get_commit_history_for_file, get_diff, get_file_content, get_related_prs, list_repos, search_by_jira_id, search_by_pr_title. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., get_changed_files, list_repos, search_by_jira_id). The verbs (get, list, search) and nouns are clear and predictable.
With 8 tools, the server is well-scoped for its purpose. It covers essential Bitbucket operations without being too sparse or overwhelming.
The tool set lacks fundamental PR operations such as listing PRs, getting a single PR by ID, creating or updating PRs, and commenting. It is read-only and focused on code review and searching, but missing basic CRUD for PRs is a notable gap.