com.mcparmory/bitbucket
OCI · GHCR.IO/MCPARMORY/BITBUCKET:1.0.5 · 2 COMPONENTS · SCANNED SEP 20
Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security0
- Malware scan not yet available for this package.Unverified
- Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 131 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 31894 tokens (~122/item across 261 items; 261 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety96
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 42 of 51 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "list_deploy_keys" implies "deploy" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 261 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the com.mcparmory/bitbucket MCP server?
com.mcparmory/bitbucket runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/bitbucket:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/mcparmory/bitbucket:1.0.5
claude mcp add com-mcparmory-bitbucket -- docker run --rm -i ghcr.io/mcparmory/bitbucket:1.0.5
{
"mcpServers": {
"com-mcparmory-bitbucket": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bitbucket:1.0.5"
]
}
}
} {
"servers": {
"com-mcparmory-bitbucket": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bitbucket:1.0.5"
]
}
}
} codex mcp add com-mcparmory-bitbucket -- docker run --rm -i ghcr.io/mcparmory/bitbucket:1.0.5
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-bitbucket": {
"type": "local",
"command": [
"docker",
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bitbucket:1.0.5"
],
"enabled": true
}
}
} mcp_servers:
com-mcparmory-bitbucket:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/mcparmory/bitbucket:1.0.5"] {
"McpServers": {
"com-mcparmory-bitbucket": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bitbucket:1.0.5"
]
}
}
} {
"mcpServers": {
"com-mcparmory-bitbucket": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/mcparmory/bitbucket:1.0.5"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 −3
- Stability: pass → 0.80 functional
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 −3
- Stability: pass → 0.80 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/bitbucket:1.0.5
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
add_default_reviewer Add Default Reviewer ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository within the workspace. |
| target_username | string | yes | The username or UUID of the user to add as a default reviewer for the repository. |
| workspace | string | yes | The workspace slug or UUID that owns the repository. |
No output schema declared.
No examples provided.
add_deploy_key Add Deploy Key ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
add_gpg_key Add GPG Key ~99
Adds a new GPG public key to the specified user account, enabling cryptographic verification of commits and other signed content. Returns the newly created GPG key object upon success.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the GPG public key to be added to the user account. |
| selected_user | string | yes | The account identifier for the target user, accepted as either an Atlassian Account ID or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
add_project_default_reviewer Add Project Default Reviewer ~133
Adds a specified user to the default reviewers list for a project in a workspace. This operation is idempotent, so adding an already-listed reviewer will not cause errors.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The unique identifier for the project, either its short key or its UUID surrounded by curly-braces. |
| selected_user | string | yes | The unique identifier for the user to add as a default reviewer, either their username or their account UUID surrounded by curly-braces. |
| workspace | string | yes | The unique identifier for the workspace, either its slug (ID) or its UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
add_ssh_key Add SSH Key ~95
Adds a new SSH public key to the specified user account. Returns the resulting SSH key object upon success.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The SSH public key payload to add to the user account, including the key type, public key string, and optional label. |
| selected_user | string | yes | The account identifier for the target user, either as an Atlassian Account ID or as an account UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
approve_commit Approve Commit ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The full SHA1 hash identifying the specific commit to approve. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository containing the commit. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace that owns the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
approve_pull_request Approve Pull Request ~106
Approves the specified pull request on behalf of the authenticated user. This records the user's approval and contributes to any required approval count for merging.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The numeric ID of the pull request to approve. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
bulk_create_annotations Bulk Create Annotations ~234
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | array | – | Array of annotation objects to create or update. Each annotation must include a unique external_id and may specify fields such as annotation_type (VULNERABILITY, CODE_SMELL, BUG), severity (CRITICAL,… |
| commit | string | yes | The full commit hash for which the report and its annotations are being uploaded. |
| repo_slug | string | yes | The repository slug or identifier within the workspace. |
| reportId | string | yes | The UUID or external ID of the report to which these annotations belong. |
| workspace | string | yes | The workspace identifier, either as a slug (e.g., my-team) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
check_snippet_watch_status Check Snippet Watch Status ~91
Checks whether the currently authenticated user is watching a specific snippet. Returns 204 if watching, 404 if not watching or if the request is made anonymously.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to check watch status for. |
| workspace | string | yes | The workspace identifier, either as a slug (human-readable short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_branch Create Branch ~92
Creates a new branch in the specified repository by providing a branch name and a target commit hash. Requires authentication with appropriate repository access.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository identifier, either as a slug (URL-friendly name) or as a UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier, either as a slug (workspace ID) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_branch_restriction Create Branch Restriction ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The branch restriction rule definition, including the restriction kind, branch matching strategy (glob pattern or branching model type), and optionally the users and groups exempt from the restrictio… |
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_commit_build_status Create Commit Build Status ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The build status payload containing fields such as key, state, description, url, and optionally refname. The key uniquely identifies the build status; if it already exists, the existing record will b… |
| commit | string | yes | The full SHA1 hash of the commit to attach the build status to. |
| repo_slug | string | yes | The repository identifier, either as a slug (e.g. my-repo) or as a UUID surrounded by curly braces. |
| workspace | string | yes | The workspace identifier, either as a slug (e.g. my-workspace) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_commit_comment Create Commit Comment ~138
Posts a new comment on a specific commit in a repository. Supports threaded replies by referencing a parent comment ID in the request body.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The comment payload, including the comment content and an optional parent comment ID to post a reply in an existing thread. |
| commit | string | yes | The full SHA1 hash of the commit to comment on. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) that identifies the repository within the workspace. |
| workspace | string | yes | The workspace ID (slug) or UUID (surrounded by curly-braces) that identifies the workspace containing the repository. |
No output schema declared.
No examples provided.
create_commit_with_files Create Commit with Files ~294
Creates a new commit in a repository by uploading, modifying, or deleting files via multipart/form-data or URL-encoded form data. Supports setting commit message, author, target branch, and file attributes such as executable or symlink.
| Name | Type | Req | Description |
|---|---|---|---|
| author | string | – | The author identity for the new commit in 'Full Name <email>' format. When omitted, the authenticated user's display name and primary email are used; anonymous commits are not permitted. |
| branch | string | – | The name of the branch on which to create the new commit. If omitted, the commit is placed on the repository's main branch. Providing a new branch name creates that branch; providing an existing bran… |
| files | string | – | One or more repository-relative file paths that this request is manipulating. Listing a path here without a corresponding file field body causes that file to be deleted; paths not referenced in this… |
| message | string | – | The commit message to associate with the new commit. When omitted, Bitbucket uses a default canned message. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) identifying the target repository. |
| workspace | string | yes | The workspace ID (slug) or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
create_environment Create Environment ~111
Creates a new deployment environment (e.g., production, staging, test) within a specified repository. Environments are used to manage deployment configurations and variables.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the environment configuration details, such as name and environment type. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace where the environment will be created. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_environment_variable Create Environment Variable ~131
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The variable definition to create, including its key, value, and whether it should be treated as secured (masked). |
| environment_uuid | string | yes | The unique identifier of the deployment environment in which the variable will be created. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_or_update_commit_report Create or Update Commit Report ~263
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The report payload containing metadata and result data. Supports fields: title, details, report_type (SECURITY, COVERAGE, TEST, BUG), reporter, link, result (PASSED, FAILED, PENDING), and a data arra… |
| commit | string | yes | The full commit hash that this report is associated with. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the target commit. |
| reportId | string | yes | A unique identifier for the report scoped to this commit — either a UUID or an external ID. To avoid collisions with other systems, prefix external IDs with your system name (e.g., mySystem-001). |
| workspace | string | yes | The workspace identifier — either the slug (short name) or the UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_pipeline_schedule Create Pipeline Schedule ~105
Creates a new pipeline schedule for the specified repository, allowing automated pipeline runs at defined intervals or times.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The schedule configuration payload defining the timing, target branch, and other schedule properties for the pipeline. |
| repo_slug | string | yes | The repository slug or identifier within the workspace for which the pipeline schedule will be created. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_pipeline_variable Create Pipeline Variable ~65
Creates a new variable at the workspace level for use across Bitbucket Pipelines. Workspace-level variables are available to all pipelines within the specified workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
create_project Create Project ~73
Creates a new project within the specified workspace, supporting optional avatar images via data-URL or external URL, privacy settings, and a unique project key.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The workspace in which to create the project, specified as either the workspace slug (human-readable ID) or the workspace UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_project_deploy_key Create Project Deploy Key ~102
Creates a new deploy key for a specified project within a workspace, enabling secure read or read/write access to the project's repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The unique key identifier assigned to the project (e.g., 'TEST_PROJECT'). This is the short key label, not the project name or UUID. |
| workspace | string | yes | The workspace identifier, either as a slug (human-readable ID) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_pull_request Create Pull Request ~146
Creates a new pull request in the specified repository, authored by the authenticated user, merging a source branch into a destination branch (defaults to the repository's main branch if not specified).
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The pull request payload including required fields such as title and source branch, plus optional fields like destination branch, reviewers list (array of user UUID objects), description, close_sourc… |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) identifying the target repository where the pull request will be created. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
create_pull_request_comment Create Pull Request Comment ~137
Creates a new comment on a specified pull request in a Bitbucket repository. Returns the newly created comment object upon success.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the comment content and any optional metadata such as inline positioning or parent comment reference. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request on which the comment will be created. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_pull_request_task Create Pull Request Task ~213
Creates a new task on a specified pull request in a Bitbucket repository. Tasks can optionally be linked to a specific comment, causing them to appear beneath that comment in the pull request view.
| Name | Type | Req | Description |
|---|---|---|---|
| comment | – | – | An optional reference to a pull request comment by its ID; when provided, the task will be displayed beneath that comment in the pull request view. |
| pending | boolean | – | Indicates whether the task should be created in a pending (incomplete) state; when omitted, the default state is applied. |
| pull_request_id | integer | yes | The numeric ID of the pull request on which the task will be created. |
| raw | string | yes | The text content of the task to be created on the pull request. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) that uniquely identifies the repository within the workspace. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) that identifies the Bitbucket workspace containing the repository. |
No output schema declared.
No examples provided.
create_repository Create Repository ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Optional request body containing repository configuration such as SCM type and project assignment. If no project is specified, the repository is automatically assigned to the oldest project in the wo… |
| repo_slug | string | yes | The slug or UUID of the repository to create. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID in which to create the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_repository_pipeline_variable Create Repository Pipeline Variable ~106
Creates a new pipeline environment variable at the repository level, making it available to all pipelines within the specified repository.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The pipeline variable object to create, including its key, value, and whether it should be secured (masked in logs). |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
create_repository_runner Create Repository Runner ~90
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or identifier within the specified workspace where the runner will be created. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_snippet Create Snippet ~50
Creates a new snippet under the authenticated user's account, supporting multiple text and binary files via multipart/form-data or multipart/related requests. Snippets can be public or private and optionally organized under a specific workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_snippet_comment Create Snippet Comment ~125
Creates a new comment on a specific snippet in a workspace. Supports threaded replies by including a parent comment ID in the request body.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The comment payload. Must include the required field `content.raw` containing the comment text. Optionally include `parent.id` to post a threaded reply to an existing comment. |
| encoded_id | string | yes | The unique identifier of the snippet to comment on. |
| workspace | string | yes | The workspace identifier, either as a slug (e.g. my-team) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_ssh_known_host Create SSH Known Host ~100
Adds a known SSH host to a repository's Pipelines configuration, enabling trusted host verification during pipeline execution.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The known host object to create, containing the hostname and its associated public key details. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_tag Create Tag ~129
Creates a new annotated tag in the specified repository, associating it with a target commit hash. An optional message may be provided; if omitted, a default message is generated automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | JSON document containing the tag name, the target commit hash, and an optional annotation message. A full commit hash is preferred over a short prefix to avoid ambiguity. |
| repo_slug | string | yes | The repository identifier, either the repository slug or the repository UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier, either the workspace slug or the workspace UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
create_workspace_runner Create Workspace Runner ~59
Creates a new runner for the specified workspace, enabling custom build infrastructure to execute Bitbucket Pipelines jobs.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The workspace identifier, either the workspace slug (human-readable short name) or the workspace UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
create_workspace_snippet Create Workspace Snippet ~74
Creates a new snippet scoped to the specified workspace. Behaves identically to the global snippet creation endpoint, but associates the snippet with the given workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The workspace in which to create the snippet, identified by either its slug (human-readable ID) or its UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
decline_pull_request Decline Pull Request ~110
Declines an open pull request in the specified repository, rejecting the proposed changes. Use this to formally close a pull request without merging.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The unique numeric ID of the pull request to decline. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_branch Delete Branch ~115
Deletes a branch from the specified repository. The main branch cannot be deleted; branch names should be provided without any prefix such as refs/heads.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the branch to delete, provided without any prefix such as refs/heads. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository; UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace; UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_branch_restriction Delete Branch Restriction ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique numeric identifier of the branch restriction rule to delete. |
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace that owns the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_commit_annotation Delete Commit Annotation ~141
Deletes a single annotation from a specific commit report in a repository. The annotation is identified by its unique ID within the specified report.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationId | string | yes | The unique identifier of the annotation to delete, either its UUID or external ID. |
| commit | string | yes | The commit hash or identifier that the target annotation belongs to. |
| repo_slug | string | yes | The repository slug or identifier within the workspace. |
| reportId | string | yes | The unique identifier of the report containing the annotation, either its UUID or external ID. |
| workspace | string | yes | The workspace identifier, either the slug (short name) or the UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
delete_commit_comment Delete Commit Comment ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the commit comment to delete. |
| commit | string | yes | The full SHA1 hash of the commit whose comment is being deleted. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_commit_property Delete Commit Property ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Bitbucket Connect app that owns the property being deleted. |
| commit | string | yes | The commit identifier (hash) whose associated application property will be deleted. |
| property_name | string | yes | The name of the application property to delete from the specified commit. |
| repo_slug | string | yes | The slug identifier of the repository from which the commit property will be deleted. |
| workspace | string | yes | The workspace containing the repository, specified as either the workspace slug or the workspace UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
delete_commit_report Delete Commit Report ~130
Deletes a single code insights report associated with a specific commit in a repository. The report is identified by its unique report ID.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The full commit hash identifying the commit to which the report belongs. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the commit and its associated report. |
| reportId | string | yes | The unique identifier of the report to delete, accepted as either the report's UUID or its external ID. |
| workspace | string | yes | The workspace identifier, either the slug (short name) or the UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
delete_deploy_key Delete Deploy Key ~103
Permanently removes a deploy key from a repository, revoking its access. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique numeric identifier of the deploy key to delete. |
| repo_slug | string | yes | The repository slug or UUID that owns the deploy key. UUID values must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID where the repository resides. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_download_artifact Delete Download Artifact ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | The exact name of the download artifact file to delete, including its file extension. |
| repo_slug | string | yes | The repository identifier, either as a URL-friendly slug or as a UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier, either as a URL-friendly slug or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_environment Delete Environment ~97
Permanently deletes a deployment environment from a repository. This action cannot be undone and will remove all associated environment configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uuid | string | yes | The unique UUID of the deployment environment to delete, surrounded by curly braces. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
delete_environment_variable Delete Environment Variable ~126
Permanently deletes a specific variable from a deployment environment in a repository. This removes the variable and its value from the environment's configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uuid | string | yes | The unique identifier (UUID) of the deployment environment from which the variable will be deleted. |
| repo_slug | string | yes | The repository slug or identifier within the workspace. |
| variable_uuid | string | yes | The unique identifier (UUID) of the variable to permanently delete from the environment. |
| workspace | string | yes | The workspace identifier, either the slug (short name) or the UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_known_host Delete Known Host ~126
Deletes a specific SSH known host entry from a repository's Pipelines configuration. This removes the trusted host record identified by its UUID, preventing Pipelines from automatically trusting that host during SSH operations.
| Name | Type | Req | Description |
|---|---|---|---|
| known_host_uuid | string | yes | The unique UUID of the known host entry to delete, used to identify the specific record within the repository's Pipelines SSH configuration. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_pipeline_cache Delete Pipeline Cache ~88
Deletes a specific pipeline cache from a repository, freeing up cached resources associated with the given cache UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_uuid | string | yes | The unique identifier (UUID) of the pipeline cache to delete. |
| repo_slug | string | yes | The repository slug identifying the repository whose pipeline cache will be deleted. |
| workspace | string | yes | The workspace slug or UUID identifying the account that owns the repository. |
No output schema declared.
No examples provided.
delete_pipeline_caches Delete Pipeline Caches ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the pipeline cache to delete; all versions matching this name will be removed. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository whose pipeline caches will be deleted. |
| workspace | string | yes | The workspace slug or UUID identifying the account that owns the repository. |
No output schema declared.
No examples provided.
delete_pipeline_schedule Delete Pipeline Schedule ~108
Permanently deletes a specific pipeline schedule from a repository. This removes the scheduled trigger and prevents any future automated pipeline runs associated with it.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| schedule_uuid | string | yes | The unique UUID of the pipeline schedule to delete, used to identify the specific schedule within the repository. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_project Delete Project ~83
Permanently deletes a project from the specified workspace. The project must have no repositories; delete or transfer all repositories before attempting deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The unique key assigned to the project, identifying which project to delete. |
| workspace | string | yes | The workspace identifier, either as a slug (human-readable ID) or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_project_deploy_key Delete Project Deploy Key ~113
Permanently removes a specific deploy key from a project in the given workspace. This revokes any access granted to systems using that key.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique numeric identifier of the deploy key to be deleted from the project. |
| project_key | string | yes | The unique key identifier assigned to the project, used to reference the project within the workspace. |
| workspace | string | yes | The workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
What is the com.mcparmory/bitbucket MCP server?
com.mcparmory/bitbucket is an MCP server listed in the public MCP registry as com.mcparmory/bitbucket. Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces. This page covers its container image (ghcr.io/mcparmory/bitbucket:1.0.5).
Is the com.mcparmory/bitbucket MCP server safe to use?
com.mcparmory/bitbucket scores 49 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mcparmory/bitbucket MCP server expose?
com.mcparmory/bitbucket exposes 261 tools: list_webhook_event_types, list_webhook_event_types_by_subject, list_workspace_repositories, get_repository, create_repository, and 256 more. Their descriptions and schemas cost roughly 31,894 tokens of context every time the server is loaded.
Is the com.mcparmory/bitbucket MCP server still maintained?
com.mcparmory/bitbucket is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.