Individual install via @genzagentsio/setup
In any terminal: `npx @genzagentsio/setup`. The CLI detects which AI tools you have installed (Claude Desktop, ChatGPT Desktop, Cursor, Cline, Windsurf, Continue.dev) and writes the MCP config block for each. Idempotent — re-running it never duplicates entries. The API key and agent DID are stored in ~/.genzagents-mcp-env (mode 600).
Individual install via manual config
If you prefer hand-editing, the config block is: ```json { "mcpServers": { "genzagents": { "command": "npx", "args": ["-y", "@genzagentsio/mcp-server"] } } } ``` For Claude Desktop: edit `~/Library/Application Support/Claude/claude_desktop_config.json` (macOS) or `%APPDATA%\Claude\claude_desktop_config.json` (Windows). For Cursor: Settings → MCP. For Cline: Settings → MCP Servers. Restart the AI tool after the change.
Team install via MDM
Push `@genzagentsio/setup` via JAMF / Intune / Workspace ONE. The post-install script runs the setup CLI with the `--org-install` flag, reading the org install token from `/etc/genzagents.env` (or the MDM-managed equivalent). Engineers see GenZAgents configured after their next laptop sync; no clicking, no copy-paste.
Verifying the install
Restart the AI tool. Open a new conversation. Type "use the genzagents tool to draft a receipt about hello world". The tool should fire and respond with a draft. Check /dashboard — the draft receipt shows up within seconds.
Common install issues
No tools showing up: restart the AI tool fully (quit + relaunch, not just close the window). Wrong API key: check ~/.genzagents-mcp-env exists and contains GENZAGENTS_API_KEY=<your-key>. Behind a corporate proxy: set HTTPS_PROXY in the env block. Old Node: the MCP server requires Node 18+; check with `node --version`.
Uninstall
Run `npx @genzagentsio/setup --uninstall` — removes the MCP config block from each AI tool's config (preserving other entries), unregisters the laptop, deletes the env file. The AI tools continue working without GenZAgents.