bitbucket-mcp-server
A Model Context Protocol (MCP) server that provides tools for interacting with Bitbucket repositories, pull requests, issues, and more.
README
Bitbucket MCP Server
<img src="./images/logo.jpg" alt="Bitbucket MCP Logo" width="640" height="320">
A Model Context Protocol (MCP) server that provides tools for interacting with Bitbucket repositories, pull requests, issues, and more.
Safety
This server is read-heavy and non-destructive — no DELETE operations are used against the Bitbucket API, so there is no risk of accidental data loss. Write operations are limited to creating and updating resources (e.g., pull requests, comments, pipelines).
Quick Start
Using NPX (Recommended)
Run directly without cloning the repository:
BITBUCKET_USERNAME="your-email@example.com" \
BITBUCKET_API_TOKEN="your-api-token" \
npx -y -p bitbucket-mcp-server@latest bitbucket-mcp
The
-p ... bitbucket-mcpflag tellsnpxwhich bin to run. The package ships two binaries —bitbucket-mcp(the MCP server) andbb(the CLI) — so the bin name must be specified explicitly.
From Source
-
Install and Build:
npm install npm run build -
Configure Environment: Set the required variables (see Configuration):
export BITBUCKET_API_TOKEN="your-api-token" export BITBUCKET_USERNAME="your-email@example.com" -
Run the Server:
npm start
CLI
This package also ships a bb CLI alongside the MCP server. After installing globally:
npm install -g bitbucket-mcp-server
bb --help
The CLI shares the same core logic as the MCP server, providing terminal access to repositories, pull requests, issues, pipelines, and more. See docs/cli.md for the full reference, including authentication, output formats, exit codes, and command-by-command examples.
Quick example—list open PRs in JSON:
BITBUCKET_WORKSPACE=acme bb --json pr list -r api --state OPEN
Features
This MCP server provides comprehensive tools for Bitbucket integration:
- Repository Management: List and inspect repositories in a workspace.
- Pull Requests: Full lifecycle support—list, get details, create, update, diff, and comment.
- Issues: Query and filter repository issues.
- Source Code: Explore branches and commits.
- Pipelines: List, get, and trigger Bitbucket pipelines for CI/CD.
- System & Search: Cross-resource search and health monitoring.
For a full list of available tools and their parameters, see the Tool Reference.
Available Tools
Repository & code
repositories— List repositories in a workspace, or fetch details for a single repository whenrepo_slugis provided.commits— List recent commits, or fetch a single commit whencommit_hashis provided.list-branches— List branches for a repository.search— Full-text search across a repository.
Pull requests
pull-requests— List PRs, or fetch a single PR whenpr_idis provided.create-pull-request— Create a new pull request.update-pr-description— Update an existing PR's description.get-pr-diff— Fetch the diff for a PR.
PR comments
pr-comments— List PR comments, or fetch a single comment whencomment_idis provided.create-pr-comment— Add a comment (or inline comment, or reply) to a PR.
Issues
list-issues— List issues for a repository.
Pipelines
pipelines— List pipelines, or fetch a single pipeline whenpipeline_uuidis provided.trigger-pipeline— Trigger a new pipeline run.pipeline-steps— Pipeline step operations. Useaction: "list" | "get" | "log"to select behavior;step_uuidis required forgetandlog.
System
health-check— Server health status.get-metrics— Request metrics.
Migrating from v1.x to v2.0
v2.0 consolidates 24 tools into 16. Update tool names and parameters as follows:
| Old (v1.x) | New (v2.0) | Parameter changes |
|---|---|---|
list-repositories |
repositories |
Same parameters; repo_slug optional |
get-repository |
repositories |
Pass repo_slug |
list-pull-requests |
pull-requests |
Same parameters; pr_id optional |
get-pull-request |
pull-requests |
Pass pr_id (previously pull_request_id — rename) |
list-pr-comments |
pr-comments |
pull_request_id → pr_id (matches pull-requests); comment_id optional |
get-pr-comment |
pr-comments |
pull_request_id → pr_id; pass comment_id |
get-commits |
commits |
Same parameters; commit_hash optional |
get-commit |
commits |
Pass commit_hash |
list-pipelines |
pipelines |
Same parameters; pipeline_uuid optional |
get-pipeline |
pipelines |
Pass pipeline_uuid |
list-pipeline-steps |
pipeline-steps |
Add action: "list" |
get-pipeline-step |
pipeline-steps |
Add action: "get" |
get-pipeline-step-log |
pipeline-steps |
Add action: "log" |
All other tools retain their v1.x names and parameters.
Installation
- Clone or download this repository.
- Install dependencies:
npm install - Build the project:
npm run build
Configuration
The server is configured via environment variables. For detailed setup instructions and client-specific examples (Claude Desktop, etc.), please refer to the Configuration Guide.
Essential Variables
| Variable | Description |
|---|---|
BITBUCKET_API_TOKEN |
(Required) Your User API token or Workspace/Project token |
BITBUCKET_USERNAME |
(Required for User API tokens) Your Atlassian account email |
BITBUCKET_WORKSPACE |
Default workspace used when the parameter is omitted |
Note: If you are using a Workspace or Project access token, you can omit
BITBUCKET_USERNAME.
Advanced Settings
Additional configuration options for timeouts, caching, metrics, and retries are documented in CONFIGURATION.md.
MCP Client Configuration
Add this server to your MCP client configuration (e.g., claude_desktop_config.json). See CONFIGURATION.md for full examples for macOS, Linux, and Windows.
Using NPX (recommended):
{
"mcpServers": {
"bitbucket-mcp": {
"command": "npx",
"args": ["-y", "-p", "bitbucket-mcp-server@latest", "bitbucket-mcp"],
"env": {
"BITBUCKET_USERNAME": "your-email@example.com",
"BITBUCKET_API_TOKEN": "your-api-token",
"BITBUCKET_WORKSPACE": "your-workspace"
}
}
}
}
Using local build:
{
"mcpServers": {
"bitbucket-mcp": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/bitbucket_mcp/build/index.js"],
"env": {
"BITBUCKET_USERNAME": "your-email@example.com",
"BITBUCKET_API_TOKEN": "your-api-token",
"BITBUCKET_WORKSPACE": "your-workspace"
}
}
}
}
Usage Examples
List Repositories
List all repositories in the 'myworkspace' workspace
Create Pull Request
Create a pull request from feature/my-feature to main in myworkspace/myrepo with title "My Feature PR"
Search Workspace
Search for "authentication" across all repositories and pull requests
See more examples for PRs, issues, and commits in the Tool Reference.
Prerequisites
- Node.js 20.19.x or >= 22.12.0
- npm (included with Node.js)
Development
- Build:
npm run build - Dev Mode:
npm run dev - Test:
npm test - Coverage:
npm run test:coverage
Troubleshooting
Refer to the Troubleshooting section in CONFIGURATION.md for common issues related to authentication, permissions, and rate limiting.
License
ISC
Contributing
Contributions are welcome! Please feel free to submit issues and pull requests.
Links
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。