ManpreetShuann/bitbucket-mcp
An mcp for bitbucket enterprise edition
Platform-specific configuration:
{
"mcpServers": {
"bitbucket-mcp": {
"command": "npx",
"args": [
"-y",
"bitbucket-mcp"
]
}
}
}Add the config above to .claude/settings.json under the mcpServers key.
An MCP (Model Context Protocol) server for Atlassian Bitbucket Server / Data Center (Enterprise). Provides 55 tools for reading and writing projects, repositories, branches, files, commits, pull requests, and code search — with no deletion operations by design.
# Clone and install
cd bitbucket-mcp
uv synccd bitbucket-mcp
docker build -t bitbucket-mcp .Set two environment variables (plus one optional):
| Variable | Description | |---|---| | BITBUCKET_URL | Base URL of your Bitbucket Server (e.g., https://bitbucket.yourcompany.com) | | BITBUCKET_TOKEN | HTTP access token (create in Bitbucket > User Settings > HTTP Access Tokens) | | BITBUCKET_LOG_LEVEL | Log level for stderr output: DEBUG, INFO, WARNING, ERROR (default: INFO) |
This server runs locally via stdio rather than as a hosted HTTP service. Running locally keeps your Bitbucket access token on your own machine, avoids exposing an authenticated API endpoint over the network, and removes the need to manage server infrastructure or TLS certificates.
Add to ~/.claude.json or project .claude/settings.json:
<details> <summary>With uv</summary>
{
"mcpServers": {
"bitbucket": {
"command": "uv",
"args": ["run", "--directory", "/path/to/bitbucket-mcp", "bitbucket-mcp"],
"env": {
"BITBUCKET_URL": "https://bitbucket.yourcompany.com",
"BITBUCKET_TOKEN": "your-token-here"
}
}
}
}</details>
<details> <summary>With Docker</summary>
{
"mcpServers": {
"bitbucket": {
"command": "docker",
"args": ["run", "--rm", "-i", "-e", "BITBUCKET_URL", "-e", "BITBUCKET_TOKEN", "bitbucket-mcp"],
"env": {
Loading reviews...