Busabase for Codex

Connect Codex to Busabase

OpenAI's terminal coding agent, with a built-in MCP client and an /mcp panel.

Paste this into Codex

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.

Read the Codex Skills documentation

Busabase

Agent Skill

Give your agent this one instruction

You end up with more than a connector: the busabase skill carries the whole change-request workflow, the CLI, and the full API — available in every future session without re-pasting anything.

Asks first

Busabase Cloud or Personal Desktop — your call, before anything happens.

Connects

Signs you in and stores the credential itself. No API key to copy by hand.

Seeds a Base

Creates and fills your first Base, so the workspace is not an empty screen.

Installs the skills

busabase and busabase-app-creator become permanent, for every session after this.

Install the Busabase skills

npx skills add busabase/skills

Prefer a connector?

If you would rather wire Busabase in as MCP tools than let the agent install a skill, use the server URL below.

At a glance

Vendor: OpenAI
How it connects: MCP + OAuth · Plugin / Skill
Transport: Streamable HTTP
Authentication: OAuth (dynamic registration)
Config file: ~/.codex/config.toml (project scope: .codex/config.toml, trusted projects only)

Run this

codex mcp add busabase --url https://busabase.com/api/mcp
codex mcp login busabase --scopes mcp

Add the server, start OAuth explicitly if needed, then inspect the connection:

codex mcp add busabase --url https://busabase.com/api/mcp
codex mcp login busabase --scopes mcp
codex mcp list

Inside Codex, use /mcp to confirm that Busabase is connected and its tools are enabled. Then ask it to call auth_verify.

To change the Busabase account or consent grant:

codex mcp logout busabase
codex mcp login busabase --scopes mcp

Remove the configuration entirely with codex mcp remove busabase.

Codex MCP documentation

Known gotchas

Switching the Busabase account or grant needs `codex mcp logout busabase` before logging in again. The current docs also state the scope resolution order: `mcp_servers.<name>.scopes` in config.toml, then the `--scopes` flag on `codex mcp login`, then the scopes in the server's `WWW-Authenticate` challenge or its protected-resource metadata — Busabase advertises the single scope `mcp`, so the recorded `codex mcp login busabase --scopes mcp` matches what Codex would request by default. Codex supports OAuth with both Client ID Metadata Documents (CIMD) and Dynamic Client Registration (DCR).

How it compares

Connection capabilities side by side with other agents already in this directory.

Capability	Codex	Claude Code	Cursor
Type	Terminal agents	Terminal agents	AI editors
Recommended path	Agent Skill	Agent Skill	Agent Skill
How it connects	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill	MCP + OAuth · Plugin / Skill
Transport	Streamable HTTP	Streamable HTTP	Streamable HTTP
Authentication	OAuth (dynamic registration)	OAuth (dynamic registration)	OAuth (dynamic registration)

These stepsFrom official docsLast checked Nov 9, 2026

Written from this agent's own documentation. We have not re-run every step on a real machine, so check the linked docs if a command has changed.

Where these steps come from Official site

Let your agent do the setup

One instruction, one authorization, and every change it makes afterwards carries a message and a diff you can check or revert.

Browse every agent

Paste this into Codex

Read https://busabase.com/SETUP_SKILL.md and set up Busabase for me. Follow it through to the end, then confirm the connection works.