How to Connect Codex to Bitbucket (and What It Can't Do)
Not natively — but as of April 2026, there’s a real official path. OpenAI Codex is built around GitHub: cloud tasks, @codex mentions, and automatic PR reviews all require a connected GitHub account, and none of that exists for Bitbucket. What changed this spring is Atlassian’s side: the Atlassian Rovo MCP server now supports Bitbucket Cloud (announced April 8, 2026), and Codex supports MCP servers. Connect the two and Codex can browse your repositories, read pull requests, leave comments, and even open PRs — from a terminal session you’re driving. What you don’t get is any of Codex’s event-driven GitHub behavior, and you don’t get an assistant that watches Bitbucket for you.
Here’s what actually works, how to set it up, the auth caveat worth knowing, and what to use for the operational layer around your Bitbucket activity.
What Codex can actually do with Bitbucket
Since July 9, 2026, Codex lives as a surface inside the single ChatGPT app on every plan, usage-metered — and its MCP support (CLI, desktop app, and IDE extension share one config) is how Bitbucket gets in. Through the Rovo MCP server at https://mcp.atlassian.com/v1/mcp, Codex can:
- Browse workspaces and repositories — list repos, walk branches, read file contents without cloning.
- Work the pull request lifecycle — create PRs, fetch diffs, leave comments, approve, and merge.
- Check pipeline results — read Bitbucket Pipelines status for context on why a build broke.
- Combine it with local work — Codex CLI operates on any local git checkout, so a repo cloned from Bitbucket has always been fair game for editing, testing, and committing. The MCP server adds the Bitbucket-side context (PRs, comments, pipelines) plain git can’t see.
One bonus: because it’s the same Atlassian MCP server that handles Jira and Confluence, a single connection gives Codex your tickets and docs alongside your code — genuinely useful when a PR references a Jira issue.
How to set it up
Setup is developer plumbing with one Bitbucket-specific wrinkle:
- Your Bitbucket Cloud workspace must be linked to an Atlassian organization — the Rovo MCP Bitbucket tools require it.
- Add the server to Codex over Streamable HTTP:
codex mcp add atlassian --url https://mcp.atlassian.com/v1/mcp(or via Settings → MCP servers in the ChatGPT desktop app). - Authenticate. Here’s the wrinkle: while Jira and Confluence tools use OAuth, Bitbucket tools currently rely on API token authentication — Atlassian says OAuth for Bitbucket is on the way but not shipped. You’ll create an API token and configure it rather than clicking through a consent screen.
- Ask Codex something Bitbucket-shaped (“list open PRs on our main repo”) to confirm the tools resolve.
If you don’t manage API tokens and MCP configs for a living, this is not a five-minute connect.
The limits that actually matter
- Zero native support means zero event layer. On GitHub, Codex reviews every new PR automatically if you turn it on. On Bitbucket, nothing fires when a PR opens, a pipeline fails, or a comment lands — Codex only acts when you’re in a session asking.
- The auth is behind GitHub’s experience. API-token auth instead of OAuth means more manual setup and a credential to rotate. Fine for a developer; a non-starter for anyone else.
- It’s a coding agent, not a Bitbucket ops manager. Codex will read the diff and fix the failing test. It won’t chase a PR that’s sat unreviewed for two days, route an incoming issue, or send your team a weekly shipped-list.
Codex + Bitbucket MCP is great for “read this PR, find the bug, push a fix.” It is not built for “keep our Bitbucket activity moving and keep people informed.”
If you want Bitbucket work handled by an assistant: Carly
The moment you want Bitbucket handled — a PR that sits unreviewed for 24 hours pings its reviewer in Slack, a failed pipeline on main becomes a Jira ticket, a Friday email summarizes what merged — you’re past what a session-scoped coding agent does.
That’s where Carly fits. Carly is an AI executive assistant built to act on triggers across your whole stack, set up by conversation instead of API tokens:
- No-code setup. Tell Carly “when a Bitbucket pipeline fails on main, create a Jira ticket and post to Slack” in plain English; it interviews you and builds the workflow.
- Fires on events, 24/7, in the cloud — nothing to keep running on your machine, no token config.
- Connects Bitbucket to the rest of your work — repo activity flows into email, Slack, Jira, and your calendar.
- Actually sends and updates — drafts and sends email (Gmail and Outlook), posts messages, files and updates tickets.
AI agents start at $35/month, and workflow steps that don’t use AI run free and unlimited. Carly connects to 200+ tools natively — including Bitbucket — and reaches anything else via your own API key.
Codex + Bitbucket vs Carly
| Codex (Bitbucket via Rovo MCP) | Carly | |
|---|---|---|
| Native Bitbucket support | No (Atlassian MCP required) | Yes (/integrations/bitbucket) |
| Purpose | Write and fix code with Bitbucket context | Handle Bitbucket + ops work |
| Setup | MCP config + API token | Describe it in plain English |
| Reads repos, PRs, pipelines | Yes (in-session) | Yes |
| Acts on triggers (PR opens, pipeline fails) | No | Yes |
| Chases reviews / sends digests | No | Yes (email, Slack) |
| Runs without your machine | No (session-scoped) | Yes (cloud, 24/7) |
| Built for | Developers | Execs, EAs, operators |
| Pricing | ChatGPT plan (usage-metered) | AI agents from $35/mo |
Codex-with-Bitbucket is a coding agent that can see your Bitbucket context during a session. Carly is an assistant that works your Bitbucket activity into the rest of your day.
Frequently Asked Questions
Does OpenAI Codex integrate with Bitbucket natively?
No. Codex’s built-in code-hosting features — cloud tasks, @codex mentions, automatic PR review — are GitHub-only. Bitbucket access comes via the Atlassian Rovo MCP server, which added Bitbucket Cloud support in April 2026 and which you connect to Codex yourself.
How do I connect Codex to Bitbucket?
Add Atlassian’s remote MCP server (https://mcp.atlassian.com/v1/mcp) to Codex via codex mcp add or the ChatGPT desktop app’s MCP settings, then authenticate. Note that Bitbucket tools currently use API token auth rather than OAuth, and your workspace must be linked to an Atlassian organization.
Can Codex review Bitbucket pull requests automatically?
No. Automatic PR review is a GitHub-only Codex feature. Via MCP, Codex can fetch a Bitbucket PR’s diff and comment on it — but only during a session you start, not automatically when the PR opens.
Can Codex monitor Bitbucket pipelines or chase stale PRs?
No. The MCP connection is session-scoped. For trigger-based Bitbucket automation — pipeline-failure alerts, stale-PR nudges, merge digests — use an agent platform like Carly, which connects to Bitbucket natively and runs 24/7 in the cloud.
More: Codex + GitHub · Codex + GitLab · Codex + Slack · Claude + Bitbucket · ChatGPT MCP explained · Codex alternatives
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
