by aashari
Easily enable Bitbucket and Jira integration with REST APIs for seamless repository management, pull requests, and works
Connects to Bitbucket Cloud and Server APIs to manage pull requests, code reviews, and branch workflows. Provides 29 tools for creating, updating, merging PRs and handling code review operations.
Bitbucket is a community-built MCP server published by aashari that provides AI assistants with tools and capabilities via the Model Context Protocol. Easily enable Bitbucket and Jira integration with REST APIs for seamless repository management, pull requests, and works It is categorized under developer tools, productivity. This server exposes 6 tools that AI clients can invoke during conversations and coding sessions.
You can install Bitbucket in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Bitbucket is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
I recommend Bitbucket for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Bitbucket is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Strong directory entry: Bitbucket surfaces stars and publisher context so we could sanity-check maintenance before adopting.
Bitbucket reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
I recommend Bitbucket for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
Bitbucket is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
Bitbucket is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Bitbucket is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
We evaluated Bitbucket against two servers with overlapping tools; this profile had the clearer scope statement.
Bitbucket has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
showing 1-10 of 28
Transform how you work with Bitbucket by connecting Claude, Cursor AI, and other AI assistants directly to your repositories, pull requests, and code. Get instant insights, automate code reviews, and streamline your development workflow.
Get up and running in 2 minutes:
IMPORTANT: Bitbucket App Passwords are being deprecated and will be removed by June 2026. We recommend using Scoped API Tokens for new setups.
Bitbucket is deprecating app passwords. Use the new scoped API tokens instead:
repository, workspacerepository, workspace, pullrequestATATT)Generate a Bitbucket App Password (legacy method):
# Set your credentials (choose one method)
# Method 1: Scoped API Token (recommended - future-proof)
export ATLASSIAN_USER_EMAIL="[email protected]"
export ATLASSIAN_API_TOKEN="your_scoped_api_token" # Token starting with ATATT
# OR Method 2: Legacy App Password (will be deprecated June 2026)
export ATLASSIAN_BITBUCKET_USERNAME="your_username"
export ATLASSIAN_BITBUCKET_APP_PASSWORD="your_app_password"
# List your workspaces
npx -y @aashari/mcp-server-atlassian-bitbucket get --path "/workspaces"
# List repositories in a workspace
npx -y @aashari/mcp-server-atlassian-bitbucket get --path "/repositories/your-workspace"
# Get pull requests for a repository
npx -y @aashari/mcp-server-atlassian-bitbucket get --path "/repositories/your-workspace/your-repo/pullrequests"
# Get repository details with JMESPath filtering
npx -y @aashari/mcp-server-atlassian-bitbucket get --path "/repositories/your-workspace/your-repo" --jq "{name: name, language: language}"
Add this to your Claude configuration file (~/.claude/claude_desktop_config.json):
Option 1: Scoped API Token (recommended - future-proof)
{
"mcpServers": {
"bitbucket": {
"command": "npx",
"args": ["-y", "@aashari/mcp-server-atlassian-bitbucket"],
"env": {
"ATLASSIAN_USER_EMAIL": "[email protected]",
"ATLASSIAN_API_TOKEN": "your_scoped_api_token"
}
}
}
}
Option 2: Legacy App Password (will be deprecated June 2026)
{
"mcpServers": {
"bitbucket": {
"command": "npx",
"args": ["-y", "@aashari/mcp-server-atlassian-bitbucket"],
"env": {
"ATLASSIAN_BITBUCKET_USERNAME": "your_username",
"ATLASSIAN_BITBUCKET_APP_PASSWORD": "your_app_password"
}
}
}
}
Restart Claude Desktop, and you'll see the bitbucket server in the status bar.
Most AI assistants support MCP. You can either:
Option 1: Use npx (recommended - always latest version):
Configure your AI assistant to run: npx -y @aashari/mcp-server-atlassian-bitbucket
Option 2: Install globally:
npm install -g @aashari/mcp-server-atlassian-bitbucket
Then configure your AI assistant to use the MCP server with STDIO transport.
Supported AI assistants:
Create ~/.mcp/configs.json for system-wide configuration:
Option 1: Scoped API Token (recommended - future-proof)
{
"bitbucket": {
"environments": {
"ATLASSIAN_USER_EMAIL": "[email protected]",
"ATLASSIAN_API_TOKEN": "your_scoped_api_token",
"BITBUCKET_DEFAULT_WORKSPACE": "your_main_workspace"
}
}
}
Option 2: Legacy App Password (will be deprecated June 2026)
{
"bitbucket": {
"environments": {
"ATLASSIAN_BITBUCKET_USERNAME": "your_username",
"ATLASSIAN_BITBUCKET_APP_PASSWORD": "your_app_password",
"BITBUCKET_DEFAULT_WORKSPACE": "your_main_workspace"
}
}
}
Alternative config keys: The system also accepts "atlassian-bitbucket", "@aashari/mcp-server-atlassian-bitbucket", or "mcp-server-atlassian-bitbucket" instead of "bitbucket".
This MCP server provides 6 generic tools that can access any Bitbucket API endpoint:
| Tool | Description | Parameters |
|---|---|---|
bb_get | GET any Bitbucket API endpoint (read data) | path, queryParams?, jq?, outputFormat? |
bb_post | POST to any endpoint (create resources) | path, body, queryParams?, jq?, outputFormat? |
bb_put | PUT to any endpoint (replace resources) | path, body, queryParams?, jq?, outputFormat? |
bb_patch | PATCH any endpoint (partial updates) | path, body, queryParams?, jq?, outputFormat? |
bb_delete | DELETE any endpoint (remove resources) | path, queryParams?, jq?, outputFormat? |
bb_clone | Clone a repository locally | workspaceSlug?, repoSlug, targetPath |
All API tools support these common parameters:
path (required): API endpoint path starting with / (the /2.0 prefix is added automatically)queryParams (optional): Key-value pairs for query parameters (e.g., {"pagelen": "25", "page": "2"})jq (optional): JMESPath expression to filter/transform the response - highly recommended to reduce token costsoutputFormat (optional): "toon" (default, 30-60% fewer tokens) or "json"body (required for POST/PUT/PATCH): Request body as JSON objectAll paths automatically have /2.0 prepended. Full Bitbucket Cloud REST API 2.0 reference: https://developer.atlassian.com/cloud/bitbucket/rest/
Workspaces & Repositories:
/workspaces - List all workspaces/repositories/{workspace} - List repos in workspace/repositories/{workspace}/{repo} - Get repo details/repositories/{workspace}/{repo}/refs/branches - List branches/repositories/{workspace}/{repo}/refs/branches/{branch_name} - Get/delete branch/repositories/{workspace}/{repo}/commits - List commits/repositories/{workspace}/{repo}/commits/{commit} - Get commit details/repositories/{workspace}/{repo}/src/{commit}/{filepath} - Get file contentPull Requests:
/repositories/{workspace}/{repo}/pullrequests - List PRs (GET) or create PR (POST)/repositories/{workspace}/{repo}/pullrequests/{id} - Get/update/delete PR/repositories/{workspace}/{repo}/pullrequests/{id}/diff - Get PR diff/repositories/{workspace}/{repo}/pullrequests/{id}/comments - List/add PR comments/repositories/{workspace}/{repo}/pullrequests/{id}/approve - Approve PR (POST) or remove approval (DELETE)/repositories/{workspace}/{repo}/pullrequests/{id}/request-changes - Request changes (POST)/repositories/{workspace}/{repo}/pullrequests/{id}/merge - Merge PR (POST)/repositories/{workspace}/{repo}/pullrequests/{id}/decline - Decline PR (POST)Comparisons:
/repositories/{workspace}/{repo}/diff/{source}..{destination} - Compare branches/commitsOther Resources:
/repositories/{workspace}/{repo}/issues - List/manage issues/repositories/{workspace}/{repo}/downloads - List/manage downloads/repositories/{workspace}/{repo}/pipelines - Access Bitbucket Pipelines/repositories/{workspace}/{repo}/deployments - View deploymentsWhat is TOON? Token-Oriented Object Notation is a format optimized for LLMs that reduces token consumption by 30-60% compared to JSON. It uses tabular arrays and minimal syntax while preserving all data.
Default behavior: All tools return TOON format by default. You can override this with outputFormat: "json" if needed.
Example comparison:
JSON (verbose):
{
"values": [
{"name": "repo1", "slug": "repo-1"},
{
---
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.