npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

bitbucket-cloud-mcp-server

v1.3.0

Published

A Model Context Protocol server for Bitbucket Cloud repositories, pull requests, commits, and reviews.

Readme

Bitbucket Cloud MCP Server

npm version

A Model Context Protocol (MCP) server that lets MCP-compatible AI clients work with Bitbucket Cloud repositories, pull requests, commits, comments, approvals, and merges.

Features

  • List repositories in a Bitbucket workspace
  • List, inspect, create, update, approve, merge, and comment on pull requests
  • Fetch pull request metadata, commits, comments, and diff content for reviews
  • List repository commits
  • Read-only annotations on safe exploration tools
  • Runs over MCP stdio for clients such as Claude Desktop, Cursor, Kiro, and MCP Inspector

Requirements

  • Node.js 18 or newer
  • A Bitbucket Cloud workspace
  • A Bitbucket API token or app password with repository and pull request access

Installation

Run without installing:

npx bitbucket-cloud-mcp-server

Or install globally:

npm install -g bitbucket-cloud-mcp-server
bitbucket-cloud-mcp-server

Configuration

Set these environment variables in your MCP client configuration:

| Variable | Description | | --- | --- | | BITBUCKET_WORKSPACE | Bitbucket workspace slug | | BITBUCKET_EMAIL | Atlassian account email | | BITBUCKET_TOKEN | Bitbucket API token or app password |

Example:

{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "bitbucket-cloud-mcp-server"],
      "env": {
        "BITBUCKET_WORKSPACE": "my-workspace",
        "BITBUCKET_EMAIL": "[email protected]",
        "BITBUCKET_TOKEN": "my-api-token"
      }
    }
  }
}

If you installed the package globally, you can use the binary directly:

{
  "mcpServers": {
    "bitbucket": {
      "command": "bitbucket-cloud-mcp-server",
      "env": {
        "BITBUCKET_WORKSPACE": "my-workspace",
        "BITBUCKET_EMAIL": "[email protected]",
        "BITBUCKET_TOKEN": "my-api-token"
      }
    }
  }
}

Verify Credentials

Before running the MCP server, verify Bitbucket access:

curl -u "[email protected]:my-api-token" \
  "https://api.bitbucket.org/2.0/repositories/my-workspace"

A successful response returns repository information for the workspace.

Tools

list_repositories

Lists repositories in the configured workspace.

Input:

{
  "includePrivate": true
}

list_pull_requests

Lists pull requests for a repository.

Input:

{
  "repo": "my-repository"
}

get_pull_request

Gets pull request details.

Input:

{
  "repo": "my-repository",
  "id": 123
}

review_pull_request

Returns pull request metadata, commits, existing comments, and diff content for review.

Input:

{
  "repo": "my-repository",
  "id": 123
}

create_pull_request

Creates a pull request.

Input:

{
  "repo": "my-repository",
  "title": "Add authentication",
  "source": "feature/auth",
  "destination": "main",
  "description": "Adds login functionality"
}

update_pull_request

Updates an existing pull request's title, description, destination branch, or reviewers. All fields are optional — only provided fields are updated.

Input:

{
  "repo": "my-repository",
  "id": 123,
  "title": "Updated title",
  "description": "Updated description",
  "destination": "develop",
  "reviewers": ["{user-uuid-1}", "{user-uuid-2}"]
}

approve_pull_request

Approves a pull request.

Input:

{
  "repo": "my-repository",
  "id": 123
}

Bitbucket may prevent users from approving their own pull requests depending on repository settings.

merge_pull_request

Merges a pull request.

Input:

{
  "repo": "my-repository",
  "id": 123
}

comment_pull_request

Adds a comment to a pull request. Optionally provide filePath and line to make it an inline comment on a specific line in the diff.

General comment:

{
  "repo": "my-repository",
  "id": 123,
  "comment": "Looks good to me."
}

Inline comment on a specific file and line:

{
  "repo": "my-repository",
  "id": 123,
  "comment": "Consider renaming this variable.",
  "filePath": "src/index.ts",
  "line": 42
}

request_changes

Requests changes on a pull request, signaling the author needs to address feedback.

Input:

{
  "repo": "my-repository",
  "id": 123
}

list_commits

Lists commits for a repository.

Input:

{
  "repo": "my-repository"
}

Development

Install dependencies:

npm install

Run in development mode:

npm run dev

Build:

npm run build

Preview the npm package contents:

npm run pack:dry-run

Publishing

The unscoped bitbucket-mcp package name is already used on npm, so this package is configured as bitbucket-cloud-mcp-server.

Before publishing, confirm you are logged in:

npm whoami

Then publish:

npm publish --access public

The prepublishOnly script rebuilds dist before publishing.

License

ISC