Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/bitbucket

PYPI · MCPARMORY-BITBUCKET · 2 COMPONENTS · SCANNED SEP 20

Manage repositories, branches, webhooks, and pull requests in Bitbucket workspaces

−15 this week 61 Trust /100
Trust breakdown (7 categories)

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
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
Install

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

# add to Claude Code
claude mcp add com-mcparmory-bitbucket -- uvx mcparmory-bitbucket
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-bitbucket": {
      "command": "uvx",
      "args": [
        "mcparmory-bitbucket"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-bitbucket": {
      "command": "uvx",
      "args": [
        "mcparmory-bitbucket"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-bitbucket -- uvx mcparmory-bitbucket
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-bitbucket": {
      "type": "local",
      "command": [
        "uvx",
        "mcparmory-bitbucket"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-mcparmory-bitbucket --command uvx --arg mcparmory-bitbucket
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-bitbucket:
    command: "uvx"
    args: ["mcparmory-bitbucket"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-bitbucket": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "mcparmory-bitbucket"
      ]
    }
  }
}
# add to Vellum
assistant mcp add com-mcparmory-bitbucket -t stdio -c uvx -a mcparmory-bitbucket
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-bitbucket": {
      "command": "uvx",
      "args": [
        "mcparmory-bitbucket"
      ]
    }
  }
}
Changelog

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
Diagnostics

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 →

MCP tools · 261 exposed · ~31,894 tokens

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 →

Tool Tokens
get_pipelines_config ~71

Retrieves the Pipelines configuration for a specific repository, including settings that control how pipelines are enabled and executed.

NameTypeReqDescription
repo_slugstringyesThe slug or UUID of the repository whose Pipelines configuration is being retrieved.
workspacestringyesThe slug or UUID of the workspace that owns the repository.

No output schema declared.

No examples provided.

get_project ~82

Retrieves details for a specific project within a workspace. Returns project metadata including its key, name, and associated settings.

NameTypeReqDescription
project_keystringyesThe unique key assigned to the project, used to identify it within the workspace.
workspacestringyesThe workspace identifier, either as a slug (human-readable ID) or a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_project_branching_model ~94

Retrieves the read-only branching model configured at the project level, including development and production branch settings and all enabled branch types. To modify these settings, use the branching model settings endpoint.

NameTypeReqDescription
project_keystringyesThe unique key assigned to the project within the workspace.
workspacestringyesThe workspace identifier, either as a slug (human-readable ID) or as a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_project_branching_model_settings ~112

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

NameTypeReqDescription
project_keystringyesThe unique key assigned to the project within the workspace, used to identify which project's branching model settings to retrieve.
workspacestringyesThe workspace identifier, accepted as either the workspace slug or the workspace UUID enclosed in curly braces.

No output schema declared.

No examples provided.

get_project_default_reviewer ~127

Retrieves a specific default reviewer for a project within a workspace. Returns reviewer details for the specified user if they are configured as a default reviewer on the project.

NameTypeReqDescription
project_keystringyesThe unique identifier of the project, either its short key or its UUID surrounded by curly-braces.
selected_userstringyesThe unique identifier of the default reviewer to retrieve, either their username or their account UUID surrounded by curly-braces.
workspacestringyesThe 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.

get_project_deploy_key ~105

Retrieves a specific deploy key associated with a project, identified by its key ID. Returns the full deploy key details for the given workspace and project.

NameTypeReqDescription
key_idstringyesThe unique numeric identifier of the deploy key to retrieve.
project_keystringyesThe unique key assigned to the project, used to identify it within the workspace.
workspacestringyesThe workspace identifier, either as a slug or as a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_pull_request ~101

Retrieves the details of a specific pull request within a repository, including its status, reviewers, and associated commits.

NameTypeReqDescription
pull_request_idintegeryesThe unique numeric identifier of the pull request to retrieve.
repo_slugstringyesThe repository slug or UUID identifying the repository; UUIDs must be surrounded by curly-braces.
workspacestringyesThe workspace slug or UUID identifying the workspace; UUIDs must be surrounded by curly-braces.

