The official Svelte MCP server providing docs and autofixing tools for Svelte development
Nothing to run from here
Bitbucket Dc 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.
94/100
trust score
29
tools declared
local
runs on your machine
—
downloads a day
What it does
MCP server for Bitbucket Data Center and Bitbucket Server
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user tekthar-bitbucket-dc-mcp '--' npx -y mcp-bitbucket-dc
# 2 — ask your agent for something these tools do
# bitbucket_getProjects, bitbucket_getProject, bitbucket_getRepositories and 26 more
Bitbucket Dc costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
TEAll 3 servers
tekthar3 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 Bitbucket Dc 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 tekthar-bitbucket-dc-mcp '--' npx -y mcp-bitbucket-dcReconnect, 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 (Absolute path to a shared dotenv-style config file. When set, values are read from this file before direct environment variable overrides are applied.), BITBUCKET_HOST (Bitbucket host domain (e.g. your-instance.atlassian.net). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or BITBUCKET_API_BASE_PATH.), BITBUCKET_API_BASE_PATH (Bitbucket API base path (alternative to BITBUCKET_HOST). Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE or BITBUCKET_HOST.), BITBUCKET_API_TOKEN (Bitbucket Personal Access Token or API token. Required unless provided through ATLASSIAN_DC_MCP_CONFIG_FILE.) 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
29 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
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 complete source file without cloning the repository. 'at' defaults to the repository's default branch. Pointing 'path' at a directory returns that directory's unpaginated git tree listing. For…
No parameter schema on file.
Browse a Bitbucket repository at a branch, tag or commit using structured, paginated responses. Omit 'path' to list the repository root. Directory pagination is under 'children'; file pagination is at the response root. Continue with the corresponding 'nextPageStart' when 'isLastPage' is false.…
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's 'id' (e.g. 'refs/heads/feature/my-branch'), which is what bitbucket_createPullRequest…
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 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.
Post a comment to a Bitbucket pull request. Use pending: true to create a draft comment that is only visible to you until you call bitbucket_submitPullRequestReview. NOTE: pending only works when filePath is provided (file-level or inline comments). True top-level PR comments (no filePath) are…
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: 'RESOLVED' ticks the task; threadResolved: true toggles the thread-level 'Resolve' button. These are independent and can be set…
No parameter schema on file.
Submit a pull request review, publishing all pending (draft) comments and setting the reviewer's verdict. This is equivalent to clicking 'Submit Review' in the Bitbucket UI. Use after posting comments with pending: true. To resolve userSlug: (1) check author.slug in any comment you posted this…
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 'compare' view: changes reachable from sourceBranch but not from targetBranch, rendered as a unified diff. targetBranch defaults to the repository's…
No parameter schema on file.
Create a new pull request in a Bitbucket repository. Supports fork-based pull requests by passing fromProjectKey/fromRepositorySlug when the source repository differs from the destination (projectKey/repositorySlug). IMPORTANT: Before creating a PR, use bitbucket_getRequiredReviewers to fetch…
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 'version' number — this is required for optimistic locking and the call will fail without it. Omit reviewers to keep…
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.
Get the CI/CD build statuses of a pull request — the builds, jobs or pipelines that any CI server integrated with Bitbucket (Jenkins, Bamboo, TeamCity or any other tool posting build statuses) reported on the latest commit of its source branch, as shown in the pull request's Builds panel. Use it…
No parameter schema on file.
Merge a pull request. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current 'version' — it is required for optimistic locking and a stale version is rejected. The merge is refused if the pull request is conflicted or a merge check vetoes it; use bitbucket_canMergePullRequest…
No parameter schema on file.
Decline (close without merging) a pull request. IMPORTANT: you MUST first call bitbucket_getPullRequest to get the current 'version' — it is required for optimistic locking and a stale version is rejected. Pass the reason as 'comment' so it is posted with the decline in a single request. Reviewers…
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 'version' — it is required for optimistic locking and a stale version is rejected. The pull request must be in the DECLINED state; anything else is refused.
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's inbox that need their review. Returns PRs across all repositories where the user is a reviewer.
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. Scope and filter inside the query text with modifiers like 'project:<key>', 'repo:<key>/<slug>', 'path:<glob>', 'lang:<language>' and 'ext:<extension>', separated from the search term by a space (e.g. 'authenticate project:TEST', 'TODO repo:TEST/demo ext:js'). NOTE:…
No parameter schema on file.
Get comments for a Bitbucket pull request and other actions, like approvals
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 Bitbucket Dc 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 94 / 100
Release 0.47.1 · scanned 7 Nov 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 score94
Findings2 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationsource
Surface digestdd48634162342f088e0ebdb36912ce97f7d37d2a34b76efecaf0611952b8579b
Score vectorthreat 100 → client 94
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| 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 (29 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>".
1 of the 29 recovered tools are registered only when mergeGateway.enabled holds (dist/index.js:215) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 27.
1 of the 29 recovered tools are registered only when declineGateway.enabled holds (dist/index.js:235) — typically when a key or option is configured. They are part of the server's surface and were analysed; a server started without that configuration exposes only the other 27.
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. high is the level these add up to.
27 tools are registered unconditionally · (1) 1 more only when mergeGateway.enabled holds (dist/index.js:215) · (2) 1 more only when declineGateway.enabled holds (dist/index.js:235) — typically when a key or option is configured. All 29 are in the table below and were analysed; the conditional ones are marked.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| bitbucket_getPR_CommentsAndAction | no tags | |
| bitbucket_getProjects | no tags | |
| bitbucket_getProject | no tags | |
| bitbucket_getRepositories | no tags | |
| bitbucket_getRepository | no tags | |
| bitbucket_getFileContent | no tags | |
| bitbucket_browseRepository | untrusted-input | untrusted-input: keyword "browse" |
| bitbucket_createBranch | no tags | |
| bitbucket_getCommits | no tags | |
| bitbucket_getPullRequests | no tags | |
| bitbucket_getPullRequest | no tags | |
| bitbucket_getPullRequestChanges | no tags | |
| bitbucket_getUser | no tags | |
| bitbucket_postPullRequestComment | no tags | |
| bitbucket_updatePullRequestComment | untrusted-input | untrusted-input: keyword "fetch" |
| 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_getPullRequestBuilds | no tags | |
| bitbucket_mergePullRequest conditional (1) | no tags | |
| bitbucket_declinePullRequest conditional (2) | 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 digestdd48634162342f08
Scanned2026-11-07
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.47.1. Pin a release below and the command asks for exactly that one.
0.47.1
undated
latestNo release note was published with this version.
—
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 Bitbucket Dc 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.