bitbucket-dc-mcp
by inkman97
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_TOKEN | Yes | HTTP Access Token (Bearer) | |
| BITBUCKET_BASE_URL | Yes | Base URL of your Bitbucket DC instance (must be https) | |
| BITBUCKET_LFS_MODE | No | LFS handling: disabled (default), enabled, or auto | disabled |
| BITBUCKET_USERNAME | Yes | Username associated with the token | |
| BITBUCKET_WORKSPACE | No | Local directory for cloned repos. Default ~/mcp-workspace | ~/mcp-workspace |
| BITBUCKET_SESSION_ID | No | Session identifier for log correlation. Auto-generated if unset | |
| BITBUCKET_GIT_TIMEOUT | No | Seconds. Default 300 | 300 |
| BITBUCKET_HTTP_TIMEOUT | No | Seconds. Default 30 | 30 |
| BITBUCKET_ALLOWED_HOSTS | No | Comma-separated host allowlist. Defaults to host of BITBUCKET_BASE_URL | |
| BITBUCKET_AUDIT_LOG_PATH | No | Path to audit log. Default {workspace}/audit.log | {workspace}/audit.log |
| BITBUCKET_MAX_FILE_BYTES | No | Max bytes returned by get_file_content, written by write_file, or applied by apply_patch. Default 1 MiB | 1048576 |
| BITBUCKET_DEFAULT_PROJECT | No | Default project key for tool calls |
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
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/inkman97/bitbucket-dc-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server