Bitbucket MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_USERNAME | No | Bitbucket username (required for basic auth method) | |
| BITBUCKET_API_TOKEN | No | API token (required for api_token auth method) | |
| BITBUCKET_WORKSPACE | No | Default workspace (optional) | |
| BITBUCKET_USER_EMAIL | No | Your Atlassian email (required for api_token auth method) | |
| BITBUCKET_AUTH_METHOD | No | Authentication method: api_token, oauth, or basic | |
| BITBUCKET_APP_PASSWORD | No | App password (required for basic auth method) | |
| BITBUCKET_OUTPUT_FORMAT | No | Output format: json, toon, or compact (optional) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitbucket_workspaces | Manage Bitbucket workspaces. Actions:
|
| bitbucket_repositories | Manage Bitbucket repositories. Actions:
|
| bitbucket_pull_requests | Manage Bitbucket pull requests. Actions:
|
| bitbucket_branches | Manage Bitbucket branches and tags. Actions:
|
| bitbucket_commits | Manage Bitbucket commits and diffs. Actions:
|
| bitbucket_pipelines | Manage Bitbucket Pipelines CI/CD. Actions:
|
| bitbucket_issues | Manage Bitbucket issue tracking. Actions:
|
| bitbucket_webhooks | Manage Bitbucket webhooks for repositories and workspaces. Actions:
|
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
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/icy-r/bitbucket-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server