Bitbucket MCP server

Read from the package source without running it. The installed server may list more.

• add_default_reviewer

  Adds a specified user to the repository's list of default reviewers for pull requests. This operation is idempotent — adding a user who is already a default reviewer has no effect.

• add_deploy_keywrite action

  Adds a new SSH deploy key to a repository, granting read or write access without requiring user credentials. Note that deploy keys authenticated via an OAuth consumer will be invalidated if that consumer is modified.

• approve_commit

  Approves a specific commit as the authenticated user, recording their explicit approval. Requires the user to have direct access to the repository, as public visibility alone does not grant approval permissions.

• bulk_create_annotationswrite action

  Bulk create or update up to 100 annotations for a specific commit report in a repository. Annotations represent individual findings (e.g., vulnerabilities, bugs, code smells) and can be optionally linked to a specific file and line number.

• create_branch_restrictionwrite action

  Creates a new branch restriction rule for a repository, controlling actions such as pushing, merging, or deleting branches based on matching patterns or branching model types.

• create_commit_build_statuswrite action

  Creates or overwrites a build status for a specific commit in a repository, allowing CI/CD systems to report build results. Optionally associate the status with a pull request by specifying the source branch via the refname field.

• create_commit_commentwrite action

  Posts a new comment on a specific commit in a repository. Supports threaded replies by referencing a parent comment ID in the request body.

• create_environmentwrite action

  Creates a new deployment environment (e.g., production, staging, test) within a specified repository. Environments are used to manage deployment configurations and variables.

• create_environment_variablewrite action

  Creates a new variable scoped to a specific deployment environment in a repository. Use this to define environment-level configuration or secrets for deployment pipelines.

• create_or_update_commit_reportwrite action

  Creates or updates a Code Insights report for a specific commit in a repository. Use a unique report ID per commit, optionally prefixed with your system name to avoid collisions.

• create_repositorywrite action

  Creates a new repository in the specified workspace. Optionally assigns the repository to a project by providing a project key or UUID in the request body.

• create_repository_runnerwrite action

  Creates a new runner for a specific repository in Bitbucket Pipelines, enabling custom build infrastructure to be registered and used for pipeline executions within that repository.

• delete_branch_restrictionwrite action

  Permanently deletes an existing branch restriction rule from a repository. This action cannot be undone and will immediately remove the associated access or push controls.

• delete_commit_annotationwrite action

  Deletes a single annotation from a specific commit report in a repository. The annotation is identified by its unique ID within the specified report.

• delete_commit_commentwrite action

  Deletes a specific comment on a commit in a repository. If the comment has visible replies, it will be soft-deleted — its content is blanked and marked as deleted — to preserve the integrity of the comment thread.

• delete_commit_propertywrite action

  Deletes a specific application property value stored against a commit in a Bitbucket repository. This permanently removes the key-value metadata associated with the given Connect app and property name.

• delete_commit_reportwrite action

  Deletes a single code insights report associated with a specific commit in a repository. The report is identified by its unique report ID.

• delete_deploy_keywrite action

  Permanently removes a deploy key from a repository, revoking its access. This action cannot be undone.

• delete_download_artifactwrite action

  Permanently deletes a specific download artifact file from a repository. This action cannot be undone and removes the file from the repository's public downloads section.

• delete_environmentwrite action

  Permanently deletes a deployment environment from a repository. This action cannot be undone and will remove all associated environment configuration.

• delete_environment_variablewrite action

  Permanently deletes a specific variable from a deployment environment in a repository. This removes the variable and its value from the environment's configuration.

• delete_pipeline_cachewrite action

  Deletes a specific pipeline cache from a repository, freeing up cached resources associated with the given cache UUID.

• delete_pipeline_cacheswrite action

  Delete all cached versions for a specific pipeline cache by name in a repository. This removes the named cache entries from the repository's pipelines configuration.

• delete_repositorywrite action

  Permanently deletes the specified repository from a workspace. This action is irreversible and does not affect any existing forks of the repository.

• delete_repository_runnerwrite action

  Permanently removes a specific runner from a repository's Pipelines configuration. The runner is identified by its UUID and will no longer be available for pipeline jobs in that repository.

• delete_repository_webhookwrite action

  Permanently removes a specific webhook subscription from a repository, stopping all future event deliveries to the configured endpoint.

