A Model Context Protocol (MCP) server that provides AI assistants with tools to interact with Bitbucket Cloud repositories. Built with Quarkus, the
A Model Context Protocol (MCP) server that provides AI assistants with tools to interact with Bitbucket Cloud repositories. Built with Quarkus, the Supersonic Subatomic Java Framework. That is what the personal bitbucket mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
The Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to Large Language Models (LLMs). This server implements MCP to expose Bitbucket operations as tools that AI assistants like Claude, ChatGPT, or other LLM-powered applications can use.
The server publishes 3 tools. What each one is for:
Repositories — ReadPrerequisites — 1. Bitbucket API Token: Create an API token at https://bitbucket.org/account/settings/api-token/ - Required permissions: repository:readLogs — The Logs tool exposed by this serverInstallation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Configuration is passed through the environment: BITBUCKET_API_TOKEN. 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.
repository:read, pullrequest:read, pullrequest:write - See Creating a Bitbucket API Token for detailed instructions 2. Docker (optional): For running the containerized versionPlenty of monitoring and observability 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. Personal Bitbucket's toolset — Repositories, Prerequisites, Logs — is a fair guide to whether it matches your workflow. It is maintained by tedysaputro; 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 |
|---|---|
| Repositories | Read |
| Prerequisites | 1. **Bitbucket API Token**: Create an API token at https://bitbucket.org/account/settings/api-token/ - Required permissions: repository:read, pullrequest:read, pullrequest:write - See [Creating a Bitbucket API Token](#cr |
| Logs | The Logs tool exposed by this server. |
{
"mcpServers": {
"personal-bitbucket": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"],
"env": {
"BITBUCKET_API_TOKEN": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
repository:read, pullrequest:read, pullrequest:write - See Creating a Bitbucket API Token for detailed instructions 2. Docker (optional): For running the containerized version| Variable | Description | Required |
|---|---|---|
| BITBUCKET_API_TOKEN | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.