---
title: "Bitbucket MCP — Atlassian Server Setup"
aliases: [bitbucket-mcp, atlassian-mcp-bitbucket, mcp-bitbucket, atlassian-api-tokens]
tags: [mcp, bitbucket, atlassian, claude-code, git, api-tokens]
sources:
  - "daily/2026-04-17.md"
created: 2026-04-17
updated: 2026-04-17
---

# Bitbucket MCP — Atlassian Server Setup

The official GitHub MCP server (`@modelcontextprotocol/server-github`) only works with GitHub — not Bitbucket Cloud or Bitbucket Server. For Bitbucket, use `aashari/mcp-server-atlassian-bitbucket`. Both MCP servers can coexist in Claude Code's global config without conflicts. Bitbucket App Passwords are deprecated; use Atlassian API Tokens instead.

## Key Points

- **GitHub MCP ≠ Bitbucket MCP** — they are completely separate servers with separate auth; the GitHub MCP server does not support the Bitbucket API
- Recommended Bitbucket MCP: `aashari/mcp-server-atlassian-bitbucket` (Bitbucket Cloud; npm package)
- Bitbucket **App Passwords are deprecated** — replaced by Atlassian API Tokens created at `id.atlassian.com/manage-profile/security/api-tokens`
- GitHub MCP and Bitbucket MCP coexist in Claude Code's global `~/.claude/settings.json` without conflicts — they appear as separate tool namespaces
- Promote MCP servers to the **global** Claude Code config if you want them available in every project (not just the current working directory)

## Details

### Why GitHub MCP Doesn't Work for Bitbucket

`@modelcontextprotocol/server-github` calls the GitHub REST API (`api.github.com`). Bitbucket Cloud uses a completely different API (`api.bitbucket.org/2.0`) with different auth headers, endpoint paths, and resource models. There is no compatibility layer — you need a separate MCP server implementation.

### Choosing a Bitbucket MCP Server

| Server | Platform | Language | Notes |
|--------|----------|----------|-------|
| `aashari/mcp-server-atlassian-bitbucket` | Bitbucket Cloud | TypeScript/npm | Best maintained as of 2026-04 |
| Atlassian official Jira/Confluence MCP | Jira + Confluence | — | Does not cover Bitbucket repos |

For Bitbucket Cloud (bitbucket.org), `aashari/mcp-server-atlassian-bitbucket` is the practical choice.

### Installation (Global Claude Code Config)

```json
// ~/.claude/settings.json — global, fires from any project
{
  "mcpServers": {
    "github": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-github"],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "ghp_..."
      }
    },
    "bitbucket": {
      "command": "npx",
      "args": ["-y", "mcp-server-atlassian-bitbucket"],
      "env": {
        "ATLASSIAN_USERNAME": "your@email.com",
        "ATLASSIAN_API_TOKEN": "ATATT3x..."
      }
    }
  }
}
```

Both servers appear under separate names in Claude Code — `github__*` tools and `bitbucket__*` tools (or whatever the server declares).

### Creating an Atlassian API Token

Bitbucket App Passwords (`https://bitbucket.org/account/settings/app-passwords/`) are legacy and deprecated. The replacement:

1. Go to `https://id.atlassian.com/manage-profile/security/api-tokens`
2. Click **Create API token**
3. Give it a label (e.g., `claude-code-mcp`)
4. Copy the token immediately — it's only shown once
5. Use as `ATLASSIAN_API_TOKEN` with your Atlassian account email as `ATLASSIAN_USERNAME`

The same API token works for Bitbucket Cloud, Jira, and Confluence since they share the Atlassian identity platform.

### Claude Code Plugin Scope

Claude Code plugins (including code-review, feature-dev) can be scoped to:
- **Project** scope — only active in the current project directory
- **User (global)** scope — active in every project

To promote a plugin to global scope: open Claude Code settings → Plugins → find the plugin → change scope to "User". This is the right choice for utility plugins like `code-review` and `feature-dev` that apply to any project.

## Related Concepts

- [[wiki/concepts/fish-abbr-patterns]] — Fish shell configuration session where MCP setup was done
- [[wiki/claude-code/_index]] — Claude Code MCP documentation, hooks, and plugin configuration
- [[wiki/connections/graph-api-vs-msal-app-vs-delegated]] — API auth patterns (App Passwords → API Tokens mirrors the broader shift to OAuth-based tokens)

## Sources

- [[daily/2026-04-17.md]] — GitHub MCP vs Bitbucket question resolved; `aashari/mcp-server-atlassian-bitbucket` selected; Atlassian API token created at id.atlassian.com; `code-review` and `feature-dev` plugins promoted to global scope; GitHub + Bitbucket MCP confirmed to coexist without conflicts