• delete_user_repository_permissionwrite action

  Deletes an explicit user-level permission for a specific repository, removing any custom access grant assigned to that user. Requires admin permission on the repository and authentication via app passwords.

• fork_repositorywrite action

  Creates a new fork of the specified repository into a target workspace, optionally overriding properties such as name, description, visibility, and issue tracker settings. The fork inherits most parent properties by default, but scm, parent, and full_name cannot be changed.

• get_branch_restriction

  Retrieves a specific branch restriction rule for a repository by its unique ID. Use this to inspect the configuration of an individual branch protection or access control rule.

• get_branching_model

  Retrieves the active branching model for a repository, including the development branch, optional production branch, and all enabled branch types. This is a read-only view; use the branching model settings endpoint to modify the configuration.

• get_branching_model_settings

  Retrieves the raw branching model configuration for a repository, including development and production branch settings, branch type definitions, and default branch deletion behavior. Use the active branching model endpoint instead if you need to see the configuration resolved against actual current branches.

• get_commit

  Retrieves details for a specific commit in a repository using its SHA1 identifier. Returns commit metadata including author, timestamp, and associated changes.

• get_commit_build_status

  Retrieves a specific build status for a given commit using its unique key. Useful for checking the CI/CD pipeline result associated with a particular commit in a repository.

• get_commit_comment

  Retrieves a specific comment on a commit by its comment ID. Returns the full comment details including content, author, and timestamps.

• get_commit_property

  Retrieves a specific application property value stored against a commit in a Bitbucket repository. Useful for reading custom metadata attached to a commit by a Connect app.

• get_commit_report

  Retrieves a single code insight report for a specific commit in a repository. Returns the full report details matching the provided report ID.

• get_commit_report_annotation

  Retrieves a single annotation by its ID from a specific code insight report on a given commit. Useful for inspecting individual findings or diagnostics attached to a commit report.

• get_default_reviewer

  Retrieves a specific default reviewer for a repository, confirming they are on the default reviewers list. A 404 response indicates the specified user is not a default reviewer for the repository.

• get_deploy_keywrite action

  Retrieves a specific deploy key associated with a repository, identified by its unique key ID. Useful for inspecting deploy key details such as label, public key value, and permissions.

• get_deployment

  Retrieves detailed information about a specific deployment in a repository. Use this to inspect the status, configuration, and metadata of a single deployment by its unique identifier.

• get_diffstat

  Retrieves file-level change statistics for a commit or commit range, returning a record per modified path with the type of change and lines added or removed. Supports single-commit diffs against the first parent, two-commit diffs, and three-dot topic branch diffs.

• get_download_artifact

  Retrieves the actual file contents of a download artifact from a repository, redirecting to the file's direct download URL. Returns the raw file data rather than artifact metadata.

• get_effective_branching_model

  Retrieves the effective (currently applied) branching model for a repository, reflecting any inherited workspace-level settings combined with repository-specific overrides.

• get_environment

  Retrieves the details of a specific deployment environment within a repository. Use this to inspect environment configuration, status, and metadata by its unique identifier.

• get_merge_base

  Finds the best common ancestor commit between two commits in a repository, useful for determining the divergence point of branches or commits. If multiple best common ancestors exist, one is returned arbitrarily.

• get_pipeline

  Retrieves the details of a specific pipeline run within a repository, including its status, steps, and configuration.

• get_pipeline_cache_content_uri

  Retrieves the download URI for the content of a specific pipeline cache in a repository. Use this URI to access or download the cached build artifacts.

• get_repository

  Retrieves detailed metadata for a specific repository within a workspace. Returns the full repository object including settings, links, and configuration.

• get_repository_diff

  Retrieves a raw git-style diff for a repository, either for a single commit against its first parent or between two commits using dot notation. Supports three-dot topic diffs, file path filtering, and whitespace/rename/binary options.

• get_repository_group_permission

  Retrieves the explicit permission level assigned to a specific group for a given repository. Requires admin permission on the repository; returns one of: admin, write, read, or none.

• get_repository_override_settings

  Retrieves the inheritance state for a repository's settings, indicating which settings are overridden at the repository level versus inherited from the workspace.

