How to Use the Bitbucket MCP in Cursor

Q: How do I configure Cursor to work with my Bitbucket repositories?

Create a .cursor/mcp.json file in your project root and add the MCP server config. Once saved, Cursor's agent mode can query listrepositories to index your workspace.

Q: Can Cursor trigger a Bitbucket pipeline build?

No, but the agent can read status data. It runs listpipelines to display the current build state of your Bitbucket repository right inside the editor.

Write code in Cursor with live context from your Bitbucket repositories, pull requests, and active branches.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Bitbucket MCP to Cursor

Create your Vinkius account to connect Bitbucket to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Bitbucket with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Build features using real Bitbucket context in Cursor

This Bitbucket MCP Server injects live repository data directly into Cursor's agent mode. The Cursor editor runs `get_repository` and `list_branches` to read your actual Bitbucket file structure instead of guessing. You get code completions in Cursor based on actual Bitbucket branch history. Cursor invokes `list_commits` to see what your teammates pushed to Bitbucket before generating matching code.

Review pull requests right inside the Cursor editor

You can inspect open Bitbucket pull requests while working in your active Cursor workspace using this MCP integration. The Cursor editor calls `list_pull_requests` to fetch the queue and `get_pull_request` to pull down specific Bitbucket review comments. This means you can fix requested changes in Cursor without switching back to a browser. The agent updates your files based on the exact feedback stored in Bitbucket.

Check pipeline status before you commit in Cursor

Your Cursor editor tracks active Bitbucket CI/CD pipelines directly through tool calls. By running `list_pipelines`, the Cursor agent checks if your last push broke the build. If things go sideways, the Cursor agent queries `list_issues` to see if there is an existing Bitbucket bug report. You can patch the bug and push a fix without leaving the Cursor interface.

Setup guide

Set up Bitbucket MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Bitbucket MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Bitbucket transactions." If the MCP tools are loaded correctly, Cursor will call the Bitbucket tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "bitbucket-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Bitbucket. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Bitbucket now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Bitbucket MCP in Cursor

Create a `.cursor/mcp.json` file in your project root and add the MCP server config. Once saved, Cursor's agent mode can query `list_repositories` to index your workspace.

No, but the agent can read status data. It runs `list_pipelines` to display the current build state of your Bitbucket repository right inside the editor.

Yes, the MCP connection uses your authenticated credentials to run `list_workspaces`. This lets Cursor access both public and private codebases you have permission to view.

You ask the editor to refresh the pull request details. It runs `get_pull_request` again to pull the latest comments directly into your active Cursor session.

No, all API calls to your Bitbucket repositories run locally through the server. Your code and commit messages are sent straight to your Cursor client, never cached on Vinkius.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript