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 Claude Code

One command adds The Frontier Brief server to Claude Code on macOS, Windows or Linux. Then you search, compare and install Skills without leaving the session.

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

The short answer

  1. 1Run claude mcp add once with --scope user and the server is there in every project.
  2. 2Check it with claude mcp get fable5, or type /mcp inside a session.
  3. 3Search right away; approve a sign-in in your browser the first time you install.

Before you start

  • Claude Code, 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.
  • A terminal where the claude command works.

Add The Frontier Brief to Claude Code

Paste the line for your system into a terminal. It saves a user-scope entry, so every project you open with Claude Code gets the server.

Terminal
claude mcp add --scope user --transport stdio fable5 -- npx --yes fable5-cli@latest mcp

Only want it in one repository? Use the project scope instead. Claude Code then writes .mcp.json in that repository, which you can commit for your team:

Terminal, inside the repository
claude mcp add --scope project --transport stdio fable5 -- npx --yes fable5-cli@latest mcp

Claude Code knows three scopes. Pick the one that matches who should have the server:

--scope user

You, in every project on this computer. Saved in ~/.claude.json. The right choice for most people.

--scope project

Everyone who opens this repository. Saved in .mcp.json at its root, ready to commit; each person approves it once.

--scope local

You, in this project only, without touching the repository. The default when you leave --scope out.

The part after -- is the command Claude Code runs to start the server. It is the same on every client: npx fetches the newest published fable5-cli and starts its mcp command, which talks to Claude Code over stdio and to The Frontier Brief over HTTPS.

Check Claude Code is connected

Terminal
claude mcp get fable5

It prints the scope, the command and the status. Inside a session, /mcp lists every server; The Frontier Brief should show as connected with 12 tools.

You should see: fable5 with its npx command and a connected status.

In /mcp, choose The Frontier Brief to see its tools one by one. Claude Code names them mcp__fable5__search_skills and so on, and asks before it calls one for the first time. Choose “Yes, and don’t ask again” for the read-only tools if the prompts get in the way; the ones that download or install will keep asking unless you allow them too.

Authorize when you install

Claude Code 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 Claude Code 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 Claude Code can’t see The Frontier Brief

Not in /mcp

The session started before you added it. Quit it and run claude again.

“Failed to connect”

The first download was slow. Warm the cache below, then restart.

Missing in one project

A project-scope entry with the same name wins there. Remove it or rename one.

Shown as “needs approval”

It is a project server from .mcp.json you haven’t approved yet. Run claude in that repository and accept it.

Tools listed, never used

Claude answered from memory. Name The Frontier Brief in the request, or add a line about it to the project’s CLAUDE.md.

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

Removing the entry stops Claude Code starting the server; your installed Skills stay where they are. Use the scope you added it with:

Terminal
claude mcp remove fable5 --scope user

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.

Ask in plain words

Say what you want made. Claude Code picks The Frontier Brief tools it needs.

Approve once a week

The browser approval lasts 7 days. When it ends, the agent asks again.

Check for updates

Ask “are my Skills up to date?” and approve the versions you want.

To have Claude Code reach for the server without being asked, add a line to CLAUDE.md such as “When I ask for a Skill, search The Frontier Brief with its MCP tools and show me the options before installing.” Claude reads that file at the start of every session.

The entry the command writes, for when you edit ~/.claude.json by hand:

~/.claude.json
{
  "mcpServers": {
    "fable5": {
      "command": "npx",
      "args": ["--yes", "fable5-cli@latest", "mcp"]
    }
  }
}

Common questions

Do I have to add it again in every project?

No. --scope user makes it available everywhere you run Claude Code. Use --scope project only when one repository should have it.

Do I need to restart Claude Code?

Start a new session after adding it. A session that was already open keeps the servers it began with.

Can my team share the setup?

Yes. Add it with --scope project and commit .mcp.json. Everyone who opens the repository runs npx --yes fable5-cli@latest mcp and signs in with their own account.

Sources

Did this guide help?