# Your Bitbucket. From diff to decision.

Source: https://corespeed.io/integrations/bitbucket

Connect Bitbucket Cloud to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent reads a pull request's diff and comments, follows a failed pipeline down to the step log, and checks deployments across environments. It acts within your own Bitbucket permissions; commenting on, approving or merging a pull request is a separate call that approvals can hold.

## Set up an agent

Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)`

It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Bitbucket after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up

## Know why it failed. Know what to review

Ask your agent for the failed pipeline, the step that broke, and the pull requests that still need a reviewer.

You ask your agent: "Find the last failed pipeline on main in acme/shop, read the failing step's log, and list the open pull requests waiting for review. Do not merge or comment."

It calls CoreSpeed:

- `bitbucket__list_pipelines`: ok, 538 ms
- `bitbucket__get_pipeline_step_log`: ok, 691 ms
- `bitbucket__list_pull_requests`: ok, 457 ms

It reads from: Bitbucket.

### Build report: One timeout, one review.

Main is red because of a checkout test timeout. One pull request still needs a reviewer.

**Failed**

- Pipeline #312, step 3: checkout.spec timed out after 30 seconds.

**Waiting**

- #57: tax rounding, one approval of two.

_Illustrative repository · Nothing merged or commented_

All connectors: https://corespeed.io/docs/connectors

## Read the change. Find what failed

Requests you can make once Bitbucket is connected. The data is fictional.

### Read a pull request

PR #57 · checkout totals · Diff and comments

- Changed: Tax rounding in the cart total
- Open comment: Add a test for zero-tax regions
- A summary, not an approval

### Find why a pipeline failed

main · pipeline #312 · The step log, read for you

- Failed step: Integration tests
- Cause: A timeout in the checkout spec
- Read from the log's tail

### Merge, after a yes

A merge that waits · Approvals hold the write

- Pull request: #57 into main
- Policy: Ask before merging into main
- Held for a person

Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md)

## Keep your agent. Bring your work

One CoreSpeed account, across compatible agents.

1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in.
2. **Connect Bitbucket**: Authorize the account and the content you need.
3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer.

Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor

## Questions

### Does it work with Bitbucket Data Center?

No. The connector works with Bitbucket Cloud workspaces.

### Can my agent merge a pull request?

Yes, if your Bitbucket permissions allow it. Merging is its own tool call, which approvals can hold for a person.

### Can I connect with an API token instead of signing in?

Yes. Supply your Atlassian account email and a Bitbucket API token with the scopes the tools need.

### Do I have to switch agents?

No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once.

### Can my agent access every account in our organization?

No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private.

### Does this work without connecting an account?

No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors

Every tool and price: https://corespeed.io/catalog/bitbucket

## Related pages

- [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents.
- [GitHub for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/github): Turn GitHub issues and pull requests into a clear project update inside your agent, without the tab tour.
- [GitLab for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/gitlab): Bring GitLab merge requests, issues and pipelines into your agent. See what needs review and which pipelines failed.

## Sources

- Connectors: https://corespeed.io/docs/connectors
- Bitbucket pull requests API: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pullrequests/
- Bitbucket pipelines API: https://developer.atlassian.com/cloud/bitbucket/rest/api-group-pipelines/
- Bitbucket API tokens: https://support.atlassian.com/bitbucket-cloud/docs/create-an-api-token/

Reviewed 2026-11-10.

## Links

- Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md)
- All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md)
- Documentation: https://corespeed.io/docs
- Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)