Prerequisites

• Codex CLI installed and set up

  • https://learn.chatgpt.com/docs/codex/cli

• A Noibu account with valid login credentials (used for the OAuth step below)

• Access to edit ~/.codex/config.toml on the machine running Codex

1. Install the Noibu skills

• In Codex, invoke the skill installer: /skill installer

• Then provide this GitHub folder when prompted: https://github.com/Noibu/ai-plugin/tree/main/src/skills

• Codex installs these seven skills into ~/.codex/skills:

  • build-business-context

  • checkout-analysis

  • product-analysis

  • querying-noibu-data

  • segment-analysis

  • store-pulse

  • tech-diagnosis

2. Configure the Noibu MCP connector

1. Open a New Task

2. Run:

Open ~/.codex/config.toml and add:

[mcp_servers.noibu]
enabled = true
url = "<https://mcp.noibu.com/mcp>"

Use url for the hosted Noibu server. Do **not** configure the address as a local command — Noibu's MCP server is hosted, not run locally.

Alternatively:

1. Go to Settings → Configuration in Codex.

   

2. Open ~/.codex/config.toml and add:

[mcp_servers.noibu]
enabled = true
url = "<https://mcp.noibu.com/mcp>"

3. Authenticate with Noibu (OAuth)

Noibu's MCP server uses OAuth (browser login), not a static bearer token, so there's nothing extra to add to config.toml for authentication.

Run:

codex mcp login noibu

Approve the login in the browser window that opens. Once approved, codex mcp list will show Auth: OAuth for the Noibu server.

Alternatively, you can authenticate from the UI:

1. Go to Settings → Plugins → MCPs

2. Find Noibu and click Authenticate

3. Sign in with your Noibu credentials in the browser window that opens

4. Reload Codex and test the connection

1. Restart Codex.

2. Open a new task.

3. Verify the connection

Run:

codex mcp get noibu

The result should show the connector as enabled, using the streamable_http transport, with URL https://mcp.noibu.com/mcp.

Ask Codex to run a Noibu analysis, for example: run /tech-diagnosis on yourdomain.com

Troubleshooting

• "No bearer token configured" message — this is expected. Noibu MCP uses OAuth rather than a static token, so bearer_token_env_var does not apply here; it's only relevant for token-based MCP servers.

  

• If codex mcp login noibu doesn't open a browser window or the login fails, re-check that the url in config.toml matches exactly https://mcp.noibu.com/mcp and that enabled = true is set.

• When conducting a Noibu Analysis, if Codex responds and says that the Noibu data connection isn’t available, this likely means that you need to Authenticate the Noibu MCP connection - see Step 3