The short answer
- 1Click Add to Cursor on the setup page and confirm the install in Cursor.
- 2Or paste the entry into
~/.cursor/mcp.jsonfor every project, or.cursor/mcp.jsonfor one. - 3Check it under Customize → MCP, then search from the agent chat.
Before you start
- Cursor, 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 Cursor
- 1
Open the setup page, choose the Cursor tab and your system, then click Add to Cursor.
- 2
Cursor opens and shows the server it is about to add. Check that the command is
npx(orcmdon Windows) and confirm.
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:
{
"mcpServers": {
"fable5": {
"command": "npx",
"args": ["--yes", "fable5-cli@latest", "mcp"]
}
}
}{
"mcpServers": {
"fable5": {
"command": "cmd",
"args": ["/c", "npx", "--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.
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.
Try your first search
Searching needs no account, so this is the quickest proof that Cursor 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
Cursor calls
search_skills, maybeget_skillfor a closer look, and answers with real Skills.
A general answer from memory, with no links, means Cursor 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
Cursor 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 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:
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
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?
