LabscoMCP early access ↗
jliocsarMCP SERVER

Bitbucket MCP Server

Puts Bitbucket pull requests in front of an LLM so it can read the diff and review context itself, from a local binary you point at your workspace.

by jliocsar ↗Git Hosting & Code ReviewCommunity

LABSCO SUMMARY

Pull requests, and the author says so.

The README calls this a learning exercise and a work in progress, and scopes it to mostly pull requests — take that at face value when planning around it. One practical note it raises: clients cap how many tools reach the agent, and this server alone brings 30 in its current source (the README says 24), so disable the ones you do not use if you are running several servers at once.

What it is

A Bun-based MCP server focused on pull requests in Bitbucket. It authenticates with a username and app password passed as a launch argument, and runs locally as a binary or straight from source.

What you get

  • Pull-request context handed to the model, so it can read and review a PR rather than being told about it
  • 30 tools in the source — pull requests with their diffs, comments, tasks and statuses, plus pipelines, issues, commits, snippets and code search (the README still says 24)
  • A prebuilt binary per release, so there is nothing to compile if you do not want to
  • The MCP Inspector wired up for browsing and calling the tools interactively before you commit to a client config

Requirements

Either a release binary extracted somewhere on disk, or Bun installed with bun i in the cloned repo. Your client config runs the binary — or bun run against src/index.civet — with username:password as the single argument. Written in Bun and Civet; contributing means installing the Civet editor extension as well.

Setup effort

Follow the published steps

See installation options