Atlassian Bitbucket MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ATLASSIAN_API_TOKEN | No | Your scoped API token (starts with ATATT) | |
| ATLASSIAN_USER_EMAIL | No | Your Atlassian account email address | |
| BITBUCKET_DEFAULT_WORKSPACE | No | Your default workspace slug to avoid specifying it every time | |
| ATLASSIAN_BITBUCKET_USERNAME | No | Your Bitbucket username (legacy method) | |
| ATLASSIAN_BITBUCKET_APP_PASSWORD | No | Your Bitbucket app password (legacy method) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bb_getA | Read any Bitbucket data. Returns TOON format by default (30-60% fewer tokens than JSON). IMPORTANT - Cost Optimization:
Schema Discovery Pattern:
Output format: TOON (default, token-efficient) or JSON ( Common paths:
Query params: Example filters (q param): JQ examples: The |
| bb_postA | Create Bitbucket resources. Returns TOON format by default (token-efficient). IMPORTANT - Cost Optimization:
Output format: TOON (default) or JSON ( Common operations:
The |
| bb_putA | Replace Bitbucket resources (full update). Returns TOON format by default. IMPORTANT - Cost Optimization:
Output format: TOON (default) or JSON ( Common operations:
The |
| bb_patchA | Partially update Bitbucket resources. Returns TOON format by default. IMPORTANT - Cost Optimization: Use Output format: TOON (default) or JSON ( Common operations:
The |
| bb_deleteA | Delete Bitbucket resources. Returns TOON format by default. Output format: TOON (default) or JSON ( Common operations:
Note: Most DELETE endpoints return 204 No Content on success. The |
| bb_cloneA | Clone a Bitbucket repository to your local filesystem using SSH (preferred) or HTTPS. Provide |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool corresponds to a distinct HTTP method (or clone operation) with clear purposes: clone for local cloning, delete for deletions, get for reads, patch for partial updates, post for creations, and put for full replacements. There is no overlap.
All tools follow a consistent 'bb_<verb>' pattern using HTTP method names (clone, delete, get, patch, post, put). The naming is predictable and uniform.
With 6 tools, the server provides a concise CRUD+L (clone) interface for Bitbucket. This is well-scoped for a MCP server; each tool has a clear role without unnecessary bloat.
The tools cover all standard CRUD operations plus cloning. However, specific workflows like merging or approving PRs are handled via generic post/put, which may require agents to construct endpoint paths. A dedicated tool for common composite operations could improve completeness slightly.