Model Context Protocol (MCP) server for Bitbucket Cloud and Server API integration
Bitbucket MCP server is a locally run integration for AI assistants that speak the Model Context Protocol. Model Context Protocol (MCP) server for Bitbucket Cloud and Server API integration.
A Model Context Protocol (MCP) server for integrating with Bitbucket Cloud and Server APIs. This MCP server enables AI assistants like Cursor to interact with your Bitbucket repositories, pull requests, and other resources.
Checkout out the official npm package This server implements the Model Context Protocol standard to provide AI assistants with access to Bitbucket data and operations. It includes tools for:
Once Bitbucket is connected, these are the calls the assistant has available:
Pagination — Unless noted otherwise, listing tools accept the following optional parameters:listRepositories — The listRepositories tool exposed by this servergetRepository — The getRepository tool exposed by this servergetPullRequests — The getPullRequests tool exposed by this servercreatePullRequest — The createPullRequest tool exposed by this servergetPullRequest — The getPullRequest tool exposed by this serverupdatePullRequest — The updatePullRequest tool exposed by this servergetPullRequestActivity — The getPullRequestActivity tool exposed by this serverapprovePullRequest — The approvePullRequest tool exposed by this serverunapprovePullRequest — The unapprovePullRequest tool exposed by this serverdeclinePullRequest — The declinePullRequest tool exposed by this servermergePullRequest — The mergePullRequest tool exposed by this serverYou will need 5 environment variables: BITBUCKET_URL, BITBUCKET_WORKSPACE, BITBUCKET_USERNAME, BITBUCKET_PASSWORD, BITBUCKET_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
bitbucket-mcp on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Bitbucket's toolset — Pagination, listRepositories, getRepository and 11 more — is a fair guide to whether it matches your workflow. It is maintained by yeminimatan; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| Pagination | Unless noted otherwise, listing tools accept the following optional parameters: |
| listRepositories | The listRepositories tool exposed by this server. |
| getRepository | The getRepository tool exposed by this server. |
| getPullRequests | The getPullRequests tool exposed by this server. |
| createPullRequest | The createPullRequest tool exposed by this server. |
| getPullRequest | The getPullRequest tool exposed by this server. |
| updatePullRequest | The updatePullRequest tool exposed by this server. |
| getPullRequestActivity | The getPullRequestActivity tool exposed by this server. |
| approvePullRequest | The approvePullRequest tool exposed by this server. |
| unapprovePullRequest | The unapprovePullRequest tool exposed by this server. |
| declinePullRequest | The declinePullRequest tool exposed by this server. |
| mergePullRequest | The mergePullRequest tool exposed by this server. |
| requestChanges | The requestChanges tool exposed by this server. |
| removeChangeRequest | The removeChangeRequest tool exposed by this server. |
{
"mcpServers": {
"bitbucket-1": {
"command": "npx",
"args": ["-y", "bitbucket-mcp"],
"env": {
"BITBUCKET_URL": "your-value",
"BITBUCKET_WORKSPACE": "your-value",
"BITBUCKET_USERNAME": "your-value",
"BITBUCKET_PASSWORD": "your-value",
"BITBUCKET_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| BITBUCKET_URL | Endpoint or connection string the server talks to. | Yes |
| BITBUCKET_WORKSPACE | Configuration value read at startup. | Optional |
| BITBUCKET_USERNAME | Configuration value read at startup. | Optional |
| BITBUCKET_PASSWORD | Configuration value read at startup. | Optional |
| BITBUCKET_TOKEN | Credential the server authenticates with. | Yes |
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.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.