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 24, so disable the ones you do not use if you are running several servers at once.
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.
- Pull-request context handed to the model, so it can read and review a PR rather than being told about it
- 24 tools in total, according to the project's own count
- 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
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.