bitbucket-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | HTTP server bind address | 0.0.0.0 |
| MCP_PORT | No | HTTP server port (only when MCP_TRANSPORT=http) | 3000 |
| NODE_ENV | No | Environment: development, production, test | production |
| LOG_LEVEL | No | Log level: fatal, error, warn, info, debug, trace | info |
| MCP_TRANSPORT | No | Transport type: stdio (local) or http (remote) | stdio |
| BITBUCKET_API_URL | No | API base URL (override for testing) | https://api.bitbucket.org/2.0 |
| BITBUCKET_USERNAME | No | Bitbucket account email (Basic auth, legacy). Required if BITBUCKET_API_TOKEN is not set. | |
| BITBUCKET_API_TOKEN | No | API token (Bearer auth, recommended). If provided, takes priority over username/password. | |
| BITBUCKET_WORKSPACE | Yes | Workspace slug | |
| BITBUCKET_APP_PASSWORD | No | App password (Basic auth, legacy). Required if BITBUCKET_API_TOKEN is not set. |
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_repositoriesB | List repositories in the workspace |
| list_projectsB | List all projects in the workspace |
| list_branchesB | List branches in a repository |
| list_tagsA | List tags in a repository |
| get_branch_commitsA | Get commit history and details for a specific branch |
| clone_repositoryB | Clone a repository using SSH (default) or HTTPS |
| create_branchB | Create a new branch in a repository |
| create_pull_requestB | Create a new pull request |
| list_pull_requestsC | List pull requests in a repository |
| get_pull_requestC | Get details of a specific pull request |
| approve_pull_requestB | Approve a pull request |
| decline_pull_requestC | Decline a pull request |
| merge_pull_requestC | Merge a pull request |
| get_pull_request_commentsB | Get all comments from a pull request |
| add_pull_request_commentB | Add a comment to a pull request |
| list_deploymentsB | List deployments for a repository |
| get_deploymentA | Get details of a specific deployment |
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/fnops/bitbucket-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server