Bitbucket MCP. Manage Code Reviews, Builds, and Repositories.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Bitbucket MCP lets your agent manage Git repositories, code reviews, and CI/CD pipelines directly from any client. Check repository metadata, list pull requests, track commits, and monitor pipeline health without leaving your terminal or IDE.
What your AI agents can do
Get pull request
Fetches specific details about one pull request by its ID.
Get repository
Retrieves all metadata for a single, specified repository.
Get user profile
Pulls the account details of the user who is currently logged in and authenticated.
Get detailed information on specific code review requests and their merge status.
Retrieve core metadata for any specified repository within your workspace.
List recent commits or active branches across a project's codebase.
Check the success status and build history of Continuous Integration/Continuous Delivery pipelines.
Access and get details for all available team workspaces and user accounts.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 Compatible Gemini Waiting for input…
Bitbucket: 10 Tools for DevOps Management
Use these tools to retrieve specific metadata about repositories, pull requests, branches, commits, and pipelines in Bitbucket.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Bitbucket on Vinkius019d755dget pull request
Fetches specific details about one pull request by its ID.
019d755dget repository
Retrieves all metadata for a single, specified repository.
019d755dget user profile
Pulls the account details of the user who is currently logged in and authenticated.
019d755dlist branches
Generates a list of all active branches for a given repository.
019d755dlist commits
Retrieves a chronological listing of recent changes (commits) for a repository.
019d755dlist issues
Lists open or closed issues within a repository, provided the tracker is enabled.
019d755dlist pipelines
Gets a list of all CI/CD pipelines run for a specific repository.
019d755dlist pull requests
Shows an overview of pull requests associated with a given repository.
019d755dlist repositories
Lists every available repository within the user's workspace.
019d755dlist workspaces
Retrieves a list of all accessible team workspaces.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Bitbucket, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
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.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
The Dashboard Dash: Where everything lives and nothing moves.
Today, checking a project's status means bouncing between three separate areas. You start in the main repository view to check if anyone has opened a pull request; then you jump to the Pipelines tab to see if the code actually built; and finally, you might need to open an issue tracker just to confirm who needs to sign off on it. It's constant clicking and context-switching.
With this MCP, your agent handles that handoff for you. You don't have to know which tab or URL to hit. You simply ask the question—like 'Is PR #12 ready?'—and the agent runs all the necessary checks against Bitbucket’s tools and gives you a single, clear answer.
Bitbucket MCP: Get Immediate Visibility into Code Status
The tedious steps that disappear are the manual lookups. You don't need to run `git log` locally or manually navigate list_repositories just to confirm a project exists, nor do you have to open 10 tabs to check every active branch.
You get an immediate, unified status report on your entire codebase history and current development stage, all through one conversation. It's like having the whole Git dashboard available inside your chat window.
What you can do with this MCP connector
Managing a complex codebase means jumping between version control dashboards, issue trackers, and build logs. This MCP lets you handle that mess using natural conversation. You can ask your agent to check the status of a specific pull request, list all repositories in a workspace, or retrieve details about user profiles—all without switching tabs.
Want to know if a recent feature is ready for merge? Your agent pulls the necessary information from Bitbucket and gives you an immediate overview. It can also track down the latest commits across projects or even check the full status of CI/CD pipelines, telling you exactly when the last build succeeded or failed.
Because Vinkius runs every call in its own isolated sandbox, your credentials pass through a zero-trust proxy; they are used only for transit and never stored on disk.
This capability is huge for complex development teams. You can combine this MCP with others—say, chaining it with an issue tracking system to automatically create a ticket whenever a pull request stalls, or connecting it to a messaging tool to notify the team when a major pipeline fails. It turns your AI agent into a central dev operations command center.
019d755d-8a2b-7189-96d5-211526454ae3 
How Bitbucket MCP Works
- 1 Subscribe to this MCP, then provide your Bitbucket Username and App Password credentials.
- 2 Connect your agent from any compatible client like Cursor or Claude.
- 3 Start asking questions about your code: 'What's the status of PR #45?' or 'List all repos in my team workspace.'
The bottom line is, you get a single conversational interface to manage complex development data that used to require dozens of manual dashboard clicks.
Who Is Bitbucket MCP For?
The software engineer who gets stuck switching between code editors and web dashboards. The DevOps engineer tired of manually checking build logs at 2 AM. Any team lead needing a quick, accurate status report on multiple projects.
Quickly check if their feature branch has passed all required code reviews or if the latest commit was successfully integrated.
Monitor build statuses and repository activity across dozens of projects without writing complex shell scripts or clicking through multiple web interfaces.
Pull a summary report on open issues, recent commits, and PR bottlenecks for daily standups in seconds.
What Changes When You Connect
- Check PR status instantly. Instead of navigating to a dedicated tab, you ask your agent for the details of a pull request, getting immediate feedback on its merge readiness.
- Get a full project picture. You can list all available repositories in a workspace and then check the specific metadata for any one of them using get_repository.
- Stay ahead of deployments. Your agent pulls the status of Bitbucket Pipelines, telling you if Build #452 succeeded or failed without you needing to click into the CI/CD dashboard.
- Track changes easily. Use list_commits to pull the last five updates for a project and immediately see who made what change, perfect for quick team syncs.
- Coordinate your team better. You can use list_issues alongside other tools to find out exactly which bugs are open in a repo before starting development.
Real-World Use Cases
The Merge Conflict Check
A developer needs to know if their feature branch is ready. They ask the agent, and it uses list_pull_requests and get_repository to confirm there are no open review comments or blocking issues.
Post-Failure Diagnosis
The DevOps engineer sees a build fail. Instead of logging into Bitbucket Pipelines, they ask the agent, which uses list_pipelines to find the failed run and checks its logs for the root cause.
New Team Onboarding
A new team member needs context on all active projects. They simply ask the agent to use list_workspaces, getting an overview of every accessible team area immediately.
The Tradeoffs
Listing everything manually
Having to open Bitbucket and click through: Repositories tab -> Select Repo -> Pipelines tab -> View Builds.
→ Just tell your agent to list all repositories, then ask it to check the latest pipeline for 'my-app'. It handles the navigation automatically.
Forgetting context
Asking about a commit without specifying which repository or branch you mean.
→ Always specify. Ask the agent to list_commits for the specific repo and branch name, giving it all the necessary context up front.
Ignoring dependencies
Assuming that a pull request is ready just because the code compiles.
→ Ask the agent to get_pull_request details. It checks not only the commit status but also if all required reviewers have signed off.
When It Fits, When It Doesn't
Use this MCP if your workflow requires coordinating actions across multiple development stages: from listing workspaces and repositories, through managing pull requests, and finally checking build pipelines. You need a single point of access to the entire lifecycle—the code review part, the commit history part, and the deployment status part. Don't use it if you just need simple version control viewing; for that, basic Git CLI commands are faster. If your goal is solely managing user accounts or team structure, consider an identity management tool instead.
Common Questions About Bitbucket MCP
Can I check the status of my latest Bitbucket Pipeline? +
Yes! Use the list_pipelines tool with your Workspace and Repository slug. Your agent will fetch the latest build statuses, showing if they passed or failed.
How do I list all open pull requests for a repository? +
Simply ask the agent to list_pull_requests and provide the Workspace and Repository slug. It will retrieve all current PRs awaiting review.
Does the integration allow merging code directly? +
Currently, the toolset is focused on querying and monitoring (Read-Only). You can list and inspect PRs, commits, and branches, but destructive actions like merging or deleting branches must be done through the Bitbucket UI for safety.
When using `get_user_profile`, what specific permissions does my agent need, and how are those credentials managed? +
Your agent needs read-level access for profile data. Vinkius handles this securely by passing your Bitbucket App Password through a zero-trust proxy; the key never sits on disk.
If I run `list_issues` but the repository doesn't have an issue tracker enabled, what should the agent report? +
The agent will return a specific error message detailing that tracking is not configured. You must enable the issue tracker within Bitbucket before running list_issues.
If I use `get_pull_request` and hit an API rate limit, does the connection handle retrying the request? +
Yes, the MCP layer manages standard API throttling. If your agent hits a rate limit, it automatically pauses and retries the call after a short delay without needing manual intervention.
When I use `list_repositories`, does the scope of my search cover all workspaces, or only one? +
The initial step is to run list_workspaces to see everything accessible. After that, you can narrow your focus and list repositories across multiple workspaces from a single prompt.
If I use `list_commits`, does the output automatically tell me which branch each commit belongs to? +
No. You first need to run list_branches for the target repository. Then, your agent combines that branch list with the commits data to give you a complete picture.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.