No output schema declared.

No examples provided.

get_pull_request_comment ~122

Retrieves a specific comment from a pull request by its comment ID. Returns the full comment details including content, author, and timestamps.

NameTypeReqDescription
comment_idstringyesThe unique numeric identifier of the comment to retrieve.
pull_request_idintegeryesThe unique numeric identifier of the pull request containing the comment.
repo_slugstringyesThe repository slug (URL-friendly name) or the repository UUID surrounded by curly-braces.
workspacestringyesThe workspace slug (URL-friendly name) or the workspace UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_pull_request_diff ~131

Retrieves the file diff for a specific pull request, showing all line-level changes between the source and destination branches. Redirects to the repository diff endpoint using the revspec corresponding to the pull request.

NameTypeReqDescription
pull_request_idintegeryesThe unique numeric identifier of the pull request whose diff you want to retrieve.
repo_slugstringyesThe repository slug or UUID identifying the repository containing the pull request. UUID values must be surrounded by curly-braces.
workspacestringyesThe 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.

get_pull_request_diffstat ~132

Retrieves the diff stat for a specific pull request, showing a summary of file changes (additions, deletions, modifications) by redirecting to the repository diffstat endpoint using the pull request's revision spec.

NameTypeReqDescription
pull_request_idintegeryesThe unique numeric identifier of the pull request whose diff stat you want to retrieve.
repo_slugstringyesThe repository slug or UUID identifying the repository. UUIDs must be surrounded by curly-braces.
workspacestringyesThe 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_pull_request_merge_task_status ~165

Checks the status of an asynchronous pull request merge task using a task ID returned from a long-running merge operation. Returns PENDING while in progress, SUCCESS with the merged pull request object on completion, or an error if the merge failed.

NameTypeReqDescription
pull_request_idintegeryesThe numeric ID of the pull request whose merge task status is being checked.
repo_slugstringyesThe repository slug or UUID (surrounded by curly-braces) identifying the repository containing the pull request.
task_idstringyesThe task ID returned by the merge endpoint when the merge operation was accepted asynchronously with a 202 response.
workspacestringyesThe workspace slug or UUID (surrounded by curly-braces) identifying the workspace that owns the repository.

No output schema declared.

No examples provided.

get_pull_request_patch ~109

Retrieves the patch file for a specific pull request, redirecting to the repository patch endpoint using the pull request's revision specification.

NameTypeReqDescription
pull_request_idintegeryesThe unique numeric identifier of the pull request within the repository.
repo_slugstringyesThe repository slug or UUID identifying the repository; UUIDs must be surrounded by curly-braces.
workspacestringyesThe workspace ID (slug) or UUID identifying the workspace; UUIDs must be surrounded by curly-braces.

No output schema declared.

No examples provided.

get_pull_request_property ~158

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

NameTypeReqDescription
app_keystringyesThe key identifying the Connect app that owns the property, used to namespace properties and avoid conflicts between apps.
property_namestringyesThe name of the application property to retrieve, scoped under the specified Connect app key.
pullrequest_idstringyesThe unique numeric identifier of the pull request within the repository.
repo_slugstringyesThe slug of the repository containing the pull request.
workspacestringyesThe 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_pull_request_task ~121

Retrieves a specific task associated with a pull request in the given repository. Returns full task details for the specified task ID.

NameTypeReqDescription
pull_request_idintegeryesThe numeric ID of the pull request containing the task.
repo_slugstringyesThe repository slug or UUID identifying the repository. UUIDs must be surrounded by curly-braces.
task_idstringyesThe unique numeric ID of the task to retrieve.
workspacestringyesThe workspace slug or UUID identifying the workspace. UUIDs must be surrounded by curly-braces.

No output schema declared.

No examples provided.

get_repository ~85

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

