Skip to main content
Glama
aashari

Atlassian Bitbucket MCP Server

by aashari
.env.example1.39 kB
# Enable debug logging (optional) DEBUG=false # ============================================================================ # AUTHENTICATION - Choose ONE method below # ============================================================================ # Method 1: Scoped API Token (RECOMMENDED - future-proof) # Generate at: https://id.atlassian.com/manage-profile/security/api-tokens # Token should start with "ATATT" # Required scopes: repository, workspace, pullrequest (for PR management) ATLASSIAN_USER_EMAIL=your-email@example.com ATLASSIAN_API_TOKEN=your_scoped_api_token_starting_with_ATATT # Method 2: Bitbucket App Password (LEGACY - deprecated June 2026) # Generate at: https://bitbucket.org/account/settings/app-passwords/ # Required permissions: Workspaces (Read), Repositories (Read/Write), Pull Requests (Read/Write) # ATLASSIAN_BITBUCKET_USERNAME=your-bitbucket-username # ATLASSIAN_BITBUCKET_APP_PASSWORD=your-app-password # ============================================================================ # OPTIONAL CONFIGURATION # ============================================================================ # Default workspace for commands (optional - uses first workspace if not set) # BITBUCKET_DEFAULT_WORKSPACE=your-main-workspace-slug # Note: ATLASSIAN_SITE_NAME is NOT needed for Bitbucket Cloud # Only use it if you're configuring Jira/Confluence alongside Bitbucket

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/aashari/mcp-server-atlassian-bitbucket'

If you have feedback or need assistance with the MCP directory API, please join our Discord server