@droplinkperformance/bitbucket-mcp-server

MCPcommunity
v1.2.0io.github.droplinkperformanceUnknownUpdated 1mo agonpmGitHub

Provider-agnostic, AI-review-first MCP server for Bitbucket Cloud.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
1mo agoLast update
Needs 1 credential before it runs
  • BITBUCKET_ACCESS_TOKENAPI keyrequired

    Bitbucket API token (ATATT), app password, or OAuth access token

  • OPENAI_API_KEYAPI keyoptional

    OpenAI API key when LLM_PROVIDER is openai

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.droplinkperformance
LicenseUnknown
Version1.2.0
Sourcenpm+mcp-registry
npm@droplinkperformance/bitbucket-mcp-server
GitHubdroplinkperformance/bitbucket-mcp-server
SBOMCycloneDX 1.6 ↓
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface9 tools · none privileged
Security scan✓ Cleanv1.2.0 · 28d agoHow well does this scan work?
EvalsNone
IndexedAug 26, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

9 tools · none privileged
Statically extracted from the published packagev1.2.0 · 28d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

analyze_pull_requestRuns an AI code review of a pull request and returns a standard ReviewResult (summary,

Runs an AI code review of a pull request and returns a standard ReviewResult (summary,

No input schema was published for this tool.

comment_pull_requestAdds a comment to a pull request. Provide `inline` to attach the comment to a file/line.

Adds a comment to a pull request. Provide `inline` to attach the comment to a file/line.

No input schema was published for this tool.

get_pull_request_commentsLists the (non-deleted) comments on a pull request.

Lists the (non-deleted) comments on a pull request.

No input schema was published for this tool.

create_pull_requestCreates a pull request from a source branch to a destination branch.

Creates a pull request from a source branch to a destination branch.

No input schema was published for this tool.

get_pull_request_diffReturns the raw unified diff for a pull request.

Returns the raw unified diff for a pull request.

No input schema was published for this tool.

get_pull_request_filesLists the files changed by a pull request with add/remove line stats.

Lists the files changed by a pull request with add/remove line stats.

No input schema was published for this tool.

get_current_userReturns the authenticated Bitbucket user.

Returns the authenticated Bitbucket user.

No input schema was published for this tool.

get_pull_requestFetches a single pull request by id.

Fetches a single pull request by id.

No input schema was published for this tool.

list_pull_requestsLists pull requests in a repository, optionally filtered by state or a query.

Lists pull requests in a repository, optionally filtered by state or a query.

No input schema was published for this tool.

9 of 9 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Provider-agnostic, AI-review-first MCP server for Bitbucket Cloud.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Tools exposed

9 tools · none privileged · observed by static extraction. A tool surface is what one scan read on one day, not a live capability list.

Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-15 — observed resolution, not a publisher declaration.

60 packages resolved · 4 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

65 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+53 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.

Topics

Related in git & code hosting