Bitbucket MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_EMAIL | Yes | Your Atlassian account email used for authentication. | |
| BITBUCKET_API_TOKEN | Yes | Bitbucket API token with required scopes (read:repository:bitbucket, read:pullrequest:bitbucket, write:pullrequest:bitbucket). | |
| BITBUCKET_WORKSPACE | No | Optional Bitbucket workspace. If omitted, workspace must be specified in each tool call. |
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 |
|---|---|
| list_repositoriesA | Lists repositories in a workspace, sorted by most recently updated. |
| list_pull_requestsB | Lists a repository's PRs, filtered by state. |
| get_pull_requestA | Returns full metadata for a PR (description, branches, reviewers, state). |
| get_pull_request_diffB | Returns the PR's full unified diff — the basis for a first-pass review. |
| get_pull_request_commentsB | Lists a PR's existing comments (general and inline). |
| get_pull_request_commitsC | Lists the commits that make up the PR. |
| get_fileA | Reads a file's contents. If |
| list_directoryA | Lists files and directories under a repository path at a commit/branch. Use it to explore the project structure while reviewing a PR. Empty |
| add_pull_request_commentA | WRITE — posts a comment on the PR. Provide |
| approve_pull_requestB | WRITE — records the authenticated user's approval on the PR. |
| request_changes_pull_requestB | WRITE — records the authenticated user's 'request changes' on the PR. |
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 11 tools
Each tool has a clearly distinct purpose: listing repos, PRs, directory/file reading, PR metadata retrieval (diff, comments, commits), and PR write actions (comment, approve, request changes). No overlap in functionality.
All tools follow a consistent verb_noun snake_case pattern (e.g., get_pull_request, add_pull_request_comment, list_repositories). No mixing of styles or vague verbs.
11 tools is well-scoped for a Bitbucket integration, covering essential read and write operations for repositories and pull request review workflows without being excessive.
Covers core PR review actions (get, comment, approve, request changes) plus file/directory exploration. Minor gaps like merge/decline PR or update/delete comments, but sufficient for typical agent use.