NameTypeReqDescription
repo_slugstringyesThe repository identifier, either as a URL-friendly slug or as a UUID wrapped in curly-braces.
workspacestringyesThe workspace identifier, either as a URL-friendly slug or as a UUID wrapped in curly-braces.

No output schema declared.

No examples provided.

get_repository_diff ~327

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

NameTypeReqDescription
binarybooleanWhen true, binary files are included in the diff output. Defaults to true if omitted.
contextintegerNumber of context lines to include around each change in the diff, overriding the default of three lines.
ignore_whitespacebooleanWhen true, whitespace differences are excluded from the diff output.
pathstringRestricts the diff output to a specific file path within the repository. This parameter may be repeated to filter on multiple paths.
renamesbooleanWhen true, rename detection is performed to identify moved or renamed files. Defaults to true if omitted.
repo_slugstringyesThe repository slug or UUID identifying the repository within the workspace.
specstringyesA single commit SHA or a two-commit range using double-dot notation to define the diff scope. For two-commit ranges, the first commit contains the changes to preview and the second represents the com…
topicbooleanWhen true, returns a two-way three-dot diff showing changes between the source commit and the merge base of the source and destination commits. When false, returns a simple two-dot diff between sourc…
workspacestringyesThe workspace slug or UUID that owns the repository.

No output schema declared.

No examples provided.

get_repository_group_permission ~118

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

NameTypeReqDescription
group_slugstringyesThe slug identifier of the group whose repository permission is being retrieved.
repo_slugstringyesThe repository slug or UUID (surrounded by curly-braces) that identifies the target repository.
workspacestringyesThe workspace ID (slug) or UUID (surrounded by curly-braces) that contains the repository.

No output schema declared.

No examples provided.

get_repository_override_settings ~91

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

NameTypeReqDescription
repo_slugstringyesThe repository slug or UUID identifying the target repository. UUIDs must be surrounded by curly-braces.
workspacestringyesThe 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_repository_patch ~169

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

NameTypeReqDescription
repo_slugstringyesThe repository slug or UUID identifying the target repository. UUIDs must be surrounded by curly-braces.
specstringyesA single commit SHA or a two-commit range using double-dot notation to generate a patch series. For a range, the first commit is the source and the second is the destination.
workspacestringyesThe 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.

get_repository_property ~120

Retrieves a specific application property value stored against a repository for a given Connect app. Useful for reading custom metadata or configuration values associated with a repository.

NameTypeReqDescription
app_keystringyesThe unique key identifying the Connect app that owns the property.
property_namestringyesThe name of the application property to retrieve from the repository.
repo_slugstringyesThe slug of the repository from which the property value will be retrieved.
workspacestringyesThe workspace containing the repository, identified by its slug or UUID wrapped in curly braces.

No output schema declared.

No examples provided.

get_repository_root_src ~101

Retrieves the root directory listing of a repository's main branch, automatically resolving the branch name and latest commit. This is a convenience redirect equivalent to browsing the root path of the main branch directly.

NameTypeReqDescription
repo_slugstringyesThe repository identifier, either as a URL-friendly slug or as a UUID wrapped in curly-braces.
workspacestringyesThe workspace identifier, either as a URL-friendly slug or as a UUID wrapped in curly-braces.

No output schema declared.

No examples provided.

get_repository_runner ~107

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

NameTypeReqDescription
repo_slugstringyesThe repository slug (URL-friendly name) that uniquely identifies the repository within the workspace.
runner_uuidstringyesThe unique UUID of the runner to retrieve, used to identify a specific Pipelines runner within the repository.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_repository_src ~340

Retrieve the raw contents of a file or a paginated directory listing at a specific commit in a Bitbucket repository. Supports metadata retrieval, rendered markup output, recursive directory traversal, and filtering/sorting for directory listings.

