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 | No | Your Bitbucket workspace slug (optional; can also be passed as a tool parameter) | |
| BITBUCKET_APP_PASSWORD | Yes | Your Bitbucket App Password |
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_workspacesA | List all Bitbucket workspaces accessible by the authenticated user. Returns workspace names, slugs, and descriptions. |
| list_repositoriesB | List all repositories in a Bitbucket workspace. Returns repository names, slugs, descriptions, and links. |
| get_repositoryA | Get detailed information about a specific repository including its description, language, size, and URLs. |
| list_branchesA | List all branches in a repository. Returns branch names and latest commit hashes. |
| list_commitsA | List recent commits in a repository, optionally filtered by branch. Returns commit messages, authors, dates, and hashes. |
| get_commitB | Get detailed information about a specific commit including author, message, date, and files changed. |
| browse_directoryA | Browse the contents of a directory in a repository. Returns file and folder names, types, and paths. Use this to explore the repository structure. |
| get_file_contentA | Read the full content of a file in a repository. Returns the raw file content as text. Use this to read source code files. |
| search_codeA | Search for code across a repository using Bitbucket's code search. Returns matching files and snippet previews. |
| get_pull_requestsB | List pull requests in a repository. Returns PR titles, authors, states, and descriptions. |
| get_readmeA | Fetch and read the README file of a repository. Automatically finds README.md, README.txt, or readme.rst. |
| get_commit_diffA | Get the diff/patch of a specific commit showing all changes made. Returns unified diff format. |
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 12 tools
Each tool targets a distinct resource and action: workspaces, repositories, branches, commits, directories, file contents, code search, PRs, README, and commit diffs are all clearly separated. Even get_commit and get_commit_diff differ by returning commit metadata versus diff output.
Tool names follow a consistent verb_noun pattern, with list_ for collections and get_ for single items. The singular/plural differences (list_repositories vs get_repository) are logical and match the resource granularity.
With 12 tools covering read-only Bitbucket operations, the count fits well within the ideal 3-15 range. Each tool serves a distinct purpose and contributes to the overall browsing and searching workflow.
The tool set provides solid read-only coverage for exploring workspaces, repositories, branches, commits, file contents, code search, and commit diffs. A notable gap is the lack of a get_pull_request detail endpoint (only list exists) and no PR diff retrieval, but these are minor for a browsing-focused server.