Bitbucket CLI
Bitbucket CLI includes a separate read-only MCP mode, where an agent inspects one pinned context without repository-write tools.
- 257 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The CLI can modify repositories and pull requests with account permissions; separate MCP mode is read-only.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add cli/bitbucket-cliDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The CLI can modify repositories and pull requests with account permissions; separate MCP mode is read-only.
This is third-party code. Review the repository files before installing.
What it does
Bitbucket CLI uses bkt for Cloud and Data Center repositories and pull requests. Users select a server and project context, inspect data and prepare changes. Scripts and agent tools read JSON or YAML output. Normal CLI commands inherit the connected account’s permissions. Personal sign-in and resource tokens support different operations. The distribution includes a version-matched agent skill and a separate read-only MCP mode.
Who it is for. Bitbucket Cloud and Data Center developers reviewing repositories and pull requests through one CLI.
Good fit when
- A developer retrieves their pull requests as structured data.
- A team works with Cloud and Data Center and switches contexts explicitly.
- CI prepares a pull request for an approved branch.
- An agent reads Bitbucket through a separate MCP connection that needs no writes.
Not a fit when
- Cloud access relies on a legacy app password.
- A write is planned without checking the active server context.
- A resource token is expected to support user-identity-dependent features.
Example request
Verify the active Bitbucket context and list my pull requests without sending branch changes or comments.Limitations
Cloud uses browser OAuth or a scoped Bitbucket API token; generic Atlassian tokens for other products are unsuitable. Tokens normally use the operating system keychain, while containers need explicitly configured access. Context selects host and project, so a Git remote must match that host. Repository or workspace tokens lack user identity and cannot replace personal authentication for every command.
How to disable. Remove any skill and MCP connection, then uninstall the CLI. Revoke unused tokens and review contexts separately.
FAQ
What is the installed command?
`bkt`, unrelated to the Rust subprocess-caching tool with the same name.
How do I inspect authentication?
Run `bkt auth status` and check host and token lifetime.
Is browser sign-in supported?
Yes. Cloud recommends `bkt auth login https://bitbucket.org --kind cloud --web`.
Why can mine fail with a resource token?
It needs user identity. Use appropriate user OAuth or API-token authentication.
Can MCP mode write?
No. `bkt mcp serve` exposes read-only tools for one pinned context.
Discussion
No questions or reviews yet.
Related
CLI toolsA CLI and MCP server that search package and repository source, read exact files and return examples with cited sources.
clihub turns any MCP server into a ready CLI: each tool becomes a subcommand and the result is one static binary with no runtime dependencies
A public remote MCP on GitVerse with no keys: searches functions, classes and events right in the 1C-Bitrix source and Bitrix Framework docs
Bitrix AI plugin for GitHub Copilot
Bitrix AI
A GitHub Copilot plugin with PHP and Bitrix coding conventions, template reformatting commands, and Bitrix24's official developer MCP server wired in
An MCP server for GitLab and self-hosted instances: projects, merge requests, issues, pipelines, wiki and releases
An MCP server in one binary: AI reads and edits files across several projects and runs your commands
README in short
Release archives include a version-matched skill. Checksums and build attestations support binary verification.