Expose Bitbucket Cloud pull request build statuses

Julien Graglia

Hi,

I'd like the Atlassian MCP Server to expose the build statuses of a pull request.

I don't use Bitbucket Pipelines for CI: Jenkins reports its build status on the commit, and other tools such as SonarQube attach their status the same way. The MCP Server currently can't read these statuses. As a result, an agent can't tell which build failed on a PR, link to the CI job, or react automatically (fix, comment, re-run).

What exists today:

• Pipelines operations (listBitbucketRepoPipelines, step logs…) only cover Bitbucket Pipelines.
• getBitbucketRepoPullRequestMergeability only reports whether merge checks pass. It doesn't list individual builds (name, state, URL), and builds only appear if a build-based merge check is configured.

Request: a read-only operation wrapping the existing REST endpoint:
GET /repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/statuses
https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/#api-repositories-workspace-repo-slug-pullrequests-pull-request-id-statuses-get

Nice to have: the same at commit level (GET /repositories/{workspace}/{repo_slug}/commit/{commit}/statuses), to check builds on a branch before a PR is opened.

Example use case: "Check PR #42, find the failing Jenkins build and propose a fix", with the agent combining the Atlassian MCP Server and the Jenkins MCP server.

Thanks!

Yevhenii Tomberg

Hi Julien,

You've already found the right endpoint. Until the MCP Server exposes it, a workaround that works today: let the agent call the REST API directly (or wrap it in a small custom MCP tool next to the Jenkins one).

1. PR level: GET /2.0/repositories/{workspace}/{repo_slug}/pullrequests/{pull_request_id}/statuses returns the PR's build statuses. Each entry has key, name, state (SUCCESSFUL, FAILED, INPROGRESS or STOPPED), url, description and updated_on. You can narrow it down with the q parameter, e.g. q=state="FAILED".
2. Branch level, before a PR exists: GET /2.0/repositories/{workspace}/{repo_slug}/commit/{commit}/statuses with the branch's head commit.

The url field is what lets the agent jump from a FAILED entry to the Jenkins job, so "find the failing build on PR #42" becomes: list statuses → keep the FAILED ones → hand the url/key to the Jenkins MCP server.

Auth: both endpoints accept an API token. The PR endpoint needs the read:pullrequest:bitbucket scope, the commit endpoint read:repository:bitbucket; both are read-only.

I'd still keep this as a feature request so it lands in the official server: read-only access to PR statuses fits agent workflows very naturally.