Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via
Node.js/TypeScript MCP server for Atlassian Bitbucket. Enables AI systems (LLMs) to interact with workspaces, repositories, and pull requests via tools (list, get
Transform how you work with Bitbucket by connecting Claude, Cursor AI, and other AI assistants directly to your repositories, pull requests, and code. Get instant insights, automate code reviews, and streamline your development workflow.
The server publishes 6 tools. What each one is for:
bb_get — GET any Bitbucket API endpoint (read data)bb_post — POST to any endpoint (create resources)bb_put — PUT to any endpoint (replace resources)bb_patch — PATCH any endpoint (partial updates)bb_delete — DELETE any endpoint (remove resources)bb_clone — Clone a repository locallyConfiguration is passed through the environment: ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN, ATLASSIAN_BITBUCKET_USERNAME, ATLASSIAN_BITBUCKET_APP_PASSWORD, BITBUCKET_DEFAULT_WORKSPACE, DEBUG. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
@aashari/mcp-server-atlassian-bitbucket on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. MCP's toolset — bb_get, bb_post, bb_put and 3 more — is a fair guide to whether it matches your workflow. It is maintained by GitHub Actions; worth a glance at recent repository activity before you build anything load-bearing on it.
bb_get — GET any Bitbucket API endpoint (read data)bb_post — POST to any endpoint (create resources)bb_put — PUT to any endpoint (replace resources)bb_patch — PATCH any endpoint (partial updates)bb_delete — DELETE any endpoint (remove resources)bb_clone — Clone a repository locallyCompare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| bb_get | GET any Bitbucket API endpoint (read data) |
| bb_post | POST to any endpoint (create resources) |
| bb_put | PUT to any endpoint (replace resources) |
| bb_patch | PATCH any endpoint (partial updates) |
| bb_delete | DELETE any endpoint (remove resources) |
| bb_clone | Clone a repository locally |
{
"mcpServers": {
"atlassian-bitbucket-1": {
"command": "npx",
"args": ["-y", "@aashari/mcp-server-atlassian-bitbucket"],
"env": {
"ATLASSIAN_USER_EMAIL": "your-value",
"ATLASSIAN_API_TOKEN": "your-value",
"ATLASSIAN_BITBUCKET_USERNAME": "your-value",
"ATLASSIAN_BITBUCKET_APP_PASSWORD": "your-value",
"BITBUCKET_DEFAULT_WORKSPACE": "your-value",
"DEBUG": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| ATLASSIAN_USER_EMAIL | Configuration value read at startup. | Optional |
| ATLASSIAN_API_TOKEN | Credential the server authenticates with. | Yes |
| ATLASSIAN_BITBUCKET_USERNAME | Configuration value read at startup. | Optional |
| ATLASSIAN_BITBUCKET_APP_PASSWORD | Configuration value read at startup. | Optional |
| BITBUCKET_DEFAULT_WORKSPACE | Configuration value read at startup. | Optional |
| DEBUG | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.