The official Svelte MCP server providing docs and autofixing tools for Svelte development
Nothing to run from here
Atlassian Dc Bitbucket is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
97/100
trust score
84
downloads a day
local
runs on your machine
12k
downloads in 30d
What it does
MCP server for Atlassian Bitbucket Data Center - interact with repositories and code
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user b1ff-atlassian-dc-bitbucket-mcp '--' npx -y @atlassian-dc-mcp/bitbucket
# 2 — ask your agent for something these tools do
# bitbucket_getProjects, bitbucket_getProject, bitbucket_getRepositories and 24 more
Atlassian Dc Bitbucket costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
B1All 3 servers
b1ff3 servers
3 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Atlassian Dc Bitbucket as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user b1ff-atlassian-dc-bitbucket-mcp '--' npx -y @atlassian-dc-mcp/bitbucketReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
Nothing is required, but it can take ATLASSIAN_DC_MCP_CONFIG_FILE, BITBUCKET_HOST, BITBUCKET_API_BASE_PATH, BITBUCKET_API_TOKEN if you want to set them.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
27 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Get a list of Bitbucket projects
No parameter schema on file.
Get a specific Bitbucket project by key
No parameter schema on file.
Get repositories for a Bitbucket project
No parameter schema on file.
Get a specific Bitbucket repository
No parameter schema on file.
Get the raw content of a file in a Bitbucket repository, at a branch, tag or commit. Use this to read a source file without cloning the repository.
No parameter schema on file.
Create a branch in a Bitbucket repository, forked from a branch, tag or commit. Use this before bitbucket_createPullRequest when the source branch does not exist yet. The response contains the new branch
No parameter schema on file.
Get commits for a Bitbucket repository
No parameter schema on file.
Get pull requests for a Bitbucket repository
No parameter schema on file.
Get a specific pull request by ID. Returns full details including title, description, reviewers, participants, author, source/target branches, current state, and version (needed for bitbucket_updatePullRequest).
No parameter schema on file.
Get comments for a Bitbucket pull request and other actions, like approvals
No parameter schema on file.
Get the changes for a Bitbucket pull request
No parameter schema on file.
Get a Bitbucket user by their slug, or search for users by name/email to discover their slug. Use this to resolve userSlug for bitbucket_submitPullRequestReview when it is not already known from a comment response or PR participant list.
No parameter schema on file.
No parameter schema on file.
Update an existing pull request comment. Use to edit text, change severity, change task state, or resolve/reopen the comment thread. On a BLOCKER (task) comment, state:
No parameter schema on file.
Submit a pull request review, publishing all pending (draft) comments and setting the reviewer
No parameter schema on file.
Get text diff for a specific file in a Bitbucket pull request. Returns plain text diff format. Note: Before getting diff, use getPullRequestChanges to understand what files were changed in the PR
No parameter schema on file.
Get the diff between two branches, tags or commits — including branches that have no pull request yet. Returns the same comparison as the Bitbucket
No parameter schema on file.
No parameter schema on file.
Update the title, description, reviewers, destination branch or draft status of an existing pull request. IMPORTANT: You MUST first call bitbucket_getPullRequest to get the current
No parameter schema on file.
Check whether a pull request can be merged. Read-only: returns canMerge, whether the pull request is conflicted, and any merge-check vetoes (e.g. missing approvals, unresolved tasks, failed builds). Use this before bitbucket_mergePullRequest to see what is blocking a merge.
No parameter schema on file.
Merge a pull request. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current
No parameter schema on file.
Decline (close without merging) a pull request. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current
No parameter schema on file.
Reopen a declined pull request, restoring it to OPEN. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current
No parameter schema on file.
Get required reviewers for pull request creation. Returns a set of users who are required reviewers for pull requests created from the given source repository and ref to the given target ref in this repository.
No parameter schema on file.
Get pull requests from the authenticated user
No parameter schema on file.
Get pull requests from the Bitbucket dashboard across all repositories. Useful for finding all PRs where you are the author, reviewer, or participant without specifying a project or repository.
No parameter schema on file.
Search code across Bitbucket. The query supports search modifiers like
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Atlassian Dc Bitbucket or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 97 / 100
Release 0.35.0 · scanned 6 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score97
Findings1 threat · 0 capability
Capabilitymoderate
Coveragesource
Verificationsource
Surface digest1bf8886471cdbd7fe070e6120ce33e76894a06cb1b38a989237fd4b0c5d3dd97
Score vectorthreat 100 → client 97
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | moderate | capability blast radius (moderate) — client exposure if the model is manipulated | −3 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (27 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. moderate is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bitbucket_getProjects | no tags | |
| bitbucket_getProject | no tags | |
| bitbucket_getRepositories | no tags | |
| bitbucket_getRepository | no tags | |
| bitbucket_getFileContent | no tags | |
| bitbucket_createBranch | no tags | |
| bitbucket_getCommits | no tags | |
| bitbucket_getPullRequests | no tags | |
| bitbucket_getPullRequest | no tags | |
| bitbucket_getPR_CommentsAndAction | no tags | |
| bitbucket_getPullRequestChanges | no tags | |
| bitbucket_getUser | no tags | |
| bitbucket_postPullRequestComment | no tags | |
| bitbucket_updatePullRequestComment | no tags | |
| bitbucket_submitPullRequestReview | no tags | |
| bitbucket_getPullRequestDiff | no tags | |
| bitbucket_getBranchDiff | no tags | |
| bitbucket_createPullRequest | untrusted-input | untrusted-input: keyword "fetch" |
| bitbucket_updatePullRequest | no tags | |
| bitbucket_canMergePullRequest | no tags | |
| bitbucket_mergePullRequest | no tags | |
| bitbucket_declinePullRequest | no tags | |
| bitbucket_reopenPullRequest | no tags | |
| bitbucket_getRequiredReviewers | no tags | |
| bitbucket_getInboxPullRequests | no tags | |
| bitbucket_getDashboardPullRequests | no tags | |
| bitbucket_searchCode | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digest1bf8886471cdbd7f
Scanned2026-10-06
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.35.0. Pin a release below and the command asks for exactly that one.
0.35.0
22 Sep 2026
latestNo release note was published with this version.
0.34.0
undated
- The version this listing was on when mcprush began following its releases. The registry was not asked when it shipped, so this row carries no date.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Atlassian Dc Bitbucket can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.