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 →
list_webhook_event_types_by_subject List Webhook Event Types by Subject ~80
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.
| Name | Type | Req | Description |
|---|---|---|---|
| subject_type | string | yes | The entity type for which to retrieve subscribable webhook events. Note: team and user subject types are deprecated; use workspace instead. |
No output schema declared.
No examples provided.
list_workspace_members List Workspace Members ~82
Retrieves all members belonging to the specified workspace. Supports filtering by email address (up to 90 at a time) when called by a workspace administrator, integration, or workspace access token.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The unique identifier of the workspace, either as a slug (e.g., a short name/alias) or as a UUID surrounded by curly braces. |
No output schema declared.
No examples provided.
list_workspace_permissions List Workspace Permissions ~93
Retrieves all members of a workspace along with their assigned permission levels (owner, collaborator, or member). Results can be filtered by permission level using the query parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | A filter expression to narrow results by permission level, using Bitbucket's filtering and sorting syntax. |
| workspace | string | yes | The workspace identifier, either the workspace slug (short name) or the workspace UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
list_workspace_pipeline_variables List Workspace Pipeline Variables ~65
Retrieves all pipeline configuration variables defined at the workspace level. These variables are available across all pipelines within the specified workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The unique identifier for the workspace, accepted as either a slug (human-readable short name) or a UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
list_workspace_projects List Workspace Projects ~58
Retrieves all projects belonging to a specified workspace. Returns a list of project resources associated with the given workspace identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
list_workspace_repositories List Workspace Repositories ~164
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.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | A query string to filter repositories using Bitbucket's filtering syntax, allowing you to narrow results by repository properties. |
| role | string | – | Filters repositories based on the authenticated user's access level: member (read access), contributor (write access), admin (administrator access), or owner (all repositories owned by the user). |
| sort | string | – | The field name by which to sort the returned repositories, following Bitbucket's sorting syntax for ordering results. |
| 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.
list_workspace_repository_permissions List Workspace Repository Permissions ~138
Retrieves the effective repository permissions for all repositories in a workspace, returning the highest permission level each user holds. Accessible only to workspace admins; results can be filtered and sorted by repository, user, or permission level.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | A query string to filter results by repository, user, or permission level using Bitbucket's filtering syntax; values must be URL-encoded. |
| sort | string | – | The response property name to sort results by, using Bitbucket's sorting syntax to control the order of returned permissions. |
| workspace | string | yes | The workspace identifier, either the workspace slug or the workspace UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
list_workspace_repository_permissions_for_user List Workspace Repository Permissions for User ~151
Retrieves each repository within the specified workspace where the authenticated user has been explicitly granted access, along with their highest effective permission level (admin, write, or read). Public repositories without explicit grants are excluded from results.
| Name | Type | Req | Description |
|---|---|---|---|
| q | string | – | A filter expression to narrow results by repository or permission level, using Bitbucket's filtering and sorting syntax. Values must be URL-encoded (e.g., encode `=` as `%3D`). |
| sort | string | – | The response property name to sort results by, using Bitbucket's filtering and sorting syntax. |
| 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.
list_workspace_runners List Workspace Runners ~65
Retrieve all pipeline runners configured for a specific workspace. Runners are used to execute Bitbucket Pipelines builds within the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The unique identifier for the workspace, accepted as either a slug (short name) or a UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
list_workspace_snippets List Workspace Snippets ~96
Retrieves all snippets owned by a specific workspace, optionally filtered by the authenticated user's role within that workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| role | string | – | Filters results to snippets where the authenticated user holds the specified role: owner (created the snippet), contributor (has edit access), or member (has view access). |
| 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.
list_workspace_webhooks List Workspace Webhooks ~69
Retrieves a paginated list of all webhooks installed on the specified workspace. Useful for auditing or managing webhook integrations configured at the workspace level.
| Name | Type | Req | Description |
|---|---|---|---|
| workspace | string | yes | The unique identifier for the workspace, accepted as either a slug (short name) or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
list_workspaces List Workspaces ~119
Retrieves all workspaces accessible to the authenticated user, including each workspace's details and the caller's admin permissions status. Supports filtering by admin role, sorting, and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| administrator | boolean | – | When set to true, returns only workspaces where the caller has admin permissions; when set to false, returns only workspaces where the caller does not have admin permissions. Omit to return all acces… |
| sort | string | – | Property name to sort the returned workspaces by; only sorting by slug is supported. |
No output schema declared.
No examples provided.
merge_pull_request Merge Pull Request ~263
Merges a pull request in the specified repository, combining the source branch into the target branch using the chosen merge strategy. Supports synchronous and asynchronous execution modes.
| Name | Type | Req | Description |
|---|---|---|---|
| async | boolean | – | When true, the merge runs asynchronously and returns immediately with a 202 status and a polling link in the Location header; when false (default), the merge runs synchronously and returns 200 on suc… |
| close_source_branch | boolean | – | Whether to delete the source branch after a successful merge; falls back to the value set when the pull request was created if not provided, which defaults to false. |
| merge_strategy | string | – | The strategy used to merge the pull request into the target branch; controls how commits are combined or rewritten. |
| message | string | – | Custom commit message to use on the resulting merge commit; limited to 128 KiB in size. |
| pull_request_id | integer | yes | The numeric ID of the pull request to merge. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) identifying the target repository. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
remove_default_reviewer Remove Default Reviewer ~99
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.
| 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 default reviewer to remove from the repository. |
| workspace | string | yes | The workspace slug or UUID that contains the repository. |
No output schema declared.
No examples provided.
remove_project_default_reviewer Remove Project Default Reviewer ~132
Removes a specific user from a project's default reviewers list. Once removed, the user will no longer be automatically added as a reviewer on new pull requests in that project.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The unique identifier of the project, either its short key or its UUID surrounded by curly-braces. |
| selected_user | string | yes | The unique identifier of the user to remove as a default reviewer, either their username or their account UUID surrounded by curly-braces. |
| workspace | string | yes | The unique identifier of the workspace containing the project, either its slug or its UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
remove_pull_request_change_request Remove Pull Request Change Request ~113
Removes the authenticated user's change request from a pull request, withdrawing their objection and allowing the PR to proceed toward merge.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The numeric ID of the pull request from which the change request will be removed. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) identifying the repository containing the pull request. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) identifying the workspace that owns the repository. |
No output schema declared.
No examples provided.
reopen_pull_request_comment_thread Reopen Pull Request Comment Thread ~132
Reopens a previously resolved comment thread on a pull request by removing its resolved status. This allows further discussion to continue on the specified comment.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the comment whose resolved status should be removed. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request containing the comment thread. |
| 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.
request_pull_request_changes Request Pull Request Changes ~119
Request changes on a pull request in a Bitbucket repository, indicating that the pull request requires modifications before it can be approved or merged.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The unique numeric identifier of the pull request on which changes are being requested. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository containing the pull request. 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.
resolve_pull_request_comment Resolve Pull Request Comment ~126
Marks a pull request comment thread as resolved, collapsing the discussion and indicating the concern has been addressed.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the comment thread to resolve. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request containing the comment thread. |
| 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 uniquely identifies the workspace containing the repository. |
No output schema declared.
No examples provided.
search_team_code Search Team Code ~167
Search across all repositories belonging to a team for code matching a given query, with results that can match file content, file paths, or both. Supports advanced query syntax for scoping searches to specific repositories and customizing returned fields.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | The page number of search results to retrieve, starting at 1 for the first page. |
| pagelen | string | – | The number of search results to return per page; controls pagination granularity. |
| search_query | string | yes | The search query string used to find matching code; supports advanced syntax such as scoping to a specific repository using the `repo:` qualifier, and combining multiple terms. |
| username | string | yes | The team account to search within, specified as either the team's username or its UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
search_user_code Search User Code ~164
Search across all repositories belonging to a specified user, matching against file content and/or file paths. Supports advanced query syntax including repository-scoped searches and field expansion for richer results.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | The page number of search results to retrieve, starting at 1 for the first page. |
| pagelen | string | – | The number of search results to return per page; controls pagination granularity. |
| search_query | string | yes | The search query string used to find matching code; supports advanced syntax such as scoping results to a specific repository using the `repo:` qualifier and combining multiple terms. |
| selected_user | string | yes | The unique identifier of the user whose repositories will be searched — either an Atlassian Account ID or a UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
search_workspace_code Search Workspace Code ~154
Search across all repositories in a workspace by code content, file path, or both. Supports scoped queries (e.g., limiting to a specific repository) and field expansion for richer response data.
| Name | Type | Req | Description |
|---|---|---|---|
| page | string | – | The page number of search results to retrieve, starting at 1 for the first page. |
| pagelen | string | – | The number of search results to return per page; controls pagination granularity. |
| search_query | string | yes | The search query string used to match code content or file paths, supporting the same syntax as the Bitbucket UI including repository-scoped filters. |
| workspace | string | yes | The workspace to search within, specified as either the workspace slug or its UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
set_pipeline_next_build_number Set Pipeline Next Build Number ~116
Updates the next build number to be assigned to a pipeline in the specified repository. The configured value must be strictly greater than the current latest build number.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | Request body containing the next build number to assign. Must be strictly higher than the current latest build number for this repository. |
| repo_slug | string | yes | The repository slug identifying which repository's pipeline build number sequence to update. |
| workspace | string | yes | The workspace identifier, either as a slug or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
set_repository_override_settings Set Repository Override Settings ~92
Configures the inheritance state for a repository's settings, determining which settings are overridden at the repository level versus inherited from the workspace.
| 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 slug or UUID identifying the workspace that contains the repository. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
set_repository_ssh_key_pair Set Repository SSH Key Pair ~110
Creates or updates the SSH key pair for a repository's pipeline configuration. The private key will be set as the default SSH identity in the build container.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The SSH key pair payload containing the public and private key to set for the repository's pipeline configuration. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| 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.
stop_pipeline Stop Pipeline ~110
Stops a running pipeline and all of its in-progress steps that have not yet completed. Use this to immediately halt pipeline execution within a specific repository.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_uuid | string | yes | The unique identifier (UUID) of the pipeline to stop, enclosed in curly braces. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the pipeline to stop. |
| workspace | string | yes | The workspace identifier, either the workspace slug (short name) or the workspace UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
trigger_pipeline Trigger Pipeline ~201
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The pipeline trigger payload defining the target and optional variables. The target type determines the trigger mode: use 'pipeline_ref_target' for branch or tag triggers, 'pipeline_commit_target' fo… |
| repo_slug | string | yes | The repository slug (URL-friendly name) or identifier within the workspace where the pipeline will be triggered. |
| workspace | string | yes | The workspace identifier — either the slug (short name) or the UUID surrounded by curly braces — that owns the repository. |
No output schema declared.
No examples provided.
unapprove_commit Unapprove Commit ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The SHA1 hash uniquely identifying the commit to unapprove. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) that contains the commit. |
| workspace | string | yes | The workspace ID (slug) or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
unapprove_pull_request Unapprove Pull Request ~113
Removes the authenticated user's approval from the specified pull request. Use this to retract a previously submitted approval on a pull request in the given repository.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The unique numeric identifier of the pull request to unapprove. |
| 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.
unwatch_snippet Unwatch Snippet ~75
Stops watching a specific snippet so the authenticated user no longer receives updates for it. Returns 204 No Content on success.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to stop watching. |
| workspace | string | yes | The workspace identifier, either as a slug or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_branch_restriction Update Branch Restriction ~138
Updates an existing branch restriction rule for a repository. Only fields included in the request body are modified; omitted fields retain their current values.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the branch restriction rule fields to update. Only fields present in the body will be modified. |
| id | string | yes | The unique numeric identifier of the branch restriction rule to update. |
| 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 ID (slug) or UUID identifying the workspace. UUID values must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_branching_model_settings Update Branching Model Settings ~113
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. 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.
update_commit_build_status Update Commit Build Status ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the build status fields to update, such as state, name, description, url, or refname. |
| commit | string | yes | The full SHA1 hash of the commit whose build status you want to update. |
| key | string | yes | The unique key identifying the build status entry to update. This value cannot be changed via this operation. |
| repo_slug | string | yes | The repository slug (URL-friendly name) or the repository UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace slug (URL-friendly identifier) or the workspace UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_commit_comment Update Commit Comment ~156
Updates the text content of an existing comment on a specific commit. Only the comment's content can be modified; other properties remain unchanged.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the updated comment content, structured as a commit comment object with a raw text content field. |
| comment_id | string | yes | The unique numeric identifier of the comment to update. |
| commit | string | yes | The full SHA1 hash of the commit that the comment belongs to. |
| 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 uniquely identifies the workspace containing the repository. |
No output schema declared.
No examples provided.
update_commit_property Update Commit Property ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Connect app that owns the property. |
| commit | string | yes | The commit identifier (hash) against which the application property is stored. |
| property_name | string | yes | The name of the application property to update, scoped to the specified Connect app. |
| repo_slug | string | yes | The slug of the repository where the commit resides. |
| workspace | string | yes | The workspace that contains the repository, identified by its slug or UUID (UUID must be wrapped in curly braces). |
No output schema declared.
No examples provided.
update_deploy_key Update Deploy Key ~102
Updates an existing deploy key in a repository, allowing the label and comment to be changed while keeping the same public key value.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The numeric ID of the deploy key to update. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) that contains the deploy key. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
update_environment Update Environment ~97
Apply configuration changes to a specific deployment environment in a repository. Use this to modify environment settings such as variables or deployment rules.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uuid | string | yes | The unique identifier (UUID) of the deployment environment to update. |
| 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.
update_environment_variable Update Environment Variable ~154
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the updated variable fields, such as key, value, or secured flag. |
| environment_uuid | string | yes | The UUID of the deployment environment whose variable is being updated. |
| repo_slug | string | yes | The repository slug or identifier within the workspace that owns the deployment environment. |
| variable_uuid | string | yes | The UUID of the specific variable to update within the deployment environment. |
| 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.
update_pipeline_known_host Update Pipeline Known Host ~140
Updates an existing SSH known host entry in a repository's pipeline configuration, allowing you to modify the host details for secure pipeline connections.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The request body containing the updated SSH known host details, such as the hostname and public key fingerprint. |
| known_host_uuid | string | yes | The unique UUID of the SSH known host entry to update, used to identify the specific record within the repository's pipeline 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.
update_pipeline_schedule Update Pipeline Schedule ~118
Updates an existing pipeline schedule for a repository. Use this to modify the timing or configuration of a scheduled pipeline run.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The updated schedule configuration payload containing the fields to modify on the existing schedule. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| schedule_uuid | string | yes | The unique identifier (UUID) of the pipeline schedule to update. |
| 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.
update_project Update Project ~112
Creates or updates a project within a workspace using the specified project key. If the key is changed in the request body, the project is relocated and the new URL is returned in the Location response header.
| Name | Type | Req | Description |
|---|---|---|---|
| project_key | string | yes | The unique key identifying the project within the workspace. This is the short alphanumeric identifier assigned to the project, not its name or UUID. |
| workspace | string | yes | The workspace in which the project resides, specified as either the workspace slug or the workspace UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
update_pull_request Update Pull Request ~138
Updates an open pull request's metadata, such as its title, description, or source and destination branches. Only pull requests in an open state can be modified.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the pull request fields to update, such as title, description, source branch, or destination branch. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request to update. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) that contains the pull request. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) that owns the repository. |
No output schema declared.
No examples provided.
update_pull_request_comment Update Pull Request Comment ~140
Updates the content of an existing comment on a specific pull request. Only the comment body can be modified through this operation.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The request body containing the updated comment content to replace the existing comment. |
| comment_id | string | yes | The unique numeric identifier of the comment to update. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request containing the comment. |
| 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.
update_pull_request_property Update Pull Request Property ~157
Update the value of a named application property stored against a specific pull request. Application properties allow Connect apps to attach custom metadata to Bitbucket resources.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The key identifying the Connect app that owns this property, used to namespace properties and prevent collisions between apps. |
| property_name | string | yes | The name of the application property to update, scoped under the specified app key. |
| pullrequest_id | string | yes | The unique numeric identifier of the pull request whose property is being updated. |
| repo_slug | string | yes | The slug of the repository that contains the pull request. |
| workspace | string | yes | The workspace containing the repository, identified by its slug or UUID (UUID must be wrapped in curly braces). |
No output schema declared.
No examples provided.
update_pull_request_task Update Pull Request Task ~159
Updates an existing task on a specific pull request, allowing changes to the task content and resolution state.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The numeric ID of the pull request that contains the task to update. |
| raw | string | yes | The updated text content of the task. |
| repo_slug | string | yes | The repository slug or UUID (surrounded by curly-braces) identifying the repository containing the pull request. |
| state | string | – | The resolution state of the task, indicating whether it is open or completed. |
| task_id | string | yes | The unique numeric ID of the task to update. |
| workspace | string | yes | The workspace slug or UUID (surrounded by curly-braces) identifying the workspace that owns the repository. |
No output schema declared.
No examples provided.
update_repository Update Repository ~144
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | The repository fields to update, such as name, description, or visibility settings. Refer to the repository POST endpoint documentation for the full request body structure. |
| repo_slug | string | yes | The slug or UUID of the repository to update. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID containing the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
update_repository_pipeline_variable Update Repository Pipeline Variable ~136
Updates an existing pipeline variable at the repository level, allowing modification of its value or configuration. Targets a specific variable by its UUID within the given workspace and repository.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | – | The updated variable object containing the new values or configuration to apply to the repository pipeline variable. |
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| variable_uuid | string | yes | The unique UUID of the pipeline variable to update, used to identify the exact variable to modify. |
| 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.
update_repository_property Update Repository Property ~125
Updates the value of a named application property stored against a specific repository. Properties are scoped to a Connect app and allow apps to persist custom metadata on repositories.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Connect app that owns this property. |
| property_name | string | yes | The name of the application property to update, scoped to the specified Connect app. |
| repo_slug | string | yes | The slug identifier of the repository within the specified workspace. |
| workspace | string | yes | The repository container, identified by either the workspace slug or the workspace UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
update_repository_runner Update Repository Runner ~106
Updates the configuration of a specific runner associated with a repository. Identifies the target runner by its UUID within the given workspace and repository.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| runner_uuid | string | yes | The unique identifier (UUID) of the runner to update, surrounded by curly-braces. |
| 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.
update_repository_webhook Update Repository Webhook ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository identifier, either its slug (short name) or its UUID surrounded by curly-braces. |
| uid | string | yes | The unique identifier of the installed webhook subscription to update. |
| workspace | string | yes | The workspace identifier, either its slug or its 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.