Does Codex support the Bitbucket MCP server?

Yes. Codex connects to the Bitbucket MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.

Do I need an API key to connect Bitbucket to Codex?

No. You sign in to Bitbucket once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.

Which Bitbucket tools can Codex use?

All 24 Bitbucket tools your team allows, such as Delete Repository, Browse Source, Get Pull Request. Admins can narrow that list per team.

Can I control which teammates use Bitbucket in Codex?

Yes. Role-based access control decides who can use Bitbucket and which of its tools appear in Codex, and every call is logged with the person's identity.

What if Codex doesn't show Bitbucket tools?

Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.

Connect Bitbucket to Codex (MCP setup guide)

Ask Codex to use the list pull request comments tool in Bitbucket
Ask Codex to use the manage branch restrictions tool in Bitbucket
Ask Codex to use the manage default reviewers tool in Bitbucket
Ask Codex to use the manage webhooks tool in Bitbucket
Ask Codex to use the delete repository tool in Bitbucket

1. Enable Bitbucket in Metorial
In your Metorial portal, enable the Bitbucket MCP server and sign in with the account that owns the data. Access stays governed by your team policies.
2. Add the server and sign in
The Codex CLI, IDE extension and ChatGPT desktop app share this config.
```
codex mcp add metorial --url <your-magic-mcp-url>
codex mcp login metorial
```
3. Check the connection
Type /mcp in Codex to see Metorial and its Bitbucket tools.

Once Bitbucket is enabled in Metorial, teammates sign in with SSO and get the same connection in Codex, with only the tools their role allows.

One link covers every app you approve. See how the MCP gateway handles access, roles and audit logs for the whole company.

Delete Repository: Permanently delete a repository from the workspace.
Browse Source: Browse repository source files at a specific revision (branch, tag, or commit hash).
Get Pull Request: Retrieve detailed information about a specific pull request including its description, reviewers, merge details, and comments summary.
Fork Repository: Fork an existing repository.
Manage Branches: List, create, or delete branches in a repository.
Manage Pull Request: Perform actions on a pull request: **approve**, **unapprove**, **merge**, **decline**, **request_changes**, or **remove_change_request**.
List Workspace Members: List all members in the configured workspace.
Update Repository: Update repository settings (wiki, fork policy, project, privacy, language, name, description).
List Pull Requests: List pull requests for a repository.
Manage Projects: List, create, update, or delete projects in the workspace.
Manage Pipelines: List, get, trigger, or stop Bitbucket Pipelines.
Create Pull Request: Create a new pull request to merge changes from a source branch into a destination branch.
Search Code: Search for code across repositories in the workspace, optionally scoped to one repository.
List Commits: List commits in a repository, optionally filtered by branch.
Create Repository: Create a new Git repository in the configured workspace.
And 9 more on the Bitbucket MCP server page.

Limit which Bitbucket tools Codex sees with enabled_tools and disabled_tools on the metorial server in config.toml.
Set default_tools_approval_mode to auto, prompt, writes or approve. writes prompts only for tools that are not marked read-only.
Type /mcp in the composer to see the connected servers.
Override the approval behavior for a single Bitbucket tool with tools.<tool>.approval_mode.

Metorial is listed but tools are missing: Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.
Metorial times out at startup: Codex waits 10 seconds by default. Raise startup_timeout_sec under [mcp_servers.metorial] in ~/.codex/config.toml.
Long tool calls fail after a minute: The default tool timeout is 60 seconds. Raise tool_timeout_sec for the metorial server in config.toml.

Based on the Codex MCP documentation.

Frequently asked questions

Common questions about connecting Bitbucket to AI agents with Metorial.

Does Codex support the Bitbucket MCP server?
Yes. Codex connects to the Bitbucket MCP server through one CLI command, pointed at your Metorial URL. You need the Codex CLI, IDE extension or ChatGPT desktop app.
Do I need an API key to connect Bitbucket to Codex?
No. You sign in to Bitbucket once through Metorial, and Codex uses that connection. No API keys go into Codex's settings.
Which Bitbucket tools can Codex use?
All 24 Bitbucket tools your team allows, such as Delete Repository, Browse Source, Get Pull Request. Admins can narrow that list per team.
Can I control which teammates use Bitbucket in Codex?
Yes. Role-based access control decides who can use Bitbucket and which of its tools appear in Codex, and every call is logged with the person's identity.
What if Codex doesn't show Bitbucket tools?
Codex can connect without credentials and then see nothing. Run codex mcp login metorial to complete the OAuth sign-in.