Bitbucket Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.0Updated Oct 24, 2026

Bitbucket repositories and users. No key required.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives an assistant access to Bitbucket repositories and users, with no API key required.

What you can do
Work with Bitbucket repositories and users through the assistant. The registry description names repositories and users as the scope, but no individual tools are listed, so the exact operations are not documented here. It runs as a local process over stdio.
When to use it
Consider it when you want an assistant to look at or work with Bitbucket repositories and user information from your own machine, and you prefer a setup that needs no key.
Requirements
Runs locally as an npm package over stdio, so Node.js and npm are needed on the machine. The manifest declares no authentication, environment variables or headers.
Before you install
No tools are listed, so what it can read or change in Bitbucket is unclear; check before pointing it at real repositories. The description says no key is required, but how it authenticates to Bitbucket is not documented.

Installation

In SourceWeft

  1. Open Bitbucket Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestSep 22, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.