Bitbucket
Connect your agent to Bitbucket to manage repos, branches, pull requests, and webhooks when your code lives in Atlassian workspaces.
Overview
com.mcparmory/bitbucket is an MCP server for the Build phase that manages Bitbucket repositories, branches, pull requests, and webhooks from your AI agent.
What is this MCP server?
- Manage Bitbucket repositories, branches, and pull requests from MCP tools
- Configure and work with webhooks in Bitbucket workspaces
- stdio server v1.0.5 via uvx mcparmory-bitbucket or ghcr.io Docker image
- Two registry packages (PyPI and OCI) on MCP Armory
- Useful when your solo stack is Atlassian (Bitbucket + Jira + Confluence)
- Server version 1.0.5 with 2 packages (PyPI uvx and Docker OCI ghcr.io/mcparmory/bitbucket:1.0.5)
- stdio transport per MCP schema 2025-12-11
Community signal: 25 GitHub stars.
What problem does it solve?
If your remotes are on Bitbucket, constantly opening the web UI for PRs, branches, and webhooks slows agent-assisted shipping.
Who is it for?
Developers on Bitbucket Cloud who want MCP-driven repo, PR, and webhook management from Claude Code or Cursor.
Skip if: GitHub-only or GitLab-only workflows, or pure local git with no Bitbucket remote.
What do I get? / Deliverables
After registration, your agent can perform Bitbucket repo and PR operations in-session so remote git hosting stays aligned with local commits and reviews.
- Agent-accessible Bitbucket repo and branch management
- Pull request create and manage operations against your workspace
- Webhook configuration and workspace-level git hosting automation
Recommended MCP Servers
Journey fit
Source hosting and PR automation are core build-phase integration work for teams standardized on Bitbucket instead of GitHub. Integrations subphase covers VCS remotes, webhooks, and repo APIs that agents call during implementation and CI setup.
How it compares
Bitbucket Cloud MCP integration—not a code review methodology skill or self-hosted git server.
Common Questions / FAQ
Who is com.mcparmory/bitbucket for?
Builders using Bitbucket workspaces who want their coding agent to manage repositories, pull requests, branches, and webhooks via MCP.
When should I use com.mcparmory/bitbucket?
Use it during build and ship when you push to Bitbucket and need PR creation, branch inspection, or webhook setup without leaving the agent.
How do I add com.mcparmory/bitbucket to my agent?
Add a stdio MCP server running uvx mcparmory-bitbucket or the ghcr.io/mcparmory/bitbucket image and configure Bitbucket API credentials in environment variables.