MCP server for Atlassian Bitbucket Data Center - interact with repositories and code
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.
BITBUCKET_API_TOKENAPI keyoptionalBitbucket Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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.
bitbucket_getProjectsNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getProjectNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getRepositoriesNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getRepositoryNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getCommitsNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getPullRequestsNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getPullRequestNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getPR_CommentsAndActionNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getPullRequestChangesNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getUserNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_postPullRequestCommentNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_updatePullRequestCommentNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_submitPullRequestReviewNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getPullRequestDiffNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_createPullRequestNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_updatePullRequestNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getRequiredReviewersNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getInboxPullRequestsNo description publishedThis tool published no description. Forge does not invent one.
bitbucket_getDashboardPullRequestsNo description publishedThis tool published no description. Forge does not invent one.
0 of 19 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.
MCP server for Atlassian Bitbucket Data Center - interact with repositories and code
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This package was last scanned before Forge began storing the resolved tree. The next scan will record it.