A repository listing or a pull-request payload from Bitbucket carries a great deal of structure nobody reads, and in a conversational client every byte of it competes with the work. Defaulting to a denser encoding is a real saving repeated on every call. The verb-shaped surface is the other trade: five tools cover the entire API and never go stale, at the cost of the caller needing to know the path. Keeping PUT and PATCH distinct rather than collapsing them into 'update' matters here, because a full replacement against a partial payload silently drops fields.
A verb-shaped Bitbucket client rather than an endpoint-shaped one: GET, POST, PUT, PATCH and DELETE against any Bitbucket resource, with a repository clone alongside.
- Five tools mapped to HTTP verbs, so any Bitbucket API resource is reachable without a wrapper per endpoint.
- Responses default to TOON, a compact format the tools state uses substantially fewer tokens than JSON for the same data.
- bb_put and bb_patch are separate, matching the API's own distinction between a full replacement and a partial update.
- bb_clone clones a repository to the local filesystem, preferring SSH.
Bitbucket credentials, and SSH configured if you want the clone to use it.
One command plus a key — npm install -g @aashari/mcp-server-atlassian-bitbucket, then supply credentials