Skip to content
BuildBase
BuildBase in your AI tools

Use BuildBase in Codex

BuildBase in your AI tools: connect Codex to BuildBase's own MCP server and manage your BuildBase organization from Codex. You sign in as yourself, and Codex can do only what your role and your organization allow.

Add BuildBase to Codex

The address is the same in every AI tool: https://api.console.buildbase.app/mcp. BuildBase signs you in the first time Codex connects.

  1. In Codex, add a remote MCP server: codex mcp add, or ~/.codex/config.toml. Use the address https://api.console.buildbase.app/mcp, or the command or config below.
  2. Sign in: run codex mcp login buildbase-console. codex mcp login <name> opens a browser to sign in; add --no-browser in a terminal without one. The ChatGPT desktop app starts the sign-in itself.
  3. On BuildBase's sign-in page, sign in as you do to the console, then approve the consent screen, which names Codex and what it asks for.
  4. Ask Codex something, such as "List my BuildBase organizations."
terminalBash
codex mcp add buildbase-console --url https://api.console.buildbase.app/mcp
codex mcp login buildbase-console
~/.codex/config.tomlTOML
[mcp_servers.buildbase-console]
url = "https://api.console.buildbase.app/mcp"

The plan it needs

OpenAI's Codex MCP page does not name a plan for MCP servers.

How sign-in looks in Codex

codex mcp login <name> opens a browser to sign in; add --no-browser in a terminal without one. The ChatGPT desktop app starts the sign-in itself.

What is different in Codex

  • In config.toml, enabled_tools and disabled_tools choose the tools, and default_tools_approval_mode (auto, prompt, writes or approve) decides when Codex asks; tools.<tool>.approval_mode sets one tool.
  • BuildBase adds its own rules on top: each organization is Off, Read only or Read and change for AI agents (Read only by default), and deletes, member and role changes, sends and money moves need your approval in the chat.
  • For a job with nobody to sign in, send one of your organization's API keys as the bearer instead. In config.toml, bearer_token_env_var names an environment variable whose value is sent as the bearer.
  • The Codex CLI, the IDE extension and the ChatGPT desktop app share one configuration.

If it does not work in Codex

Codex needs to sign in again
Run codex mcp login <name> again.
Codex does not connect
/mcp lists the active servers. startup_timeout_sec and tool_timeout_sec raise the timeouts, and /debug-config shows which config file set what.
Codex says the organization does not let agents in
An owner or admin sets the organization's AI agents setting in the console, under Account, then Security. Off turns every agent away, and an owner or admin can also block one agent for one member there.
Codex cannot change anything
The organization is Read only, the default. An owner or admin can switch it to Read and change, and Codex can then make changes without signing in again. Deleting, sending to an audience, roles and money still ask you to approve each change.

Frequently Asked Questions

Which Codex plan do I need?

OpenAI's Codex MCP page does not name a plan for MCP servers.

Can Codex change things in my BuildBase organization?

Only where the organization allows it: Read only is the default. Even then, deletes, member and role changes, sends and money moves need your approval in the chat, and secrets never reach Codex.

Can I connect Codex with an API key instead of signing in?

Yes, for a job with nobody to sign in: send one of your organization's API keys as the bearer. In config.toml, bearer_token_env_var names an environment variable whose value is sent as the bearer. The key works in its own organization only, and the organization's AI agents setting still applies.

Where next