NameTypeReqDescription
commitstringyesThe full SHA1 hash of the commit to retrieve file or directory contents from.
formatstringControls the response format: 'meta' returns JSON metadata about the file or directory (size, attributes, links) instead of raw contents; 'rendered' returns HTML-rendered markup for supported plain-t…
max_depthintegerMaximum directory depth to recurse into when listing directory contents. Performs a breadth-first traversal; very large values may cause the request to time out with a 555 error. Defaults to 1 (non-r…
pathstringyesThe path to the target file or directory within the repository, relative to the repository root. Append a trailing slash when targeting the root directory.
qstringA filter expression to narrow directory listing results using Bitbucket's filtering syntax, such as filtering by file size or attributes.
repo_slugstringyesThe repository slug or UUID identifying the repository. UUIDs must be surrounded by curly braces.
sortstringA sort expression to order directory listing results using Bitbucket's sorting syntax, such as sorting by size ascending or descending.
workspacestringyesThe 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_repository_ssh_key_pair ~90

Retrieves the SSH key pair configured for a repository's pipeline, returning only the public key. The private key is write-only and is never exposed through the API or logs.

NameTypeReqDescription
repo_slugstringyesThe repository slug or identifier within the specified workspace.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_repository_tag ~107

Retrieves details for a specific tag in a repository, including the tag's target commit, tagger information, date, and associated links.

NameTypeReqDescription
namestringyesThe name of the tag to retrieve.
repo_slugstringyesThe repository slug or UUID (surrounded by curly-braces) that uniquely identifies the repository within the workspace.
workspacestringyesThe workspace slug or UUID (surrounded by curly-braces) that uniquely identifies the workspace containing the repository.

No output schema declared.

No examples provided.

get_repository_webhook ~111

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

NameTypeReqDescription
repo_slugstringyesThe repository slug (URL-friendly name) or the repository UUID surrounded by curly-braces.
uidstringyesThe unique identifier of the installed webhook to retrieve.
workspacestringyesThe workspace slug (ID) or the workspace UUID surrounded by curly-braces that owns the repository.

No output schema declared.

No examples provided.

get_snippet ~108

Retrieves a single snippet by its ID within a workspace. Supports multiple response content types: application/json (default, metadata and file links only), multipart/related (full snippet including file contents in one response), and multipart/form-data (flat structure with file contents).

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet to retrieve.
workspacestringyesThe workspace identifier, either as a slug (e.g. a short name) or as a UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_snippet_comment ~97

Retrieves a specific comment on a snippet within a workspace. Returns the full comment details for the given comment ID.

NameTypeReqDescription
comment_idstringyesThe unique numeric identifier of the comment to retrieve.
encoded_idstringyesThe unique identifier of the snippet, as assigned by Bitbucket.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_snippet_commit_changes ~111

Retrieves the changes made to a specific snippet in a given commit. Use this to inspect what was modified in a snippet at a particular point in its history.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet whose commit changes you want to retrieve.
revisionstringyesThe SHA1 hash of the commit whose changes you want to inspect.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_snippet_diff ~164

Retrieves the diff of a specific snippet commit against its first parent, showing what changed in that revision. Optionally filter the diff to a single file using the path parameter.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet whose diff is being retrieved.
pathstringWhen provided, restricts the diff output to only the specified file path within the snippet, rather than showing all changed files.
revisionstringyesA revspec expression identifying the commit or range to diff, such as a commit SHA1, a branch/tag ref name, or a two-dot compare expression to diff between two refs.
workspacestringyesThe workspace containing the snippet, specified as either the workspace slug or the workspace UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_snippet_file_content ~106

Retrieves the raw content of a specific file within a snippet at its HEAD revision, bypassing the need to first fetch the snippet and extract versioned file links.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet to retrieve the file from.
pathstringyesThe relative path to the target file within the snippet.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_snippet_file_contents ~144

Retrieves the raw contents of a specific file within a snippet at a given commit revision. The response includes appropriate Content-Type and Content-Disposition headers based on the file's name and type.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet to retrieve the file from.
node_idstringyesThe commit revision SHA1 hash identifying the specific version of the snippet to retrieve the file from.
pathstringyesThe path to the target file within the snippet, relative to the snippet's root.
workspacestringyesThe 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.

get_snippet_patch ~146

Retrieves the patch of a specific snippet commit against its first parent, including commit headers such as username and message. Unlike a diff, this returns separate patches for each commit on the second parent's ancestry up to the oldest common ancestor for merge commits.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet to retrieve the patch for.
revisionstringyesA revspec expression identifying the commit or range to patch against its first parent, such as a commit SHA1, a ref name, or a range expression using double-dot notation.
workspacestringyesThe workspace containing the snippet, specified as either the workspace slug or the workspace UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_snippet_revision ~120

Retrieves the file contents of a snippet at a specific historical revision identified by a commit SHA1. Unlike the standard snippet endpoint, this returns the snapshot of file contents at the given revision rather than the current version.

NameTypeReqDescription
encoded_idstringyesThe unique identifier of the snippet to retrieve.
node_idstringyesThe commit revision SHA1 hash identifying the specific historical version of the snippet to retrieve.
workspacestringyesThe workspace containing the snippet, specified as either the workspace slug or the workspace UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_user ~65

Retrieves public profile information for a specified Bitbucket user account. Private profiles omit location, website, and account creation date fields.

NameTypeReqDescription
selected_userstringyesThe identifier of the user to retrieve, accepted as either an Atlassian Account ID or a UUID wrapped in curly braces.

No output schema declared.

No examples provided.

get_user_app_property ~111

Retrieves a specific application property value stored against a Bitbucket user account. Use this to read Connect app metadata associated with a particular user.

NameTypeReqDescription
app_keystringyesThe unique key identifying the Connect app whose property is being retrieved.
property_namestringyesThe name of the application property to retrieve from the specified user and Connect app.
selected_userstringyesThe 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.

get_user_gpg_key ~93

Retrieves a specific GPG public key belonging to a user, identified by its fingerprint. Supports partial responses to include the full key and subkey fields.

NameTypeReqDescription
fingerprintstringyesThe fingerprint uniquely identifying the GPG key to retrieve.
selected_userstringyesThe user whose GPG key is being retrieved, specified as either an Atlassian Account ID or a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

get_user_repository_permission ~136

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

NameTypeReqDescription
repo_slugstringyesThe repository slug or UUID identifying the target repository. UUID format must be surrounded by curly-braces.
selected_user_idstringyesThe unique identifier of the user whose permission is being retrieved. Accepts either an Atlassian Account ID or a UUID surrounded by curly-braces.
workspacestringyesThe workspace slug or UUID that contains the repository. UUID format must be surrounded by curly-braces.

No output schema declared.

No examples provided.

get_user_ssh_key ~97

Retrieves a specific SSH public key belonging to a user account. Useful for inspecting key details such as label, value, and creation date for a given user.

NameTypeReqDescription
key_idstringyesThe unique identifier (UUID) of the SSH key to retrieve.
selected_userstringyesThe user account to retrieve the SSH key from, specified as either an Atlassian Account ID or an account UUID wrapped in curly braces.

No output schema declared.

No examples provided.

get_workspace ~59

Retrieves details for a specific Bitbucket workspace. Returns workspace metadata including settings, links, and membership information.

NameTypeReqDescription
workspacestringyesThe unique identifier for the workspace, accepted as either a slug (short name) or a UUID wrapped in curly braces.

No output schema declared.

No examples provided.

get_workspace_member ~89

Retrieves the membership details for a specific user in a given workspace, including the full User and Workspace objects associated with that membership.

NameTypeReqDescription
memberstringyesThe unique identifier of the member to look up, either their UUID or Atlassian account ID.
workspacestringyesThe unique identifier of the workspace, either its slug (human-readable ID) or its UUID wrapped in curly braces.

No output schema declared.

No examples provided.

get_workspace_permission ~70

Retrieves the calling user's effective (highest) permission role for a specified workspace. If the user belongs to multiple groups with different roles, only the highest privilege level is returned.

NameTypeReqDescription
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces.

No output schema declared.

No examples provided.

get_workspace_pipeline_variable ~91

Retrieves a specific pipeline configuration variable at the workspace level by its UUID. Use this to inspect the details of a single workspace-scoped pipeline variable.

NameTypeReqDescription
variable_uuidstringyesThe unique identifier (UUID) of the workspace pipeline configuration variable to retrieve.
workspacestringyesThe 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.

get_workspace_runner ~87

Retrieves details for a specific Pipelines runner configured in a workspace. Useful for inspecting runner status, configuration, and metadata by its unique identifier.

NameTypeReqDescription
runner_uuidstringyesThe unique UUID identifying the runner to retrieve within the specified workspace.
workspacestringyesThe 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.

get_workspace_webhook ~86

Retrieves the details of a specific webhook installed on a workspace, identified by its unique ID. Useful for inspecting webhook configuration, events, and status for a given workspace.

NameTypeReqDescription
uidstringyesThe unique identifier of the installed webhook to retrieve.
workspacestringyesThe workspace identifier, either as a slug (short name) or a UUID surrounded by curly-braces.

No output schema declared.

No examples provided.

list_branch_restrictions ~140

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

NameTypeReqDescription
kindstringFilters results to only return branch restrictions of the specified type, such as push or merge restrictions.
patternstringFilters results to only return branch restrictions that apply to branches matching the specified pattern.
repo_slugstringyesThe repository slug or UUID identifying the target repository. UUID values must be surrounded by curly-braces.
workspacestringyesThe 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.

list_branches ~169

Retrieves all open branches for the specified repository, returned in the order the source control manager provides them. Supports filtering and natural sorting by branch name via query parameters.

NameTypeReqDescription
qstringA filter expression to narrow down the list of branches returned, following Bitbucket's filtering and sorting syntax.
repo_slugstringyesThe repository slug or UUID identifying the target repository. UUIDs must be surrounded by curly-braces.
sortstringThe field by which to sort the returned branches, following Bitbucket's filtering and sorting syntax. Sorting by name applies natural ordering so numerical segments are interpreted as numbers rather…
workspacestringyesThe 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.

list_commit_comments ~194

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

NameTypeReqDescription
commitstringyesThe full SHA1 hash identifying the specific commit whose comments should be retrieved.
qstringA query string to filter the returned comments using Bitbucket's filtering and sorting syntax, allowing you to narrow results by specific field conditions.
repo_slugstringyesThe repository slug or UUID that uniquely identifies the repository within the workspace. UUIDs must be surrounded by curly-braces.
sortstringThe field name by which to sort the returned comments, following Bitbucket's filtering and sorting syntax. Overrides the default oldest-to-newest ordering.
workspacestringyesThe workspace slug or UUID that uniquely identifies the workspace containing the repository. UUIDs must be surrounded by curly-braces.

No output schema declared.

No examples provided.

list_commit_pull_requests ~133

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

NameTypeReqDescription
commitstringyesThe full SHA1 hash of the commit whose associated pull requests should be retrieved.
pagelenstringThe number of pull requests to return per page; controls pagination page size.
repo_slugstringyesThe repository identifier, either the repository slug or the UUID enclosed in curly braces.
workspacestringyesThe workspace identifier, either the workspace slug or the UUID enclosed in curly braces.

No output schema declared.

No examples provided.

list_commit_report_annotations ~135

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

NameTypeReqDescription
commitstringyesThe full commit hash identifying the specific commit whose report annotations should be retrieved.
repo_slugstringyesThe repository slug (URL-friendly name) that uniquely identifies the repository within the workspace.
reportIdstringyesThe unique identifier of the report, accepted as either a UUID or an external ID, for which annotations will be listed.
workspacestringyesThe workspace identifier, either as a slug (short name) or as a UUID surrounded by curly braces.

No output schema declared.

No examples provided.

Common questions

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.