The short answer
- 1Run
codex mcp addonce; the entry lands in~/.codex/config.toml. - 2The Codex CLI, the IDE extension and the desktop app share that file, so there is nothing to repeat.
- 3Check it with
codex mcp list, then search; approve a sign-in the first time you install.
Before you start
- The Codex CLI, IDE extension or desktop app, up to date.
- Node.js 22 or newer:
node --versionprintsv22or higher. - macOS, Windows or Linux. No API key, and no account until you install something.
Add The Frontier Brief to Codex
Run the line for your system in a terminal. The desktop app and the IDE extension pick it up the next time they start.
codex mcp add fable5 -- npx --yes fable5-cli@latest mcpcodex mcp add fable5 -- cmd /c npx --yes fable5-cli@latest mcpPrefer to edit the file? Add this table to ~/.codex/config.toml (on Windows use the cmd version from the setup page):
[mcp_servers.fable5]
command = "npx"
args = ["--yes", "fable5-cli@latest", "mcp"]Codex starts the server at the beginning of each session. The very first start takes a little longer, because npx downloads the fable5-cli package; after that it comes from the cache. The entry names the newest published version (@latest), so a new release reaches you the next time a session starts.
Check that Codex is connected
codex mcp listIn a Codex session, /mcp shows the same list with each server’s tools.
Try your first search
Searching needs no account, so this is the quickest proof that Codex reached the server. Start a new chat, so the server’s tools are loaded, and paste the prompt:
- 1
Send the prompt as it is.
Prompt Use The Frontier Brief MCP server to find three Skills that make product demos. For each, give me the preview link, what it needs from me, its dependencies and any outside costs. Don't install or run anything yet. - 2
Codex calls
search_skills, maybeget_skillfor a closer look, and answers with real Skills.
A general answer from memory, with no links, means Codex did not use the server: it is not loaded yet, or the chat started before you added it. Open a new one and ask again, naming The Frontier Brief once so the agent knows which tools you mean.
Once it works, ask the way you would ask a colleague. The agent reads each Skill’s inputs, dependencies and cost notes before it suggests one, so say what matters to you:
- “Find a Skill for a pitch deck I can edit in PowerPoint, nothing that needs an API key.”
- “Compare the two best launch-video Skills: what each needs from me and what it costs to run.”
- “Show me the preview for the first one, then wait for me to decide.”
Find and compare
Codex searches by the result you want, reads each Skill’s inputs, dependencies and costs, and shows previews before anything is installed.
Install where you say
It installs the version you picked into the agent folder and scope you name, and never replaces a Skill that is already there.
Keep it current
It checks the Skills it installed against their published versions and updates one only after you approve that version, keeping the old folder.
If Codex can’t see The Frontier Brief
Not in /mcp
Codex read the file before you changed it. Start a new session or restart the app.
Times out on start
The first npx download is slow. Warm the cache below; you can also raise startup_timeout_sec in the table.
Config error on launch
A TOML typo, often a missing quote. Fix it and start again.
Two The Frontier Brief tables
The command and a hand-written entry both exist under different names. Keep one.
Works in the CLI, not the app
The app was open while you edited the file. Quit it fully and open it again.
The first start downloads the package, and some clients give up before that finishes. Run it once by hand so npm caches it; it waits silently for a client, so stop it with Ctrl+C:
npx --yes fable5-cli@latest mcp
# Windows: cmd /c npx --yes fable5-cli@latest mcpStill nothing? Check node --version in the same terminal: anything below 22 makes the server stop at once. Apps opened from the dock or the Start menu sometimes see an older PATH than your terminal, so after installing Node.js, quit the client completely and open it again.
Remove or disconnect
codex mcp remove fable5To sign this computer out, ask the agent to disconnect your Frontier Brief account. It calls disconnect_account, which revokes the sign-in on the server and deletes it from the keychain; the terminal commands are signed out too.
Neither step touches the Skills you installed: they are ordinary folders and keep working in your agent. To remove one, delete its folder from the Skills folder it was installed into; the agent can tell you the path with list_installed_skills.
Reference
Every tool, its parameters, limits and replies are listed in the The Frontier Brief MCP tool reference. The agent-readable setup lives at /install/mcp.md.
- Discovery:
search_skills,get_skill. No account needed. - Account:
connect_account,connection_status,account_status,disconnect_account,get_skill_access. - Downloads and installs:
download_skill,install_skill,list_installed_skills,check_updates,update_skill.
Codex reads project instructions from AGENTS.md as well. A line there such as “use The Frontier Brief MCP server to look for Skills” makes it reach for the server without being asked.
Skills that Codex installs through the server go to ~/.agents/skills/ unless you name a project folder; that is the folder Codex reads Skills from. Ask for “project scope” and give the repository’s path to keep one inside .agents/skills/ there instead.
Common questions
Do I set it up again for the ChatGPT desktop app?
No. The app reads the same ~/.codex/config.toml as the CLI and the IDE extension. Restart it after adding the entry.
Can I use it in one project only?
Codex has no per-project MCP command. Leave the server in your user config and say in that project’s AGENTS.md when to use it.
Why is the first start slow?
npx downloads the package the first time. After that it starts from the cache in a second or two.
Sources
Did this guide help?
