Bitbucket MCP for AI Agents. Check PRs, commits, and builds without switching apps.
Bitbucket connects your Git repositories directly into any AI agent, letting you manage complex software development workflows through natural conversation. List pull requests, check commit history, and monitor CI/CD pipelines without leaving your chat window.
Give Claude and any AI agent real-world access
Retrieve a list of every repository available in your workspaces.
Get details and monitor the current state of any specific pull request.
View a list of commits made to a repository, including who wrote them and when.
Check the status of CI/CD builds (Bitbucket Pipelines) for success or failure.
List all active branches or check for open issues within a project's tracker.
Ask an AI about this
Waiting for input…
What AI agents can do with Bitbucket with 10 Tools
Use these tools to get specific data points from your Bitbucket workspace, whether you need a list of repositories or the details for one pull request.
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 MCPGet Pull Request
Retrieves specific details about one pull request by its ID.
List Commits
Generates a list of commits made to a selected repository.
Get Repository
Provides full metadata for a specific project repository.
Get User Profile
Pulls the profile information of the currently authenticated user.
List Branches
Lists all available branches for a given repository.
List Issues
Retrieves open issues for a repository, provided the issue tracker is enabled.
List Pipelines
Lists all CI/CD pipelines associated with a specific repository.
List Pull Requests
Gets a list of all pull requests within a given repository.
List Repositories
Lists every repository available in the connected workspace.
List Workspaces
Retrieves a list of all accessible team workspaces.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
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 each 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 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
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 each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Overhead of Context Switching Solved with Vinkius AI Gateway
Every time you need to know the status of a feature, you have to open Bitbucket. You jump from the main repository view to check if a pull request is ready. Then, you switch again to see if the associated build pipeline actually passed tests. Finally, you might go back to the issue tracker just to confirm what the original bug was.
With this MCP, your agent handles the entire sequence. You ask one question—for example, 'Is feature X merge-ready?' The system then automatically checks list_pull_requests, validates get_repository details, and confirms that list_pipelines reports a successful build. It's all in one chat response.
Bitbucket MCP: Full Git Workflow Visibility
You eliminate the need to manually navigate between tabs, copy commit hashes, or run multiple status checks across different internal systems. You don't have to remember which tool handles PRs versus pipelines.
Your workflow becomes conversational and immediate. The complex structure of Git is distilled down to simple answers from your agent.
What your AI can actually do with this
Use this MCP to connect your Bitbucket Cloud account and run entire software development processes using just plain language. Instead of jumping between Git interfaces or running multiple commands in a terminal, you can simply ask your agent for updates. You can list all repositories across your workspaces, check the status of pull requests, and even review commit activity history.
It also tracks the health of your CI/CD pipelines. Because this MCP is hosted on Vinkius, you connect once from any compatible client—like Cursor or Claude—and gain access to Bitbucket alongside thousands of other services. You just talk to it and get actionable data back.
019d755d-8a2b-7189-96d5-211526454ae3 Here's how it actually works
The bottom line is you manage complex code workflows using conversation, not command lines.
Subscribe to this MCP and provide your Bitbucket username and App Password.
Direct your AI agent to the connection. You don't need to remember specific commands or API endpoints.
Ask a plain language question, like 'What is the status of PR #45?' and get the answer instantly.
Who is this actually for?
Software engineers who spend too much time switching between their IDE, Jira, and Bitbucket to check a simple PR status. DevOps staff tired of running manual git commands just to get build health checks.
Using this MCP, you can ask your agent for the latest commits or review open pull requests without opening a browser tab.
You monitor build statuses and repository activity directly from your primary workflow tool. You'll check pipeline health in seconds.
You retrieve summaries of recent code changes, open issues, and PRs needed for a quick daily standup update.
What Changes When You Connect
Instantly check pull request statuses. Instead of clicking through multiple tabs to see if a merge is blocked, your agent gets you the status directly.
Monitor CI/CD pipelines effortlessly. You get immediate feedback on whether a build succeeded or failed using list_pipelines without logging into the Jenkins dashboard.
Never lose track of code history again. Use list_commits to quickly find out who made what change and when, giving perfect context for discussions.
Manage teams with confidence. By listing repositories and workspaces, you get a clean overview of everything your team is working on.
Streamline reviews. You can check details about specific pull requests using get_pull_request in one go, speeding up the entire code review cycle.
See it in action
Need to know if a feature branch is ready for merge?
A developer asks their agent: 'What are the open pull requests and have they passed CI/CD?' The agent runs list_pull_requests, then checks list_pipelines. It reports that PR #12 is green on all builds and has 3 approvals. They can proceed with confidence.
Debugging a build failure quickly.
A DevOps engineer asks: 'Show me the last five commits for 'user-service' and what the status of the latest pipeline was.' The agent uses list_commits and list_pipelines, showing the commit that introduced the error right next to the failed build report.
Preparing for a team sync.
A team lead asks: 'List all repositories in our main workspace and show me any open issues for the billing module.' The agent uses list_repositories, then runs list_issues on the target repo. They get an immediate status report.
Onboarding a new developer.
A manager asks: 'What are the core services we maintain?' The agent calls list_workspaces and list_repositories, giving the new hire a comprehensive map of the codebase structure immediately.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Checking status via multiple tabs
Opening Bitbucket, clicking 'Repositories', then finding the project. Next, opening the 'Pull Requests' section to check a specific PR ID. Finally, switching to 'Pipelines' just for one build status.
Ask your agent directly: 'Show me the status of pull request 45 and its corresponding pipeline run.' This combines multiple checks into one conversational query.
Manually copying commit hashes
When discussing a bug, manually finding the exact commit hash in the GUI and pasting it into Slack to reference the issue.
Use list_commits. Ask your agent: 'List the last 5 commits related to API authentication.' The agent provides clean, readable summaries of the changes.
Running checks in a separate CLI tool
Using dedicated Git client tools or running complex git branch commands just to see active branches for a quick check.
Use list_branches. Simply ask your agent: 'What are the current development branches available?' and get a clean, instant list.
When It Fits, When It Doesn't
Use this MCP if your primary pain point is context switching—if checking repository status requires opening 3 or more different internal tools (PR viewer, CI dashboard, commit log). This MCP excels at synthesizing information from distinct sources like get_pull_request and list_pipelines into one chat response.
Don't use this if you just need to perform a single action, like writing a new commit message. For pure text generation or simple data manipulation (like reformatting code blocks), stick to dedicated LLMs. If your goal is simply to manage user accounts without needing Git context, look for an identity management MCP instead.
Questions you might have
How do I check the status of a pull request using Bitbucket MCP? +
You use get_pull_request by providing the ID. This tool retrieves all necessary details, letting you know if it's open, merged, or requires changes.
Does Bitbucket MCP track user accounts? +
Yes, the list_user_profile tool lets your agent retrieve the authenticated user's profile information directly from Bitbucket.
Can I see all branches in a repo with this MCP? +
You use list_branches to get a complete and up-to-date list of every active branch for that repository.
What is the difference between list_commits and listing repositories? +
list_repositories gives you metadata about the project container itself. list_commits tracks the specific changes, including who authored them and when, within a single project.
How often is pipeline data updated in Bitbucket MCP? +
The list_pipelines tool pulls real-time status from Bitbucket Pipelines, so you are always viewing the most current build health information available.