feat(cli): configure MCP natively across coding agents

Replace the subprocess installer in `setup mcp` with a built-in one that
detects installed agents, pre-selects them in a picker, and offers to install
rules telling those agents to prefer Firecrawl for web search and scraping.

Covers Claude Code, Cursor, VS Code, Codex, OpenCode, Windsurf, Zed, Hermes
Agent, and OpenClaw through per-agent flags, `--project` for project scope, and
`--rules` / `--no-rules` for scripted runs. `-y` stays MCP-only. The two
launchers were previously reachable only by flag, so a plain `setup mcp` never
offered them; they now sit in the picker alongside the editors, and because a
launcher shells out to a CLI, a missing binary is reported against that one
agent instead of ending the run.

Credential handling is unchanged in principle and stricter in reach: an API key
is never written as a literal. Knowing which agents were selected means each one
receives a reference to FIRECRAWL_API_KEY in the syntax it expands, so the setup
no longer has to refuse a run that omits --agent. Agents with no verified syntax
fall back to the keyless endpoint and say so rather than persisting a secret.

Config edits are surgical. JSON is patched through a JSONC-aware editor so
commented settings files parse at all and keep their comments, and TOML tables
are replaced along with any stale sub-tables left by a previous stdio entry.
Reruns are byte-identical.

Also gives every setup test a throwaway HOME and resets spawn mocks between
tests, since MCP setup now writes real config files and would otherwise rewrite
the developer's own agent settings; and teaches doctor about the `servers` and
`context_servers` keys so those registrations are recognized.

Author: Max17190

README.md

@@ -75,12 +75,40 @@ firecrawl setup skills
 firecrawl setup workflows
 ```
 
-To install the Firecrawl MCP server into your editors (Cursor, Claude Code, VS Code, etc.):
+To install the Firecrawl MCP server into your coding agents:
 
 ```bash
 firecrawl setup mcp
 ```
 
+This detects which agents you have installed, pre-selects them in a picker, and
+asks whether to add rules telling those agents to prefer Firecrawl for web
+search and scraping. Supported agents are Claude Code, Cursor, VS Code, Codex,
+OpenCode, Windsurf, Zed, Hermes Agent, and OpenClaw.
+
+Pass agent flags to skip the picker, `-y` to configure every detected agent
+(MCP only), or `--project` to write to the current project instead of your
+global agent settings:
+
+```bash
+firecrawl setup mcp --claude --cursor    # skip the picker
+firecrawl setup mcp -y                   # every detected agent, MCP only
+firecrawl setup mcp -y --rules           # ...and install the rules too
+firecrawl setup mcp --project --cursor   # write project config
+```
+
+Rerun the command any time to update an existing setup or add another agent; it
+edits only the Firecrawl entry and leaves the rest of each config alone.
+
+Your API key is never written into an agent config. When `FIRECRAWL_API_KEY` is
+exported in the environment your agents run under, each agent gets a reference
+to that variable in the syntax it understands. Otherwise setup stays keyless,
+which still serves search, scrape, and parse under an anonymous rate limit. Use
+`--keyless` to force the anonymous path even when a key is available.
+
+Not every agent supports project-level MCP configuration. Those agents always
+receive the global configuration.
+
 To make Firecrawl the default web provider for supported AI agents:
 
 ```bash

package.json

@@ -74,6 +74,7 @@
     "@inquirer/prompts": "^8.2.1",
     "commander": "^14.0.2",
     "firecrawl": "4.24.0",
+    "jsonc-parser": "3.3.1",
     "yaml": "^2.9.0",
     "zod-to-json-schema": "3.24.6"
   }