Bitbucket MCP Integration

Add a new comment to an issue in a Bitbucket repository. Creates a comment with the specified text content. The authenticated user is automatically set as the comment author. Returns the newly created comment object with ID, creation timestamp, and content. Useful for providing feedback on bug reports, discussing solutions, asking questions, documenting decisions, and communicating with team members about issues. Comments support markdown formatting. May be rejected if detected as spam. Note: Requires repository to have issue tracker enabled.

Add a comment to a pull request. Use cases: (1) General comment - provide only content; (2) Reply to comment - provide content + parent_id; (3) Inline code review - provide content + inline with path and line number(s). Returns the created comment.

Create a new branch in a Bitbucket repository from a specific commit or existing branch. Returns the newly created branch object with name, target commit hash, and links. Requires write access to the repository. The branch name should not include prefixes (e.g., use 'feature/new-feature', not 'refs/heads/feature/new-feature'). Useful for creating feature branches, release branches, or hotfix branches.

Create a new issue in a Bitbucket repository. Only title is required; all other fields are optional. The authenticated user is automatically set as the issue reporter. Supports setting description, kind (bug/enhancement/proposal/task), priority (trivial to blocker), assignee, milestone, version, and component. Returns the newly created issue object with ID, creation date, and all specified fields. Useful for bug reporting, feature requests, task tracking, and project management. Creates immutable change record. Note: Requires repository to have issue tracker enabled.

Create and initiate a new pipeline execution in a Bitbucket repository. Supports multiple trigger types: branch/tag pipeline (specify ref_type and ref_name), commit-specific pipeline (specify commit hash), custom pipeline with selector pattern, or pull request pipeline. Can optionally pass variables to the pipeline (with secured flag for sensitive values). The repository must have bitbucket-pipelines.yml configured. Returns the created pipeline object with UUID, build number, and status. Useful for manually triggering deployments, running custom pipelines, testing pipeline configurations, triggering builds for specific commits, and automating CI/CD workflows. Requires pipeline write permissions.

Create a new pull request in a Bitbucket repository. Requires title and source branch. Optionally specify destination branch, description, draft status, reviewers, and whether to close source branch after merge.

Create a new tag in a Bitbucket repository pointing to a specific commit. Tags are immutable references commonly used for marking release points (v1.0.0, v2.0.0) or important milestones in project history. The tag will be created at the specified commit hash. Use full commit hashes to avoid ambiguity errors. Returns the newly created tag object with name, target commit details, and links. Useful for release management, versioning, and CI/CD automation workflows.

Create a new webhook subscription on a Bitbucket repository. Configures automatic HTTP POST notifications to a specified URL when selected events occur. The URL must be publicly accessible and properly resolve (cannot be internal address). When a secret is provided, Bitbucket generates HMAC digest in X-Hub-Signature header for request verification. Returns the created webhook object with UUID for management. Useful for integrating CI/CD systems, triggering deployments on push, notifying external services about pull requests, automating issue tracking workflows, and building custom integrations. Requires webhook write permissions plus permissions for subscribed event types.