Connecting Bitbucket to Claude and OpenAI Codex

Last updated: October 27, 2026

Bitbucket doesn't have a first-party connector for Claude or OpenAI Codex the way GitHub does. Instead, Atlassian runs its own official Remote MCP Server, which gives an AI coding agent read access to Jira, Confluence and Bitbucket through one connection.

This guide walks you through the easiest way to set up that connection, with steps for both Claude and OpenAI Codex. By the end, your agent can see the Bitbucket repos your account has access to. If your code is on GitHub instead, see Connecting GitHub to Claude or Connecting GitHub to OpenAI Codex.

The agent only sees what your own Bitbucket account can already access. Connecting doesn't give it any extra permissions.

Before you start

You'll need:

  • A Bitbucket Cloud account and an Atlassian account (Bitbucket sign-in runs through Atlassian), with access to the workspace and repos you want the agent to see.

  • One of the following:

    • Claude: Claude Desktop, Claude Code (CLI), or Cowork on claude.ai with connectors enabled.

    • OpenAI Codex: the Codex CLI, the Codex IDE extension, or the ChatGPT desktop app.

    • Another MCP-compatible client, such as VS Code or Cursor.

You don't need any special Bitbucket admin permission to connect.

There are two ways to set this up. Option A lets the agent configure itself with one prompt. Option B walks you through adding the connector yourself. Whichever you pick, finish with Confirm the connection.

Option A: Connect with one prompt (easiest)

  1. Open a chat in Claude (Desktop, Code or Cowork) or in Codex.

  2. Paste this prompt:

Set up the Atlassian remote MCP server for this client using the official guide at https://support.atlassian.com/atlassian-ai-gateway/docs/get-started-with-the-atlassian-remote-mcp-server/ and the MCP server URL https://mcp.atlassian.com/v2/mcp

  1. Complete the Atlassian sign-in when the agent asks. It opens in your browser once the connector is added.

This works for both Claude and Codex because each already knows how to add a remote MCP server from a URL. You're just pointing it at Atlassian's.

Option B: Add the connector manually

If you'd rather not hand the setup to the agent, follow the steps for your tool.

Claude Desktop or Cowork

  1. Go to Settings → Connectors (or Extensions, depending on your version).

  2. Click Browse (or Add connector) and search for Atlassian.

  3. Click Connect, then complete the Atlassian sign-in that opens in your browser.

Claude Code (CLI)

  1. Run:

claude mcp add --transport http atlassian https://mcp.atlassian.com/v2/mcp

  1. Start (or restart) a session. Claude Code asks you to sign in to Atlassian the first time it needs the server.

Codex CLI

  1. Add the server:

codex mcp add atlassian --url https://mcp.atlassian.com/v2/mcp

  1. Sign in:

codex mcp login atlassian

  1. In the browser tab that opens, pick the Atlassian Cloud site to grant access to and approve the consent screen. Codex saves the sign-in for future sessions.

  2. Inside a Codex session, run /mcp to confirm the connector is active.

The same setup works in the Codex IDE extension and the ChatGPT desktop app, because they share the same config.

VS Code

In the Extensions panel, search for @mcp Atlassian and install the connector. You can also use the quick-install link in Atlassian's setup guide. This works whether you use VS Code with Claude or with the Codex extension.

Cursor and other MCP clients

In the client's MCP settings, add a remote HTTP MCP server that points to https://mcp.atlassian.com/v2/mcp. The menu varies by client, but the URL and the Atlassian sign-in are the same everywhere.

Confirm the connection

Back in the agent, check that it can see your Bitbucket data. Replace the placeholder with your own workspace and repo, then paste:

Can you see the [workspace/repo-name] repo in Bitbucket? Summarize the last few commits on main.

If the agent returns real details from the repo, you're done.

Troubleshooting

  • The agent says it has no Bitbucket access. The Atlassian sign-in probably didn't finish. Run Option A or Option B again and complete the sign-in in your browser.

  • The sign-in tab closed before you approved access. Run the setup again and keep the tab open until the Atlassian consent screen confirms access.

  • Codex can't use the connector after you added it. Running codex mcp add doesn't sign you in. Run codex mcp login atlassian to finish.

For more detail on the server itself, see Atlassian's guide, Get started with the Atlassian Remote MCP Server. If you have questions, reach out to your Noibu contact.