Use authenticated Bitbucket Cloud 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. Use the token and direct REST API instructions below only when those tools are unavailable or when raw API or curl access is explicitly needed.

You are working with Bitbucket Cloud (bitbucket.org). You have access to an environment variable, BITBUCKET_TOKEN, which allows you to interact with the Bitbucket Cloud API.

REST API base URL: https://api.bitbucket.org/2.0
Repository identifier format: workspace/repo_slug

Only rewrite the Bitbucket remote if a push actually fails with authentication errors and the user has asked you to push. Do not proactively rewrite origin. OpenHands OSS commonly stores BITBUCKET_TOKEN in the same unencoded user:token form used by commands such as curl --user "$BITBUCKET_TOKEN" ..., so keep it in that form unless you truly need to embed it in a Git remote URL.

If you need a non-interactive HTTPS remote URL, split BITBUCKET_TOKEN on the first : and URL-encode each part before calling git remote set-url. This avoids breaking usernames or emails that contain reserved URL characters such as @:

bitbucket-cloud