• get_repository_patchwrite action

  Retrieves a raw patch for a single commit (diffed against its first parent) or a patch series for a two-commit range, including commit headers such as author and message. Unlike diffs, patches carry full commit metadata and are returned as plain text in the repository's native encoding.

• get_repository_runner

  Retrieves details of a specific Pipelines runner configured for a repository, identified by its UUID.

• get_repository_webhook

  Retrieves the details of a specific webhook installed on a repository, identified by its unique ID. Use this to inspect webhook configuration, events, and status for a given repository.

• get_user_repository_permission

  Retrieves the explicit permission level assigned to a specific user for a given repository. Requires admin permission on the repository; returns one of: admin, write, read, or none.

• list_branch_restrictions

  Retrieves a paginated list of all branch restrictions configured for a repository. Optionally filter results by restriction kind or branch name pattern.

• list_commit_comments

  Retrieves all comments (both global and inline) for a specific commit in a repository. Results are sorted oldest to newest by default and can be filtered or reordered using query parameters.

• list_commit_pull_requests

  Retrieves a paginated list of all pull requests that include a specific commit as part of their review. Requires the Pull Request Commit Links app to be installed on the repository.

• list_commit_report_annotations

  Retrieves a paginated list of annotations associated with a specific code insights report for a given commit in a repository.

• list_commit_reports

  Retrieves a paginated list of code insight reports linked to a specific commit in a repository. Useful for reviewing quality, security, or test results associated with a given commit.

• list_commit_statuses

  Retrieves all statuses (such as CI/CD build results) associated with a specific commit in a Bitbucket repository. Supports filtering by ref name, query string, and custom sorting.

• list_commits

  Retrieves all commits for a repository in reverse chronological (topological) order, similar to `git log --all`. Supports filtering by included/excluded refs and an optional file or directory path to scope results.

• list_commits_by_revision

  Retrieves a paginated list of commits for a given branch, tag, or commit SHA in reverse chronological order, similar to `git log`. Supports filtering by additional include/exclude refs and an optional file or directory path to narrow results to commits affecting that path.

• list_commits_by_revision_postwrite action

  Retrieves the commit history for a specific revision (SHA1 or branch/tag name) in a repository, using the request body to pass include and exclude filters instead of URL parameters to avoid length limitations.

• list_commits_with_filters

  Retrieves a list of commits for a repository, accepting include and exclude branch/commit parameters in the request body to avoid URL length limitations. This is functionally identical to the GET commits endpoint but does not support creating new commits.

• list_default_reviewers

  Retrieves the list of users automatically added as reviewers on every new pull request for the specified repository. To include reviewers inherited from the parent project, use the effective-default-reviewers endpoint instead.

• list_deploy_keyswrite action

  Retrieves all deploy keys associated with a specific repository in a workspace. Deploy keys provide read or read/write access to a repository without requiring user credentials.

• list_deployments

  Retrieves a list of all deployments for a specified repository. Returns deployment history and status information for the given workspace and repository.

• list_download_artifacts

  Retrieves all download artifacts associated with a specific repository in a workspace. Returns a list of available download links for the repository.

• list_effective_default_reviewers

  Retrieves the effective default reviewers for a repository, combining reviewers defined at the repository level with those inherited from its parent project. These users are automatically added as reviewers on every new pull request created in the repository.

• list_environment_variables

  Retrieves all deployment variables configured for a specific environment in a repository. Returns environment-level variables used during deployments.

• list_environments

  Retrieves all deployment environments configured for a specified repository within a workspace. Useful for inspecting available environments such as production, staging, or test.

• list_file_history

  Retrieves a paginated list of commits that modified a specific file in a repository, returned in reverse chronological order. Supports rename tracking, filtering, and sorting to precisely scope the results.

• list_pipeline_caches

  Retrieves all pipeline caches configured for a repository, providing visibility into cached dependencies and build artifacts used to speed up pipeline runs.

• list_pipelines
• list_repository_forks

  Retrieves a paginated list of all forks for a specified repository in a given workspace. Results can be filtered by the authenticated user's role, a query string, and sorted by a specified field.

• list_repository_group_permissions

  Retrieves a paginated list of explicit group permissions configured for a specific repository. Only explicitly set group permissions are returned; inherited or default permissions are not included.

• list_repository_runners

  Retrieve all pipeline runners configured for a specific repository. Runners are used to execute Bitbucket Pipelines builds within the given workspace and repository.

