Skip to main content
Glama
mohitgoel188

MCP Bitbucket

by mohitgoel188

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BITBUCKET_TOKENNoScoped API token or repository access token. Preferred auth mode. No username needed. A token wins when both auth modes are configured.
BITBUCKET_USERNAMENoUsername for legacy app password auth. Must be paired with BITBUCKET_APP_PASSWORD.
BITBUCKET_REPO_SLUGNoBitbucket repository slug. Optional inside a Bitbucket checkout (auto-detected from git remote), required otherwise.
BITBUCKET_WORKSPACENoBitbucket workspace. Optional inside a Bitbucket checkout (auto-detected from git remote), required otherwise. There is no built-in default.
BITBUCKET_PROJECT_DIRNoPoint auto-detection at a directory other than the process cwd.
BITBUCKET_APP_PASSWORDNoApp password for legacy auth. Must be paired with BITBUCKET_USERNAME.
BITBUCKET_REQUEST_LOG_FILENoWhere to write request logs. Default: ./bitbucket_requests.log, relative to the cwd../bitbucket_requests.log
BITBUCKET_ALLOW_DESTRUCTIVENoRegister bb_delete_repository at all. Default 'false'.false
BITBUCKET_BB_REQUEST_READONLYNoAllow non-GET requests through bb_request. Default 'true' (reads only). Set to 'false' to allow any write endpoint.true
BITBUCKET_ENABLE_REQUEST_LOGGINGNoLog every request as a runnable curl command. Default 'false'.false

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
bb_create_repositoryB

Create a new repository in Bitbucket

bb_search_repositoriesA

Search repositories using Bitbucket's query syntax: name (name ~ "pattern"), project key (project.key = "PROJ"), language (language = "python"), or dates (updated_on >= "2024-01-19", ISO 8601 only). To search file contents instead, use bb_list_endpoints for the code-search endpoints.

bb_create_branchB

Create a new branch in a Bitbucket repository

bb_read_fileB

Read a file from a Bitbucket repository

bb_write_fileA

Write or update a file in a Bitbucket repository

bb_delete_fileB

Delete a file from a Bitbucket repository

bb_create_issueC

Create an issue in a Bitbucket repository

bb_delete_issueB

Delete an issue from a Bitbucket repository

bb_create_pull_requestB

Create a new pull request in a Bitbucket repository

bb_get_pull_requestB

Get details of a pull request in a Bitbucket repository

bb_get_pr_diffstatA

Get the diffstat for a pull request: every modified file with its added/removed line counts and a totals summary

bb_get_pr_file_contentA

Get one file's content at both the source and destination branches of a pull request, for side-by-side review

bb_get_pr_file_diffA

Get the line-by-line diff for one specific file in a pull request

bb_get_pr_all_file_diffsA

Get the complete diff for every modified file in a pull request in a single call - much more efficient than calling bb_get_pr_file_diff per file

bb_list_pull_requestsA

List pull requests in a repository, optionally filtered by state, source or destination branch, or author. Use the source_branch filter to resolve a branch name to its PR number when the user names a branch instead of a PR.

bb_pr_list_commentsA

List comments on a pull request, showing which are inline (with file and line), which are replies, and which threads are resolved

bb_pr_commentA

Add a comment to a pull request. Pass file_path and line together to anchor it inline on that line of the diff; pass parent_id to reply within an existing thread; pass neither for a general PR comment.

bb_pr_resolve_threadA

Mark a pull request comment thread as resolved

bb_pr_approveA

Approve a pull request as the authenticated user. This is visible to the team - only call it when the user has asked for an approval.

bb_pr_request_changesA

Request changes on a pull request as the authenticated user. Visible to the team - only call it when the user has asked to request changes.

bb_list_endpointsA

Search the full Bitbucket Cloud REST API (all endpoints, generated from Atlassian's official OpenAPI spec) to find the right method, path and params for a task. Call this FIRST whenever no purpose-built bb_* tool covers what you need, then pass the result to bb_request. Every whitespace-separated term in search must match, so 'pull request comment' narrows better than 'comment'.

bb_requestA

Call ANY Bitbucket Cloud 2.0 REST endpoint directly. This is the escape hatch for everything the purpose-built bb_* tools do not wrap - merges, commit comparison, branches and tags, pipelines, code search, webhooks, permissions. Use bb_list_endpoints first to get the exact path and params. Paths are relative to https://api.bitbucket.org/2.0 and must have real values substituted for {placeholders}. Set paginate=true on list endpoints to follow Bitbucket's next links and merge all pages.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mohitgoel188/mcp-bitbucket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server