Skip to content
B6AIDocs

Connect MCP with Codex

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

5 min readLast updated

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

  1. A B6AI workspace with the MCP server enabled on your plan.
  2. The Codex application installed and updated to a version that supports remote MCP servers.
  3. 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).
  4. The OAuth client ID `b6ai-mcp`. B6AI does not allow clients to register themselves, so Codex cannot obtain this automatically.

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

Use the B6AI OAuth client ID

Most MCP clients try to register themselves with the authorization server the first time they connect (dynamic client registration). B6AI switches that off on purpose, because anything that can reach the identity provider could otherwise create its own OAuth client. Instead, B6AI publishes one pre-approved client that every user shares.

When Codex asks for an OAuth client ID, enter the value below. Leave it blank and registration fails before you ever reach the sign-in page.

text
b6ai-mcp
This is not a secret
The client ID identifies the application, not you. It is a public value, safe to share with your team and to paste into a client’s settings. Your own credentials are only ever entered on the B6AI sign-in page.

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.

  1. Open the tools / connectors list in Codex and confirm `b6ai-bot-builder` appears as connected.
  2. Ask Codex to list your bots, or to describe what it can do with B6AI.
  3. 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

SymptomLikely causeResolution
Could not register with B6AI’s sign-in serviceNo OAuth client ID supplied; B6AI does not allow self-registrationEnter `b6ai-mcp` as the OAuth client ID in Codex, then connect again.
Server not listedConfig not loadedCheck the config path and fully restart Codex.
Sign-in loop / 401Auth not completed or token expiredRe-run the sign-in flow, or regenerate the token and update the header.
No bots returnedAccount has no bots or lacks permissionConfirm your B6AI role can build bots and that the workspace has at least one bot.
Tool calls rejectedEndpoint or transport mismatchConfirm the URL ends in `/mcp` and matches the transport Codex expects.
Was this page helpful?