Bitbucket MCP. Manage code reviews, commits, and pipelines from chat.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Bitbucket. Manage your entire Git workflow directly from any AI client. List repositories, check pull request status, track commits, and monitor CI/CD pipelines without leaving your chat window.
Get deep metadata on your code base—all the information you need to speed up reviews and deployments.
What your AI agents can do
Get pull request
Gets full details for a specific pull request.
Get repository
Gets all metadata about one specific repository.
Get user profile
Fetches the profile information for the authenticated user.
Retrieves metadata for a specific Bitbucket repository.
Gets all details for one specific pull request.
Retrieves a list of pull requests for a given repository.
Retrieves a chronological list of commits for a repository.
Retrieves the build status and history of Bitbucket Pipelines.
Lists all active branches associated with a repository.
Retrieves a list of tracked issues linked to a repository.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Bitbucket MCP Server: 10 Tools for Dev Workflow
Use these tools to pull structured data from Bitbucket, allowing your AI agent to manage everything from repo discovery to final pipeline status.
019d755dget pull request
Gets full details for a specific pull request.
019d755dget repository
Gets all metadata about one specific repository.
019d755dget user profile
Fetches the profile information for the authenticated user.
019d755dlist branches
Lists every branch associated with a repository.
019d755dlist commits
Lists recent commits for a repository.
019d755dlist issues
Lists issues linked to a repository, provided the tracker is enabled.
019d755dlist pipelines
Lists and checks the status of CI/CD pipelines.
019d755dlist pull requests
Lists multiple pull requests for a repository.
019d755dlist repositories
Lists all repositories within a workspace.
019d755dlist workspaces
Lists every workspace you have access to.
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,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ 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
What you can do with this MCP connector
Yo, you connect your Bitbucket account to any AI client and you manage your whole Git workflow straight up from your chat. You don't even gotta leave your chat window to check your code. You can list all your workspaces and all your repos. You can get the full metadata on any specific repo.
You'll also see every branch attached to a repo. You can list recent commits for a repo. You can list all the PRs for a repo, or you can get the full details on one specific pull request. You can check the status and history of your CI/CD pipelines. You can list all issues tied to a repo, provided they've got a tracker set up.
You can list all repos in a workspace and list all workspaces you've got access to.
How Bitbucket MCP Works
- 1 Subscribe to the Bitbucket MCP Server and provide your Bitbucket credentials (Username and App Password).
- 2 Prompt your AI client with a request, like 'List all open pull requests for my-app'.
- 3 Your agent calls the appropriate tool (e.g.,
list_pull_requests) and returns the structured data to your chat for immediate review.
The bottom line is, you tell your agent what code status you need, and it fetches the data directly from Bitbucket, skipping the UI clicks.
Who Is Bitbucket MCP For?
This is for the software engineer who spends half a day switching between the Git UI, the CI/CD dashboard, and the issue tracker. It's for the DevOps engineer tired of manual status checks and the team lead who needs a daily summary of commits and PRs without opening a browser. It puts all that context into your chat.
Checks the status of pull requests and monitors pipeline health immediately after pushing code.
Gets repository metadata and monitors build statuses straight from their workflow tools, minimizing context switches.
Retrieves summaries of recent commits and open issues for daily standups or project reporting.
What Changes When You Connect
- Accelerated Reviews: Use
list_pull_requestsandget_pull_requestto instantly see the status and details of any code review. No more jumping to the PR tab to check if it's ready to merge. - Centralized Monitoring:
list_pipelinesdelivers the build status directly. You get to know instantly if a deployment failed or passed without opening the CI/CD dashboard. - Full Code History:
list_commitsgives you the last 50 commits and what they touched. You maintain a precise, immediate history log without opening the Git log UI. - Scope Visibility:
list_repositoriesandlist_workspacesshow you everything you're working with. You know exactly which code base is where. - Issue-Code Linkage:
list_issueslinks development tasks directly to the code. You see that commit SHA X was made to address issue Y. - User Context:
get_user_profileconfirms who's running the check. This is useful when auditing or verifying permissions.
Real-World Use Cases
Debugging a Broken Feature Branch
A developer pushes code but the build fails. Instead of manually checking the CI/CD dashboard, they ask their agent: 'Check the latest pipeline for my-app.' The agent runs list_pipelines, confirms the build failed, and provides the failure status immediately.
Daily Standup Prep
A team lead needs a quick update on what's ready to merge. They prompt the agent to run list_pull_requests for the main project. The agent compiles a list of open PRs and their titles, saving the team lead from opening the web UI.
Auditing Code Changes
An engineer needs to know who changed a specific file last week. They ask the agent to run list_commits for the repo. The agent returns the top 10 commits, showing the user the author and commit message for quick auditing.
Finding the Right Repo
A new team member needs to know which repositories exist in their department's scope. They ask the agent to use list_workspaces and then list_repositories, getting a clear, structured list of all available code bases.
The Tradeoffs
Manual UI Navigation
Opening the Bitbucket web UI, clicking into the repo, then navigating to the Pipelines tab, and finally filtering commits by date. This takes 4-5 minutes and requires multiple context switches.
→
Ask your agent to run list_pipelines or list_commits. The data appears instantly in your chat. You get the build status or the commit list without ever leaving your workflow tool.
Guessing Commit History
Running a manual Git command line search to find who touched a file three months ago, requiring remembering complex SHA hashes and branch names.
→
Use list_commits and specify the date range or file path. The agent runs the tool and gives you the clean list of changes and authors you need.
Ignoring Linked Issues
Seeing a PR is ready to merge, but not knowing which bug ticket it addresses. The developer has to open the issue tracker and manually cross-reference IDs.
→
Ask the agent to run list_issues alongside list_pull_requests. This connects the issue ID directly to the PR, making the link explicit.
When It Fits, When It Doesn't
Use this server if your workflow involves constantly cross-referencing data across multiple Bitbucket areas: PRs, commits, issues, and pipelines. You need to know the status of a feature (is it merged? did the build pass? is the issue closed?) without opening a browser. Don't use it if you just need to read a single, static piece of information, like a repo name—your native Bitbucket UI works fine for that. If you need to know the relationship between a bug (Issue X) and the code fix (Commit Y), this is the only way to automate that context linking.
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.
Available Capabilities
Jumping between tabs to check code status is a massive time sink.
Right now, checking if a PR is ready to merge means clicking into the Bitbucket web app. You check the PR details, then you jump to the Pipelines tab to see if the last build passed. Then you might switch to the Issues section to confirm the linked ticket is closed. It's a multi-tab, multi-click chore that breaks your focus.
With this MCP server, you just talk to your agent. You ask, 'Is PR 12 ready to merge?' Your agent runs `get_pull_request` and gives you the full status—merge status, pipeline status, and linked issue details—all in one reply. It's instant, and it keeps you in your flow.
Bitbucket MCP Server: See PR status and pipeline health instantly.
The manual process involves checking the repository UI for the PR status, then navigating to the Pipelines dashboard to see if the associated build is green. This requires keeping track of three different pages and their timestamps.
Now, your agent runs `list_pull_requests` and `list_pipelines` together. It synthesizes that complex data set and tells you, 'PR 12 is ready; the pipeline passed 10 minutes ago.' You stop guessing and start deploying.
Common Questions About Bitbucket MCP
How do I use the `list_repositories` tool with Bitbucket MCP Server? +
You simply ask your agent to 'List all repositories in my workspace.' The agent runs list_repositories and provides a structured list of all repos you can access, saving you from navigating the workspace tree.
Does `get_pull_request` show if the code is merged? +
Yes, get_pull_request retrieves detailed metadata, including the current merge status and history. This lets you know if the PR is open, merged, or needs attention.
What is the purpose of the `list_pipelines` tool? +
The list_pipelines tool checks your CI/CD status. It tells you if the latest build for a repository passed or failed, which is critical before merging any code.
Can I use `list_issues` with Bitbucket MCP Server? +
Yes, list_issues lists issues for a repository. Remember, this only works if the repository has an issue tracker enabled in Bitbucket.
How does `list_commits` work? +
The list_commits tool lists the most recent commits for a repository. You can use this to see who wrote what and when, acting as a quick audit log.
How do I use `list_workspaces` to see all my team's codebases? +
It lists all accessible workspaces. This is useful if you need to know which team areas contain the repository you want to work with.
What is the difference between `list_branches` and `list_repositories`? +
You first use list_repositories to find the main project container. Then, list_branches shows the specific development lines within that repository.
Can I use `get_user_profile` to check my permissions? +
It retrieves your authenticated user profile details. This confirms your identity and what Bitbucket sees as your current access level.
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.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Cloudflare Alternative
Manage DNS, Workers, KV, Pages and firewall via Cloudflare — audit records, deploy config and inspect CDN analytics from any AI agent.
Cloudflare
AI edge infrastructure: manage Workers, KV, D1, R2, routes, and deployments via agents.
Railway
Equip your AI with direct access to your Railway infrastructure — manage projects, deployments, services, and environment variables.
You might also like
Internet Archive Metadata
Get detailed metadata, files, reviews, and stats for any Internet Archive item.
Europe PMC
Access over 33 million life science publications and research grants. Search PubMed, Agricola, and more directly from your AI agent.
Criteo Marketing API
Equip your AI agent to manage Criteo marketing campaigns, ad sets, and budgets directly via the Criteo API.