Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_TOKEN | No | Your HTTP access token (for Server). | |
| BITBUCKET_BASE_URL | No | The base URL of your Bitbucket Server instance (e.g., https://bitbucket.yourcompany.com). | |
| BITBUCKET_USERNAME | No | Your Bitbucket username (for Cloud) or email (for Server). | |
| BITBUCKET_APP_PASSWORD | No | Your Bitbucket app password (for Cloud). |
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 |
|---|---|
| get_pull_requestA | Get details of a Bitbucket pull request including merge commit information |
| list_pull_requestsC | List pull requests for a repository with optional filters |
| create_pull_requestC | Create a new pull request |
| update_pull_requestA | Update an existing pull request. When updating without specifying reviewers, existing reviewers and their approval status will be preserved. |
| add_commentA | Add a comment to a pull request. Supports: 1) General PR comments, 2) Replies to existing comments, 3) Inline comments on specific code lines (using line_number OR code_snippet), 4) Code suggestions for single or multi-line replacements. For inline comments, you can either provide exact line_number or use code_snippet to auto-detect the line. |
| merge_pull_requestC | Merge a pull request |
| list_branchesB | List branches in a repository |
| delete_branchC | Delete a branch |
| get_pull_request_diffB | Get the diff/changes for a pull request with optional filtering |
| approve_pull_requestC | Approve a pull request |
| unapprove_pull_requestA | Remove approval from a pull request |
| request_changesB | Request changes on a pull request |
| remove_requested_changesB | Remove change request from a pull request |
| get_branchA | Get detailed information about a branch including associated pull requests |
| list_directory_contentA | List files and directories in a repository path |
| get_file_contentB | Get file content from a repository with smart truncation for large files |
| list_branch_commitsB | List commits in a branch with detailed information and filtering options |
| list_pr_commitsB | List all commits that are part of a pull request |
| search_codeA | Search for code across Bitbucket repositories with enhanced context-aware search patterns (currently only supported for Bitbucket Server) |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/zhanglc/bitbucket-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server