• list_repository_user_permissions

  Retrieves a paginated list of explicit user-level permissions configured for a specific repository. Only directly assigned user permissions are returned; inherited or group-based permissions are not included.

• list_repository_webhooks

  Retrieves a paginated list of all webhooks installed on a specific repository. Useful for auditing or managing event-driven integrations configured for the repo.

• list_webhook_event_types

  Retrieves all webhook resource and subject types on which webhooks can be registered. Each returned type includes an events link for browsing the paginated list of specific events that subject type can emit. No authentication required.

• list_webhook_event_types_by_subject

  Retrieves a paginated list of all valid webhook event types available for subscription on a given subject type (repository or workspace). This is public data requiring no authentication or scopes.

• list_workspace_repositories

  Retrieves a paginated list of all repositories within a specified workspace. Results can be filtered by the authenticated user's role and further narrowed using query and sort parameters.

• remove_default_reviewerwrite action

  Removes a specified user from the default reviewers list for a repository. After removal, the user will no longer be automatically added as a reviewer on new pull requests.

• set_repository_override_settings

  Configures the inheritance state for a repository's settings, determining which settings are overridden at the repository level versus inherited from the workspace.

• trigger_pipelinewrite action

  Creates and initiates a pipeline run for a repository, supporting multiple trigger modes including branch-based, commit-specific, custom selector, pull request, and variable-injected pipelines as defined in the repository's bitbucket-pipelines.yml file.

• unapprove_commitwrite action

  Removes the authenticated user's approval from a specified commit in a repository. This action requires explicit access to the repository; public visibility alone does not grant approval or unapproval rights.

• update_branch_restrictionwrite action

  Updates an existing branch restriction rule for a repository. Only fields included in the request body are modified; omitted fields retain their current values.

• update_branching_model_settingswrite action

  Updates the branching model configuration for a repository, including development branch, production branch, branch type prefixes, and default branch deletion behavior. Only properties explicitly passed in the request body will be modified; omitted properties remain unchanged.

• update_commit_build_statuswrite action

  Updates an existing build status entry for a specific commit in a repository. Allows modification of state, name, description, URL, and ref name, while the unique key remains immutable.

• update_commit_commentwrite action

  Updates the text content of an existing comment on a specific commit. Only the comment's content can be modified; other properties remain unchanged.

• update_commit_propertywrite action

  Update the value of an application property stored against a specific commit in a repository. Application properties allow Connect apps to associate custom metadata with Bitbucket resources.

• update_deploy_keywrite action

  Updates an existing deploy key in a repository, allowing the label and comment to be changed while keeping the same public key value.

• update_environmentwrite action

  Apply configuration changes to a specific deployment environment in a repository. Use this to modify environment settings such as variables or deployment rules.

• update_environment_variablewrite action

  Updates an existing deployment environment level variable for a specific environment in a repository. Use this to modify the key, value, or secured status of a previously created variable.

• update_repositorywrite action

  Updates an existing repository's settings and metadata within a workspace, or creates one if it does not exist. Renaming the repository will change its URL slug and return the new location in the response's Location header if no slug conflict occurs.

• update_repository_runnerwrite action

  Updates the configuration of a specific runner associated with a repository. Identifies the target runner by its UUID within the given workspace and repository.

• update_repository_webhookwrite action

  Updates an existing webhook subscription on a repository, allowing mutation of its description, URL, secret, active status, and events. The secret field controls HMAC signature generation for the X-Hub-Signature header; omit it to leave unchanged, or pass null to remove it.

• upload_download_artifactwrite action

  Upload one or more download artifacts to a repository using a multipart/form-data POST request. If a file with the same name already exists, it will be replaced.

• upsert_commit_report_annotationwrite action

  Creates or updates a single annotation on a specific commit report, representing an individual finding such as a vulnerability, bug, or code smell, optionally linked to a file and line number.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

100

the typical server has 7

Tools that change things

46%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

153

more than 71% of 12,191 servers with a package

Bitbucket: common questions

Is Bitbucket MCP server safe?

Mostly: it is graded B (80/100). Read the Bitbucket safety report

How do I install Bitbucket?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Bitbucket need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Bitbucket maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.5.

How does Bitbucket compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 100 (the typical server has 7); tools that change things 46% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.