marrow-setup

Set up Marrow in your AI agent (MCP) with one disposable command — run once via npx, nothing to install.

Marrow is a crawler for AI agents: scout, read, crawl and watch the web, with chunk-level change tracking and flat-rate monitoring. marrow-setup doesn't fetch anything itself — it gets you a key and wires the Marrow MCP server into your agent. Day-to-day, your agent uses the MCP tools (or the REST API); you never run this again.

Quick start

# No key yet? Sign up free (email in, key out) and wire up everything:
npx -y marrow-setup --email [email protected]

That single command gets you a key (or paste an existing one), detects your agents (Claude Code, Cursor, Claude Desktop, VS Code, Codex, Windsurf, Antigravity), installs the marrow MCP server into each, and adds the scout → read skill for Claude Code. Then it's done — there is nothing installed to maintain.

Auth: signup vs login

There is no password — your API key is the credential (like gh auth / stripe login).

• signup --email [email protected] — email in, free key out, saved automatically.
• login --api-key mrw_xxx — store a key you already have (e.g. from a paid plan).

Commands

Run any of these as npx -y marrow-setup <command>:

| Command | What it does | |---|---| | (none) | Key (paste or signup) + MCP install + scout→read skill, in one go | | signup --email [email protected] | Get a free API key and save it | | login --api-key mrw_xxx | Save an API key you already have (~/.config/marrow/config.json) | | upgrade --plan pro | Upgrade your saved key in place — opens Stripe Checkout; your agents stay wired and credits just go up | | setup mcp | (Re)install the Marrow MCP server into detected agents | | setup skill | Install the scout→read skill (Claude Code) — --undo to remove | | setup defaults | Route web access through Marrow (denies native WebSearch/WebFetch in Claude Code) — --undo to reverse |

Options

| Flag | Meaning | |---|---| | --email [email protected] | Email for the free key (signup) | | --plan developer\|pro | Plan for upgrade | | --api-key mrw_xxx | API key (else MARROW_API_KEY env, or saved) | | --api-url URL | Override the API endpoint (self-host / edge) | | --target a,b,c | Force specific clients: claude-code, cursor, claude-desktop, vscode, codex, windsurf, antigravity | | --all | Install into every known client | | --undo | Reverse setup skill / setup defaults | | -y, --yes | Non-interactive (needs --email or --api-key) |

What it writes

• Claude Code — via claude mcp add (user scope)
• Cursor / Claude Desktop / Windsurf / Antigravity — mcpServers JSON
• VS Code — .vscode/mcp.json (servers)
• Codex — ~/.codex/config.toml ([mcp_servers.marrow])

Existing config files are backed up to <file>.marrow.bak before editing, and the marrow entry is merged in (idempotent — re-running replaces, never duplicates). When no agent is detected, it prints a ready-to-paste snippet instead of guessing.

Notes

• The MCP server itself is @marrowdev/cloud-mcp (npx -y @marrowdev/cloud-mcp), launched per-client with your MARROW_API_KEY. marrow-setup just configures it.
• This is a disposable installer, not a long-lived CLI — there is intentionally no global install and no standalone binary. If a scriptable, daily-use marrow binary (scout / read / crawl / monitor with Flux output) is ever warranted, it would ship separately.

MIT