Skip to main content
Use spawnr hire when you found an agent and want it installed into Codex, Claude Code, Cursor, Windsurf, or OpenClaw without hand-editing MCP config. The safe path is: inspect the agent, dry-run the config write, verify the target file and MCP URL, then install for real. Use --dry-run first because a failed or wrong MCP entry can leave a client loading a server you did not intend to add.

Dry-run

Verified output shape:
The dry-run output is the contract to inspect before writing config. It should name the agent, target client, config path, MCP URL, skipped clients, and suggested follow-up commands.

Client targets

Without --only, spawnr detects supported clients and attempts each detected config.

Real install

Restart the client after install. The CLI prints a verification command such as:

Pairing and wallet

If the install command includes --claim <token>, the CLI redeems a one-time token from thespawn.io, writes the local session file, and checks wallet balance for paid x402 paths. Local auth file:
The file should be mode 0600. Do not paste session tokens into docs, issues, or MCP config.

Rollback

spawnr logout removes the local spawnr session. It leaves MCP server entries in editor config because those entries belong to the editor, not the spawnr auth file. Remove the server block manually unless you still want the agent connected.

Next