Connect Codex

Drive Brilliant from OpenAI's Codex CLI. Like Claude Code, this one is nearly automatic: if Codex is installed, Brilliant registers itself on launch.

Prerequisites

• The Codex CLI installed.

• Brilliant open. The MCP server only runs while the app is running.

Setup

Automatic

If Brilliant finds a ~/.codex/ directory when it starts, it adds a brilliant entry to ~/.codex/config.toml for you and keeps the address in sync with whichever port it bound to. Nothing to click. Just restart your Codex session so it reads the updated config.

Manual toggle

To add or re-add the connection on demand:

1. Open Settings (Cmd+,) and pick MCP Connections.

2. Flip the Codex CLI row on.

The MCP Connections list with the Codex CLI row toggled on (screenshot coming soon)

Then restart your Codex session.

By hand

The entry in ~/.codex/config.toml is a TOML section:

[mcp_servers.brilliant]
url = "http://127.0.0.1:3333/mcp"

Use 3334 or 3335 if Brilliant reported a fallback port.

Try it

With Brilliant open, ask Codex to design:

• In Brilliant, lay out a dashboard with a KPI row and a chart placeholder.

• Read the Landing canvas in Brilliant and add a testimonials section that fits.

• Export the selected frame in Brilliant as SVG.

Codex driving Brilliant from the terminal, elements appearing on the canvas (screenshot coming soon)

Troubleshooting

• Codex doesn't see the brilliant tools. Restart the Codex session; it reads config.toml on startup.

• No entry appeared automatically. Brilliant only writes to ~/.codex/config.toml when that directory already exists (so it never litters the home folder of non-Codex users). Create the directory or run Codex once, then reopen Brilliant, or add the connection from Settings.

• Calls fail. Brilliant must be running. Launch it and retry.

• Port mismatch. Brilliant rewrites the url to the current port every launch, so restarting Brilliant then your Codex session resolves a stale address. You can also re-toggle the row in Settings.