Connect MCP with Codex

Configure the B6AI MCP server so Codex can build and manage your bots in natural language.

5 min read

Overview

B6AI ships a hosted Model Context Protocol server, `b6ai-bot-builder`, that lets an AI client build and manage your bots (intents, utterances, knowledge and flows) from natural-language instructions. Once Codex is connected, you can ask it to "create a support bot that handles order status and refunds" and it authors a complete bot in your workspace.

The server speaks MCP over HTTP and authenticates every request with your workspace identity, so Codex only ever sees what your role is allowed to see.

Before you start

You need an active B6AI workspace and permission to build bots (Enterprise Admin or Agent Admin). Codex reads MCP servers from its config file.

Prerequisites

A B6AI workspace with the MCP server enabled on your plan.
The Codex application installed and updated to a version that supports remote MCP servers.
Your B6AI MCP endpoint (https://mcp.b6ai.ai/mcp) and a way to sign in, the server authorizes you through B6AI’s identity provider (Keycloak / OAuth 2.0).

Get your B6AI MCP endpoint

The MCP endpoint is workspace-specific. Copy it from your workspace, or ask your administrator for it. Authentication uses OAuth 2.0 against B6AI’s identity provider, the client opens a sign-in window the first time it connects, so you do not paste long-lived secrets into config files where the client supports OAuth.

text

https://mcp.b6ai.ai/mcp

Add the server to ~/.codex/config.toml

Add the B6AI MCP server to Codex using the configuration below, then restart the client so it loads the new server.

toml

[mcp_servers.b6ai]
url = "https://mcp.b6ai.ai/mcp"
# Codex opens the browser OAuth flow on first use.

Keep tokens safe

If your client uses a static bearer token instead of interactive OAuth, treat it like a password: never commit it to source control, and rotate it if it is exposed.

Verify the connection

Restart Codex and confirm the b6ai server initializes without errors.

Open the tools / connectors list in Codex and confirm `b6ai-bot-builder` appears as connected.
Ask Codex to list your bots, or to describe what it can do with B6AI.
Ask it to create a simple test bot, then open Bot Builder in B6AI to confirm the bot was created.

Connected

Codex can now build and manage bots in your B6AI workspace with your permissions.

Troubleshooting

Symptom	Likely cause	Resolution
Server not listed	Config not loaded	Check the config path and fully restart Codex.
Sign-in loop / 401	Auth not completed or token expired	Re-run the sign-in flow, or regenerate the token and update the header.
No bots returned	Account has no bots or lacks permission	Confirm your B6AI role can build bots and that the workspace has at least one bot.
Tool calls rejected	Endpoint or transport mismatch	Confirm the URL ends in `/mcp` and matches the transport Codex expects.

Was this page helpful?

Connect MCP with ChatGPT

Connect MCP with Gemini