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 Cursor

Cursor installs The Frontier Brief server from a link, or from a few lines in mcp.json. Either way it takes a couple of minutes and no API key.

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

The short answer

  1. 1Click Add to Cursor on the setup page and confirm the install in Cursor.
  2. 2Or paste the entry into ~/.cursor/mcp.json for every project, or .cursor/mcp.json for one.
  3. 3Check it under Customize → MCP, then search from the agent chat.

Before you start

  • Cursor, 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 Cursor

  1. 1

    Open the setup page, choose the Cursor tab and your system, then click Add to Cursor.

  2. 2

    Cursor opens and shows the server it is about to add. Check that the command is npx (or cmd on Windows) and confirm.

    Opening Cursor is not the same as being connected. Finish the install there, then do the check below.

The link carries only the server’s name and the command that starts it; Cursor shows both before it saves anything. It writes the same entry you would type by hand, into your global ~/.cursor/mcp.json.

Rather edit the file? Merge this into ~/.cursor/mcp.json and keep any servers already in it:

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

Check that Cursor is connected

Open Customize → MCP. The Frontier Brief should be listed with a green dot and its tools. A grey or red dot means it did not start; see the next sections.

You should see: fable5 switched on, with 12 tools.

Click the server to see its tools. You can switch single tools off there, for example the ones that change files, if you only want Cursor to search. In the agent chat, Cursor asks before it runs a tool unless you have turned on auto-run.

Authorize when you install

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

Nothing happened after the link

Cursor was not installed or not set to open these links. Use the file method instead.

Listed, but red

The first npx download timed out. Warm the cache below, then turn the server off and on.

Tools never used

Ask in the agent chat, not the inline editor, and name The Frontier Brief once.

Red after an update

The package cache holds a broken download. Run the warm-up below again; npx refreshes it.

Two The Frontier Brief entries

The link and a hand-written entry under another name. Delete one.

Cursor writes each server’s start-up messages to the Output panel (choose MCP Logs in its list). An error there names the cause, usually a missing node or a typo in mcp.json.

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

Switch the server off in Customize → MCP, or delete its entry from mcp.json. Installed Skills stay where they are.

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.

Skills Cursor installs through the server go to ~/.agents/skills/, the folder Cursor reads Skills from, unless you ask for project scope and give the repository’s path. Add a line to your project rules, such as “search The Frontier Brief with its MCP tools when I ask for a Skill”, so the agent reaches for the server by itself.

Common questions

Is the install link safe?

It only carries the server’s name and its npx command, which Cursor shows before you confirm. No key or token is in it.

Global or project file?

~/.cursor/mcp.json gives every project the server. .cursor/mcp.json in a repository limits it to that one, and you can commit it.

Do I need to restart Cursor?

Usually not; new servers start when you save the file. If it stays grey, reload the window.

Sources

Did this guide help?