Black Friday: Lock in your founding rate.Compare plans

Every Premium Skill for $19.9/month. Cancel anytime. See plans

Skip to content

Add The Frontier Brief MCP to Codex

Codex keeps its MCP servers in one file that the CLI, the IDE extension and the ChatGPT desktop app all read. Add The Frontier Brief there once and it works in each.

For
People who use Codex
Time
About 5 minutes
Checked
7 Nov 2026

The short answer

  1. 1Run codex mcp add once; the entry lands in ~/.codex/config.toml.
  2. 2The Codex CLI, the IDE extension and the desktop app share that file, so there is nothing to repeat.
  3. 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 --version prints v22 or 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.

Terminal
codex mcp add fable5 -- npx --yes fable5-cli@latest mcp

Prefer to edit the file? Add this table to ~/.codex/config.toml (on Windows use the cmd version from the setup page):

~/.codex/config.toml
[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

Terminal
codex mcp list

In a Codex session, /mcp shows the same list with each server’s tools.

You should see: fable5 in the list, enabled.

Authorize when you install

Codex only needs your account when it downloads or installs a Skill. It asks the server for a sign-in and shows you a link and a short code; nothing is typed into a terminal, and no password or key goes through the chat.

  1. 1

    Ask Codex to install a Skill you picked. It calls connect_account and shows the link and the code.

    You should see: A link to https://fable5.app/device and a short code.

  2. 2

    Open the link, check the code matches and approve. Come back to the chat; it calls connection_status and carries on.

    You should see: “Connected”, then the install with the folder and version it used.

The approval lasts 7 days and is not renewed on its own. It lives in your system keychain (Keychain on macOS, Credential Manager on Windows, GNOME Keyring or KWallet on Linux, or a file only you can read where there is none), never in the chat or the config file. The fable5-cli terminal commands share it, so signing in on one signs in the other.

Free Skills install with any account. For a paid Skill your account doesn’t have yet, the agent shows the price and the purchase link instead of installing; nothing is charged until you buy it yourself. Each account can download 50 different Skills a day across MCP, the CLI and the website.

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:

Terminal
npx --yes fable5-cli@latest mcp
# Windows: cmd /c npx --yes fable5-cli@latest mcp

Still 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

Terminal
codex mcp remove fable5

To 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?