com.mcparmory/bitbucket
PYPI · MCPARMORY-BITBUCKET · 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 Security37
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Install-script risk not yet assessed.Unverified
- 2 of 46 dependencies flagged as unhealthy. View diagnostics → Partial
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: the license (MIT License) isn't a recognized OSI-approved license. 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 Management87
- Stability observed for 26 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 current MCP spec version (2026-07-28).Pass
How do I install the com.mcparmory/bitbucket MCP server?
com.mcparmory/bitbucket runs locally as a PyPI package, launched with uvx mcparmory-bitbucket. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcparmory-bitbucket
claude mcp add com-mcparmory-bitbucket -- uvx mcparmory-bitbucket
{
"mcpServers": {
"com-mcparmory-bitbucket": {
"command": "uvx",
"args": [
"mcparmory-bitbucket"
]
}
}
} {
"servers": {
"com-mcparmory-bitbucket": {
"command": "uvx",
"args": [
"mcparmory-bitbucket"
]
}
}
} codex mcp add com-mcparmory-bitbucket -- uvx mcparmory-bitbucket
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mcparmory-bitbucket": {
"type": "local",
"command": [
"uvx",
"mcparmory-bitbucket"
],
"enabled": true
}
}
} openclaw mcp add com-mcparmory-bitbucket --command uvx --arg mcparmory-bitbucket
mcp_servers:
com-mcparmory-bitbucket:
command: "uvx"
args: ["mcparmory-bitbucket"] {
"McpServers": {
"com-mcparmory-bitbucket": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcparmory-bitbucket"
]
}
}
} assistant mcp add com-mcparmory-bitbucket -t stdio -c uvx -a mcparmory-bitbucket
{
"mcpServers": {
"com-mcparmory-bitbucket": {
"command": "uvx",
"args": [
"mcparmory-bitbucket"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 −18
- Malware scan: pass → unverified ▼ security
- Stability: pass → 0.80 functional
- 17 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 13 Sept 26 +15
- Malware scan: unverified → pass ▲ security
- 12 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 11 Sept 26 −3
- Stability: pass → 0.80 functional
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 pypi/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 | pypi |
Background: How many MCP packages publish verified provenance →
Dependencies 46 packages
| Packages resolved | 46 |
|---|---|
| Stale | 1 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
delete_pull_request_comment Delete Pull Request Comment ~122
Permanently deletes a specific comment from a pull request. This action is irreversible and removes the comment from the pull request discussion thread.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the comment to delete. |
| pull_request_id | integer | yes | The unique numeric identifier of the pull request containing the comment. |
| 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 name) or the workspace UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_pull_request_property Delete Pull Request Property ~144
Deletes a specific application property value stored against a pull request. Use this to remove custom metadata associated with a pull request by a Connect app.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The key identifying the Connect app that owns the property being deleted. |
| property_name | string | yes | The name of the application property to delete from the pull request. |
| pullrequest_id | string | yes | The unique numeric identifier of the pull request whose property should be deleted. |
| repo_slug | string | yes | The slug of the repository containing 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.
delete_pull_request_task Delete Pull Request Task ~129
Permanently deletes a specific task from a pull request. This action cannot be undone and removes the task from the pull request's task list.
| Name | Type | Req | Description |
|---|---|---|---|
| pull_request_id | integer | yes | The numeric ID of the pull request from which the task will be deleted. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUIDs must be surrounded by curly-braces. |
| task_id | string | yes | The unique numeric ID of the task to delete. |
| 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_repository Delete Repository ~134
Permanently deletes the specified repository from a workspace. This action is irreversible and does not affect any existing forks of the repository.
| Name | Type | Req | Description |
|---|---|---|---|
| redirect_to | string | – | An optional redirect path to display a friendly relocation message in the Bitbucket UI when a repository has moved. Note that GET requests to the original endpoint will still return a 404 regardless. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository to delete. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace slug or UUID identifying the workspace that owns the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_repository_pipeline_variable Delete Repository Pipeline Variable ~108
Permanently deletes a specific pipeline variable from a repository. This removes the variable and its value from the repository's pipeline configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the pipeline variable to delete. |
| variable_uuid | string | yes | The UUID of the pipeline variable to delete, uniquely identifying the variable within the repository. |
| 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_repository_property Delete Repository Property ~125
Deletes a specific application property value stored against a repository. Removes the property identified by the app key and property name from the target repository.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Connect app that owns the property to be deleted. |
| property_name | string | yes | The name of the application property to delete from the repository. |
| repo_slug | string | yes | The slug identifier of the repository from which the 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_repository_runner Delete Repository Runner ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or identifier within the specified workspace. |
| runner_uuid | string | yes | The unique UUID of the runner to delete, used to precisely identify the target runner within the repository's Pipelines configuration. |
| 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_repository_ssh_key_pair Delete Repository SSH Key Pair ~84
Deletes the SSH key pair configured for a repository's pipelines. This removes both the public and private keys associated with the repository's pipeline SSH configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
delete_repository_webhook Delete Repository Webhook ~106
Permanently removes a specific webhook subscription from a repository, stopping all future event deliveries to the configured endpoint.
| 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. |
| uid | string | yes | The unique identifier of the installed webhook subscription to delete. |
| 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_snippet Delete Snippet ~75
Permanently deletes a specific snippet from the given workspace. Returns an empty response upon successful deletion.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to delete. |
| 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.
delete_snippet_comment Delete Snippet Comment ~101
Permanently deletes a specific comment from a snippet. This action is restricted to the comment author, snippet creator, or a workspace admin.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the comment to delete. |
| encoded_id | string | yes | The unique identifier of the snippet, as assigned by Bitbucket. |
| 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_snippet_revision Delete Snippet Revision ~123
Deletes a snippet at a specific versioned commit, but only if that commit is the latest revision. To delete a snippet unconditionally, use the base snippet delete endpoint instead.
| Name | Type | Req | Description |
|---|---|---|---|
| encoded_id | string | yes | The unique identifier of the snippet to delete. |
| node_id | string | yes | The SHA1 commit hash identifying the specific revision of the snippet; must point to the latest commit or the request will fail. |
| 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.
delete_tag Delete Tag ~106
Permanently deletes a tag from the specified repository. Provide only the tag name without any ref prefixes such as refs/tags.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the tag to delete, without any ref prefixes. |
| 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_user_app_property Delete User App Property ~109
Deletes a specific application property value stored against a Bitbucket user account. Targets a property by its Connect app key and property name.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Bitbucket Connect app whose property is being deleted. |
| property_name | string | yes | The name of the application property to delete from the user's account. |
| selected_user | string | yes | The identifier of the target user account, either as an Atlassian Account ID or a UUID wrapped in curly braces. |
No output schema declared.
No examples provided.
delete_user_gpg_key Delete User GPG Key ~97
Permanently removes a specific GPG public key from a user's account, identified by its fingerprint. This action cannot be undone.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | The unique fingerprint identifying the GPG key to delete, used to locate the specific key within the user's 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.
delete_user_repository_permission Delete User Repository Permission ~127
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository within the workspace. |
| selected_user_id | string | yes | The account identifier for the user whose repository permission will be deleted, provided as either an Atlassian Account ID or a UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier, provided as either the workspace slug or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_user_ssh_key Delete User SSH Key ~85
Permanently removes a specific SSH public key from a user's account, revoking any access associated with that key.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique UUID identifier of the SSH key to delete. |
| selected_user | string | yes | The account identifier for the target user, accepted as either an Atlassian Account ID or an account UUID wrapped in curly-braces. |
No output schema declared.
No examples provided.
delete_workspace_pipeline_variable Delete Workspace Pipeline Variable ~104
Permanently deletes a specific pipeline configuration variable at the workspace level. This action cannot be undone and will remove the variable from all pipelines that reference it within the workspace.
| Name | Type | Req | Description |
|---|---|---|---|
| variable_uuid | string | yes | The UUID of the workspace pipeline variable to delete. This uniquely identifies the specific variable to be permanently removed. |
| workspace | string | yes | The unique identifier for the workspace, accepted as either a slug (human-readable short name) or a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
delete_workspace_runner Delete Workspace Runner ~88
Permanently deletes a specific Pipelines runner from a workspace using its UUID. This removes the runner's registration and it will no longer be available to execute pipeline steps.
| Name | Type | Req | Description |
|---|---|---|---|
| runner_uuid | string | yes | The unique identifier (UUID) of the runner to delete. |
| 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.
delete_workspace_webhook Delete Workspace Webhook ~75
Permanently deletes a specific webhook subscription from a workspace, stopping all future event deliveries for that hook.
| Name | Type | Req | Description |
|---|---|---|---|
| uid | string | yes | The unique identifier of the installed webhook subscription to delete. |
| 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.
fork_repository Fork Repository ~195
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | Optional request body following the repository JSON schema to configure the fork. Must include a workspace slug to specify the fork destination, and a name to distinguish it from the parent. Overrida… |
| repo_slug | string | yes | The slug or UUID of the repository to fork. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The slug or UUID of the workspace that owns the source repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_branch Get Branch ~122
Retrieves details for a specific branch within a repository by its name. Authentication is required, and private repositories require appropriate account authorization.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The name of the branch to retrieve. For Git repositories, omit any prefix such as 'refs/heads' and provide only the bare branch name. |
| repo_slug | string | yes | The repository identifier, either as a human-readable slug or as a UUID surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier, either as a human-readable slug or as a UUID surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_branch_restriction Get Branch Restriction ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The unique numeric identifier of the branch restriction rule to retrieve. |
| 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 that owns the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_branching_model Get Branching Model ~102
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository identifier, either the URL-friendly slug or the repository UUID enclosed in curly-braces. |
| 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.
get_branching_model_settings Get Branching Model Settings ~123
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the repository whose branching model settings are being retrieved. 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.
get_commit Get Commit ~106
Retrieves details for a specific commit in a repository using its SHA1 identifier. Returns commit metadata including author, timestamp, and associated changes.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The full SHA1 hash of the commit to retrieve. |
| 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.
get_commit_build_status Get Commit Build Status ~136
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.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The full SHA1 hash of the commit whose build status you want to retrieve. |
| key | string | yes | The unique key identifying the specific build status entry associated with the commit. |
| 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.
get_commit_comment Get Commit Comment ~121
Retrieves a specific comment on a commit by its comment ID. Returns the full comment details including content, author, and timestamps.
| Name | Type | Req | Description |
|---|---|---|---|
| comment_id | string | yes | The unique numeric identifier of the commit comment to retrieve. |
| commit | string | yes | The full SHA1 hash of the commit whose comment is being retrieved. |
| 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.
get_commit_property Get Commit Property ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| app_key | string | yes | The unique key identifying the Connect app that owns the property. |
| commit | string | yes | The identifier of the commit whose application property is being retrieved. |
| property_name | string | yes | The name of the application property to retrieve from the specified commit. |
| repo_slug | string | yes | The slug of the repository where the commit resides. |
| 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.
get_commit_report Get Commit Report ~133
Retrieves a single code insight report for a specific commit in a repository. Returns the full report details matching the provided report ID.
| Name | Type | Req | Description |
|---|---|---|---|
| commit | string | yes | The full commit hash identifying the specific commit the report is associated with. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the commit and report. |
| reportId | string | yes | The unique identifier of the report, accepted as either a UUID or an external ID assigned by the reporting tool. |
| 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.
get_commit_report_annotation Get Commit Report Annotation ~158
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotationId | string | yes | The unique identifier of the annotation to retrieve, accepted as either its UUID or its external ID string. |
| commit | string | yes | The full commit hash identifying the commit to which the report belongs. |
| repo_slug | string | yes | The URL-friendly slug of the repository within the specified workspace. |
| reportId | string | yes | The unique identifier of the report, accepted as either its UUID or its external ID string. |
| 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.
get_current_user Get Current User ~35
Retrieves the profile and details of the currently authenticated user. Useful for confirming identity or accessing user-specific information tied to the active session.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_default_reviewer Get Default Reviewer ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the repository. UUIDs must be surrounded by curly-braces. |
| target_username | string | yes | The username or UUID of the default reviewer to look up. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace ID (slug) or UUID that owns the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_deploy_key Get Deploy Key ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| key_id | string | yes | The unique numeric identifier of the deploy key to retrieve. |
| repo_slug | string | yes | The repository slug or UUID that owns the deploy key. UUIDs must be surrounded by curly-braces. |
| workspace | string | yes | The workspace identifier (slug) or UUID in which the repository resides. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_deployment Get Deployment ~106
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.
| Name | Type | Req | Description |
|---|---|---|---|
| deployment_uuid | string | yes | The unique identifier (UUID) of the deployment to retrieve. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the deployment. |
| 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.
get_diffstat Get Diffstat ~269
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ignore_whitespace | boolean | – | When true, whitespace-only changes are excluded from the diffstat output. |
| path | string | – | Restricts the diffstat to one or more specific file paths; repeat this parameter to include multiple paths. |
| renames | boolean | – | Controls whether file rename detection is performed; defaults to true when omitted. |
| repo_slug | string | yes | The repository slug or UUID identifying the repository within the workspace. |
| spec | string | yes | A single commit SHA or a commit range using double-dot notation to compare two commits. For two-commit specs, the first commit represents the source (changes to preview) and the second represents the… |
| topic | boolean | – | When true, returns a three-dot diff between the source commit and the merge base of the source and destination commits. When false, returns a simple two-dot diff between the two commits. |
| workspace | string | yes | The workspace ID (slug) or UUID identifying the workspace that owns the repository. |
No output schema declared.
No examples provided.
get_download_artifact Get Download Artifact ~116
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.
| Name | Type | Req | Description |
|---|---|---|---|
| filename | string | yes | The exact filename of the download artifact to retrieve from the repository's downloads section. |
| repo_slug | string | yes | The repository identifier, either as a URL-friendly slug or as a UUID enclosed in curly braces. |
| workspace | string | yes | The workspace identifier, either as a URL-friendly slug or as a UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
get_effective_branching_model Get Effective Branching Model ~93
Retrieves the effective (currently applied) branching model for a repository, reflecting any inherited workspace-level settings combined with repository-specific overrides.
| 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 slug or UUID identifying the workspace that contains the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_email Get Email ~60
Retrieves details for a specific email address belonging to the authenticated user. The response includes whether the address has been confirmed and whether it is the user's primary email.
| Name | Type | Req | Description |
|---|---|---|---|
| string | yes | The full email address to look up among the authenticated user's registered email addresses. |
No output schema declared.
No examples provided.
get_environment Get Environment ~108
Retrieves the details of a specific deployment environment within a repository. Use this to inspect environment configuration, status, and metadata by its unique identifier.
| Name | Type | Req | Description |
|---|---|---|---|
| environment_uuid | string | yes | The unique UUID of the deployment environment to retrieve, surrounded by curly-braces. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that contains the target 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.
get_merge_base Get Merge Base ~132
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug or UUID identifying the target repository. UUIDs must be surrounded by curly-braces. |
| revspec | string | yes | A range of exactly two commits specified using double-dot notation, identifying the two commits whose common ancestor should be found. |
| workspace | string | yes | The workspace ID (slug) or UUID that owns the repository. UUIDs must be surrounded by curly-braces. |
No output schema declared.
No examples provided.
get_pipeline Get Pipeline ~98
Retrieves the details of a specific pipeline run within a repository, including its status, steps, and configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_uuid | string | yes | The unique UUID of the pipeline run to retrieve. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that uniquely identifies the repository 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.
get_pipeline_cache_content_uri Get Pipeline Cache Content URI ~103
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cache_uuid | string | yes | The unique identifier (UUID) of the pipeline cache whose content URI you want to retrieve. |
| repo_slug | string | yes | The slug or UUID of the repository containing the pipeline cache. |
| workspace | string | yes | The slug or UUID of the Bitbucket workspace that owns the repository. |
No output schema declared.
No examples provided.
get_pipeline_schedule Get Pipeline Schedule ~103
Retrieves a specific pipeline schedule by its UUID for a given repository. Returns the full schedule configuration including timing and status details.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug (URL-friendly name) that uniquely identifies the repository within the workspace. |
| schedule_uuid | string | yes | The UUID that uniquely identifies the pipeline schedule to retrieve. |
| 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.
get_pipeline_ssh_known_host Get Pipeline SSH Known Host ~113
Retrieves a specific SSH known host entry configured at the repository level for Pipelines, identified by its UUID.
| Name | Type | Req | Description |
|---|---|---|---|
| known_host_uuid | string | yes | The UUID of the SSH known host entry to retrieve, uniquely identifying it within the repository's Pipelines SSH configuration. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that uniquely identifies the repository within the workspace. |
| workspace | string | yes | The workspace identifier, either the slug (short name) or the UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
get_pipeline_step Get Pipeline Step ~140
Retrieves the details of a specific step within a pipeline, including its status, timing, and configuration. Useful for monitoring or inspecting individual steps of a CI/CD pipeline run.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_uuid | string | yes | The unique identifier (UUID) of the pipeline whose step is being retrieved. |
| repo_slug | string | yes | The repository slug, which is the URL-friendly name of the repository within the specified workspace. |
| step_uuid | string | yes | The unique identifier (UUID) of the specific step within the pipeline to retrieve. |
| 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.
get_pipeline_step_log Get Pipeline Step Log ~136
Retrieves the full log file for a specific step within a pipeline. Supports HTTP Range requests to efficiently stream or paginate potentially large log files.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_uuid | string | yes | The unique identifier (UUID) of the pipeline whose step log is being retrieved. |
| repo_slug | string | yes | The repository slug, which is the URL-friendly name of the repository within the workspace. |
| step_uuid | string | yes | The unique identifier (UUID) of the specific pipeline step whose log file should be returned. |
| 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.
get_pipeline_step_log_container Get Pipeline Step Log Container ~158
Retrieves the log file for a build container or service container within a specific pipeline step. Supports HTTP Range requests to efficiently handle large log files.
| Name | Type | Req | Description |
|---|---|---|---|
| log_uuid | string | yes | The UUID identifying which container log to retrieve — use the step UUID for the main build container, or the service container UUID for a service container. |
| pipeline_uuid | string | yes | The UUID of the pipeline whose step logs are being retrieved. |
| repo_slug | string | yes | The repository slug identifying the target repository within the workspace. |
| step_uuid | string | yes | The UUID of the step within the pipeline whose container logs are being retrieved. |
| 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.
get_pipeline_step_test_report Get Pipeline Step Test Report ~132
Retrieves a summary of test reports for a specific step within a pipeline, providing an overview of test results such as pass/fail counts and coverage metrics.
| Name | Type | Req | Description |
|---|---|---|---|
| pipeline_uuid | string | yes | The UUID of the pipeline whose step test reports are being retrieved. |
| repo_slug | string | yes | The repository slug (URL-friendly name) that uniquely identifies the repository within the workspace. |
| step_uuid | string | yes | The UUID of the specific pipeline step for which test reports are being retrieved. |
| workspace | string | yes | The workspace identifier, either the slug (short name) or the UUID enclosed in curly braces. |
No output schema declared.
No examples provided.
get_pipeline_variable Get Pipeline Variable ~111
Retrieves a specific pipeline configuration variable for a repository by its UUID. Use this to inspect the details of a single repository-level pipeline variable.
| Name | Type | Req | Description |
|---|---|---|---|
| repo_slug | string | yes | The repository slug (URL-friendly name) that uniquely identifies the repository within the workspace. |
| variable_uuid | string | yes | The UUID of the pipeline configuration variable to retrieve, uniquely identifying it 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.
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 PyPI package (mcparmory-bitbucket).
Is the com.mcparmory/bitbucket MCP server safe to use?
com.mcparmory/bitbucket scores 61 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.