bitbucket-automation

Bitbucket Automation - Code Repository Automation Driven by Rube MCP

Skill Overview

Bitbucket Automation provides full Bitbucket operation capabilities for Claude Code via Rube MCP (Composio), supporting automated management of repositories, pull requests, branches, issues, and workspaces. Complex code collaboration workflows can be completed with simple natural language instructions.

Applicable Scenarios

1. Pull Request Automation Workflows

When you need to automate the creation and management of pull requests, this skill can create PRs in bulk, assign reviewers, retrieve code diffs, and add review comments. It is especially suitable for development teams that frequently create PRs or CI/CD scenarios that require automated code review processes.

2. Bulk Repository and Workspace Management

When you need to manage multiple Bitbucket repositories consistently, this skill supports listing all workspaces and repositories, creating new repositories, setting privacy permissions, and listing member information. It is suitable for DevOps engineers managing infrastructure or project managers conducting team resource inventories.

3. Issue Tracking and Branch Management

When you need to automate project issue tracking and feature branch creation, this skill supports creating, updating, and deleting issues, and creating new branches from specific commits. It is suitable for agile development teams’ daily task management or Git workflows that require automated branch strategies.

Core Features

1. Pull Request Full Lifecycle Management

Supports creating PRs and specifying reviewers (using UUID format), listing PRs by different statuses (OPEN/MERGED/DECLINED), retrieving PR details and code diffs, and adding inline code review comments. Built-in BBQL filtering is supported for flexible filtering by workspace, repository, and status.

2. Bitbucket Repository and Workspace Operations

Supports listing all accessible workspaces, creating or deleting repositories within a workspace (note that delete operations are irreversible), using the BBQL query language to filter repository lists, filtering by user role (member/contributor/admin/owner), and listing workspace members for reviewer assignment.

3. Issue and Branch Automation

Supports creating four types of issues: Bug, Enhancement, Proposal, and Task; setting priority and due date; adding comments and updating status. Supports creating branches from full SHA1 commit hashes, and filtering and sorting branch lists using BBQL.

4. Smart Querying and Pagination Handling

Supports Bitbucket Query Language (BBQL) for complex filtering; string values must be enclosed in double quotes. Built-in pagination handling is provided, with 10 results per page by default; the pagelen parameter can be set (PR maximum 50, others maximum 100) to retrieve complete data.

5. Code Review Collaboration

Supports retrieving a unified diff for a PR (a max_chars limit can be set to avoid context overflow), retrieving line counts of changed files, creating review comments in Markdown format, and supporting inline code comments and thread replies.

Frequently Asked Questions

How do I connect to Bitbucket using Rube MCP?

First, add https://rube.app/mcp as the MCP server in the client configuration; no API key is required. Then call RUBE_SEARCH_TOOLS to verify the connection is available, use RUBE_MANAGE_CONNECTIONS to configure the toolkit as bitbucket, follow the returned OAuth link to complete authorization, and finally confirm the connection status is ACTIVE to begin use.

What operations does Bitbucket Automation support?

This skill supports five core operation areas: pull request management (create, list, get details, get diff, add comments), repository management (list, create, delete), issue management (create, update, delete, comment), branch management (list, create), and workspace management (list members, list repositories). All operations support BBQL filtering and pagination.

Why do reviewers need a UUID format instead of a username?

The Bitbucket API uses UUIDs as user identifiers; the format must include braces like {123e4567-e89b-12d3-a456-426614174000}. You can obtain members’ UUIDs via BITBUCKET_LIST_WORKSPACE_MEMBERS. Note that in different APIs, creating an issue uses the username string, while updating an issue uses assignee_account_id as a UUID—this is an API design difference.

Are there special requirements for BBQL query syntax?

BBQL (Bitbucket Query Language) is used to filter list results; string values must be enclosed in double quotes, e.g., name~"api" rather than name~api. Supported operators include = (exact match), ~ (contains), != (not equal), >, >=, <, <=, and combinations using AND/OR. Note that repository is not a valid BBQL field; use name instead.

What limitations does the Bitbucket API have?

Bitbucket Cloud API has rate limits; large batch operations should include delays. Paginated requests count toward rate limits, so minimize unnecessary page retrievals. Delete operations (repository, issue) are irreversible—confirm before executing. The maximum pagelen for PR-related operations is 50, and 100 for other operations. When fetching large diffs, it is recommended to set the max_chars parameter (for example, 50000) to avoid context overflow.