Bitbucket MCP Server Cursor IDE Setup 2026

If your team uses Bitbucket for source control, the Bitbucket MCP server lets Cursor interact with your repos, branches, and pull requests without switching tabs. This guide walks through the complete setup for Cursor IDE in 2026.

What You Can Do With Bitbucket MCP

Once connected, Cursor can:

Read repository content — browse files, directories, and commit history

Manage pull requests — create PRs, read comments, check review status

Run pipeline status checks — see if builds are passing before suggesting merges

Create and switch branches — manage branching workflows from chat

Search code — find usages, patterns, and references across all repos

Read issues and tasks — pull context from Bitbucket Issues

Prerequisites

Cursor IDE 0.43+

A Bitbucket Cloud account (or Bitbucket Server/Data Center)

A Bitbucket App Password (for Cloud) or Personal Access Token (for Server)

Node.js 18+ installed

Step 1: Create a Bitbucket App Password

For Bitbucket Cloud:

1. Log in to bitbucket.org
2. Click your avatar → Personal settings
3. Go to App passwords → Create app password
4. Label it cursor-mcp-2026
5. Grant these permissions:

Repositories: Read, Write

Pull requests: Read, Write

Issues: Read

Pipelines: Read

6. Click Create and copy the password

Your workspace slug is visible in your Bitbucket URL: bitbucket.org/YOUR-WORKSPACE/

Step 2: Install the Bitbucket MCP Server

npm install -g bitbucket-mcp-server

Or use the community package:

npm install -g @modelcontextprotocol/server-bitbucket

Verify the install:

bitbucket-mcp-server --version

Step 3: Add to Cursor MCP Config

Open Cursor → Settings → MCP and add the Bitbucket server:

{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "bitbucket-mcp-server"],
      "env": {
        "BITBUCKET_USERNAME": "your-bitbucket-username",
        "BITBUCKET_APP_PASSWORD": "your-app-password-here",
        "BITBUCKET_WORKSPACE": "your-workspace-slug",
        "BITBUCKET_DEFAULT_REPO": "my-main-repo"
      }
    }
  }
}

BITBUCKET_DEFAULT_REPO is optional — it sets a default so you don't have to specify the repo on every request.

Restart Cursor to load the new config.

Step 4: Test the Connection

In Cursor chat, try:

List my Bitbucket repositories

Or:

Show me the open pull requests in the backend-api repo

A successful response with real data means you're connected.

Step 5: Practical Workflows

Code review assistance

Read PR #47 in the payments-service repo. Summarize the changes and flag any potential issues I should review before approving.

Pre-commit checks

Before I push this branch, check if there are any open PRs on main that might conflict with my changes to /src/billing/

Branch management

Create a new branch called feature/stripe-webhooks from main in the payments-service repo

Pipeline monitoring

What's the status of the last pipeline run on the main branch of payments-service?

Automated PR creation

I just finished the feature. Create a pull request from feature/stripe-webhooks to main with the title "Add Stripe webhook handling" and a description summarizing the changes in this diff

Bitbucket Server / Data Center Setup

If you're on Bitbucket Server (self-hosted), the config is slightly different:

{
  "mcpServers": {
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "bitbucket-mcp-server"],
      "env": {
        "BITBUCKET_TYPE": "server",
        "BITBUCKET_BASE_URL": "https://bitbucket.yourcompany.com",
        "BITBUCKET_TOKEN": "your-personal-access-token",
        "BITBUCKET_PROJECT_KEY": "PROJ"
      }
    }
  }
}

Personal Access Tokens on Bitbucket Server are found under Profile → Manage Account → Personal Access Tokens.

Combining Bitbucket With Jira and Confluence

Bitbucket, Jira, and Confluence are all part of the Atlassian ecosystem. With all three MCP servers configured, you can do powerful cross-tool workflows:

Find Jira ticket PROJ-892, read the spec in Confluence, check if there's already a branch for it in Bitbucket, and if not, create one called feature/PROJ-892

This is a workflow that normally requires 3 browser tabs. With all three MCP servers, Cursor handles it in one prompt.

See our guides for Jira MCP setup, Confluence MCP setup, and the combined Atlassian MCP bundle.

Troubleshooting

"Invalid credentials" error
Make sure you're using an App Password, not your account password. Account passwords don't work with the API.

"Repository not found"
Check your workspace slug matches exactly. It's case-sensitive in some configurations.

Pipelines not showing
Pipelines access requires the Pipelines: Read permission on your App Password. Recreate the password with that permission checked.

Slow responses on large repos
The MCP server paginates results. For repos with thousands of files or PRs, add a limit: "Show me the 5 most recent open PRs" rather than "show all open PRs."

Summary

The Bitbucket MCP server gives Cursor direct access to your source control workflow — creating branches, reading PRs, checking pipelines, and searching code across your workspace. Setup takes under 15 minutes.

For teams on the full Atlassian stack, pairing this with Jira and Confluence MCP servers creates a unified development context that makes AI assistance significantly more accurate and useful.