bbkt
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BITBUCKET_USERNAME | No | Your Bitbucket username. Recommended when using API Tokens. | |
| BITBUCKET_API_TOKEN | No | An Atlassian API Token. If omitted, the server will attempt to trigger an OAuth 2.0 browser flow. | |
| BITBUCKET_CLIENT_ID | No | OAuth 2.0 Client ID. Required if using OAuth instead of an API Token. | |
| BITBUCKET_CLIENT_SECRET | No | OAuth 2.0 Client Secret. Required if using OAuth instead of an API Token. | |
| BITBUCKET_DISABLED_TOOLS | No | Explicitly deny the AI agent access to specific tools (e.g., 'delete_repository,delete_branch,delete_file'). |
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
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| bitbucket_apiA | Authenticated passthrough to ANY Bitbucket Cloud REST API v2 endpoint not covered by the manage_* tools above (e.g. pipelines-config/OIDC, webhooks, branch restrictions). Prefer a typed manage_* tool when one fits; use this for the long tail instead of calling the API yourself. Reads (GET/HEAD) work by default; write methods are rejected unless BBKT_API_ALLOW_WRITE is set on the server. Supports pagination and returns the raw HTTP status + JSON body. |
| manage_commitsC | Unified tool for listing and getting commits, diffs, and diffstats |
| manage_issuesC | Unified tool for managing repository issues (list, get, create, update) |
| manage_pipelinesC | Unified tool for managing Bitbucket Pipelines (list, get, trigger, stop, list-steps, get-step-log) |
| manage_pr_commentsC | Unified tool for managing pull request comments (list, create, update, delete, resolve, unresolve) |
| manage_pull_requestsB | Unified tool covering all pull request operations (list, get, create, update, merge, approve, unapprove, decline, diff, diffstat, commits) |
| manage_refsC | Unified tool for listing, creating, and deleting branches and tags |
| manage_repositoriesC | Unified tool for listing, getting, creating, and deleting repositories |
| manage_sourceC | Unified tool for source code operations (read, list_directory, get_history, search, write, delete) |
| manage_workspacesC | Unified tool for getting and listing Bitbucket workspaces |
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 10 tools
Each manage_* tool targets a distinct Bitbucket resource (commits, issues, pipelines, etc.) with clear operation lists, and the catch-all bitbucket_api handles everything else, ensuring no overlap.
All manage_* tools follow a consistent verb_noun pattern, but the bitbucket_api tool breaks that pattern, causing a minor inconsistency.
With 10 tools covering workspaces, repos, issues, PRs, comments, commits, pipelines, source, and refs, the count is well-scoped for a Bitbucket integration server.
The tool set provides CRUD or lifecycle operations for all major Bitbucket resources, and the bitbucket_api tool covers any remaining endpoints, leaving no obvious gaps.