Skip to main content
Glama
icy-r

Bitbucket MCP

by icy-r
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
BITBUCKET_USERNAMENoBitbucket username (required for basic auth method)
BITBUCKET_API_TOKENNoAPI token (required for api_token auth method)
BITBUCKET_WORKSPACENoDefault workspace (optional)
BITBUCKET_USER_EMAILNoYour Atlassian email (required for api_token auth method)
BITBUCKET_AUTH_METHODNoAuthentication method: api_token, oauth, or basic
BITBUCKET_APP_PASSWORDNoApp password (required for basic auth method)
BITBUCKET_OUTPUT_FORMATNoOutput format: json, toon, or compact (optional)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
bitbucket_workspacesB

Manage Bitbucket workspaces. Actions:

  • list: List all accessible workspaces

  • get: Get details of a specific workspace

  • list_projects: List projects in a workspace

  • list_members: List members of a workspace

bitbucket_repositoriesC

Manage Bitbucket repositories. Actions:

  • list: List repositories in a workspace

  • get: Get repository details

  • create: Create a new repository

  • delete: Delete a repository

  • fork: Fork a repository

  • get_file: Get file content from a repository

  • list_source: List files/directories in a repository path

bitbucket_pull_requestsB

Manage Bitbucket pull requests. Actions:

  • list: List pull requests in a repository

  • get: Get pull request details

  • create: Create a new pull request

  • update: Update a pull request

  • merge: Merge a pull request

  • approve: Approve a pull request

  • unapprove: Remove approval from a pull request

  • decline: Decline a pull request

  • list_comments: List comments on a pull request

  • add_comment: Add a comment to a pull request

  • get_diff: Get the diff of a pull request

bitbucket_branchesB

Manage Bitbucket branches and tags. Actions:

  • list_branches: List all branches in a repository

  • get_branch: Get details of a specific branch

  • create_branch: Create a new branch from a commit/ref

  • delete_branch: Delete a branch

  • list_tags: List all tags in a repository

  • get_tag: Get details of a specific tag

  • create_tag: Create a new tag

bitbucket_commitsB

Manage Bitbucket commits and diffs. Actions:

  • list: List commits in a repository

  • get: Get details of a specific commit

  • get_diff: Get diff between two refs (e.g., "branch1..branch2" or "commit1..commit2")

  • get_diffstat: Get diffstat (summary of changes) between two refs

bitbucket_pipelinesA

Manage Bitbucket Pipelines CI/CD. Actions:

  • list: List pipelines in a repository

  • get: Get details of a specific pipeline

  • trigger: Trigger a new pipeline run on a branch

  • trigger_custom: Trigger a custom pipeline with a specific pattern

  • stop: Stop a running pipeline

  • list_steps: List steps of a pipeline

  • get_step: Get details of a specific step

  • get_logs: Get logs for a pipeline step

  • get_config: Get pipeline configuration (enabled status)

  • set_enabled: Enable or disable pipelines for a repository

  • list_variables: List pipeline variables

  • get_variable: Get a specific pipeline variable

  • create_variable: Create a pipeline variable

  • update_variable: Update a pipeline variable

  • delete_variable: Delete a pipeline variable

bitbucket_issuesB

Manage Bitbucket issue tracking. Actions:

  • list: List issues in a repository

  • get: Get details of a specific issue

  • create: Create a new issue

  • update: Update an existing issue

  • delete: Delete an issue

  • list_comments: List comments on an issue

  • add_comment: Add a comment to an issue

  • vote: Vote for an issue

  • unvote: Remove vote from an issue

  • watch: Watch an issue for notifications

  • unwatch: Stop watching an issue

bitbucket_webhooksB

Manage Bitbucket webhooks for repositories and workspaces. Actions:

  • list: List webhooks for a repository

  • get: Get details of a specific webhook

  • create: Create a new webhook

  • update: Update an existing webhook

  • delete: Delete a webhook

  • list_workspace: List webhooks for a workspace

  • get_workspace: Get a workspace webhook

  • create_workspace: Create a workspace webhook

  • update_workspace: Update a workspace webhook

  • delete_workspace: Delete a workspace webhook

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool covers a distinct Bitbucket domain (branches, commits, issues, pipelines, pull requests, repositories, webhooks, workspaces) with no overlap in primary functionality. An agent can easily select the correct tool for a task.

Naming Consistency5/5

All tools follow a consistent 'bitbucket_<domain>' pattern, and within each tool, action names are short, clear verbs. The naming scheme is predictable and uniform across the entire set.

Tool Count5/5

With 8 tools covering the major Bitbucket features, the count is well-scoped for the platform's complexity. Each tool represents a natural grouping of related actions, avoiding unnecessary fragmentation or lumping.

Completeness5/5

The tool surface covers all core Bitbucket operations: source control (branches, commits), collaboration (PRs, issues), CI/CD (pipelines), repository management, webhooks, and workspaces. Critical workflows like create/update/delete are present where applicable.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources