Atlassian has made Bitbucket Cloud easier for an AI assistant to reach. In Connect Bitbucket Cloud to your AI tools with Atlassian MCP, the post explains that Bitbucket was already available through the Atlassian MCP Server with API tokens, and the latest release adds OAuth, so developers can sign in with their Atlassian account instead. “API tokens remain supported, while OAuth offers a simpler way to get started with compatible AI clients.” The pitch is that one connection carries both halves of a change: “Jira explains why the change is needed, Confluence captures technical decisions and rollout plans, and Bitbucket provides the code, commits, pull request discussion, and pipeline results.”
There are no figures, and the examples are the right ones. An assistant can read a Jira item and its linked design page, implement the change and raise a pull request; or, given a failing build, read the failed step and its logs, suggest a cause and raise a separate pull request with the fix. The release also expands what an assistant can do in Bitbucket: manage pull request comments and reviewer updates, find commits and locate related pull requests, so it can “help with implementation and review, not just retrieve information.” Access “remains governed by your existing Atlassian and Bitbucket permissions.” OAuth arrives on a v2 endpoint, and v1 users may need to remove and re-add their connector.
The catalog holds the Bitbucket surface in depth. The Atlassian provider page lists 186 API pages, and the post’s two workflows run over the Atlassian Pull Requests API, the Atlassian Bitbucket Commits API and the Atlassian Bitbucket Pipelines API. The agentic access profile maps 2,550 operations, 1,290 of them acting. Agent skills, dry-run mode, delegated identity, reversibility and error semantics are lit on the Agent Readiness score.
The Kin Score is 73.6, exemplar band, and the Agent Readiness score is 42.2, agent-ready. The MCP server dimension is unlit, as are protected resource metadata and dynamic client registration, on the record of a company running a remote MCP server that now supports OAuth sign-in. That is the third time this series has found a major provider’s MCP server missing from its record, after Kong and AWS, and it is on our side. A server that moved to a v2 endpoint is exactly the case a probe built against an older address would miss. Atlassian has put Jira, Confluence and Bitbucket behind one sign-in for any AI client. The catalog needs to find the door it moved.