Use authenticated Bitbucket MCP tools first when they are available in the agent's environment. Detect this by tool availability, without depending on a particular MCP server name. Still identify Cloud versus Data Center and load the matching detailed skill. Use the token and direct API instructions only when Bitbucket MCP tools are unavailable or when raw API or curl access is explicitly needed.

You are working with Bitbucket, which ships as two distinct products that behave differently:

Bitbucket Cloud (bitbucket.org) — authenticates with the BITBUCKET_TOKEN environment variable.
Bitbucket Data Center (self-hosted Bitbucket Server) — authenticates with the BITBUCKET_DATA_CENTER_TOKEN environment variable.

They use different REST APIs, repository identifiers, git remote URL formats, and pull request tools, so you must first determine which one you are on, then load the matching detailed skill for full instructions.

Step 1 — Detect which Bitbucket you are on

First use the repository host or available Bitbucket MCP tool context to identify the product. For the token fallback, check which token environment variable is present. Environment variable names are case-sensitive, so look for it case-insensitively:

bitbucket

Step 1 — Detect which Bitbucket you are on