Installation
These four editors live under See more editors… in npx zephex setup. Every flow starts the same way: browser sign-in on zephex.dev, then either a config file is written on disk (Crush, Hermes, Kilo) or you finish in ChatGPT with OAuth (no local mcp.json).
npx -y zephex setup --crush — writes crush.jsonnpx -y zephex setup --hermes — writes ~/.hermes/config.yamlnpx -y zephex setup --chatgpt — zephex.dev sign-in only; terminal steps for ChatGPT (you open ChatGPT yourself)npx -y zephex setup --kilo — writes kilo.jsonc (local npx zephex)Skip the picker with a flag, or run npx zephex setup and choose See more editors…. Add --project for Crush or Kilo to write project-scoped files in the current directory.
Already have a key? One command still works — paste your real Zephex key (from zephex.dev/dashboard/keys), not a random string. It must start with mcp_prod_, mcp_dev_, or mcp_sk_:
npx -y zephex setup --crush --api-key mcp_prod_your-key-herenpx -y zephex setup --hermes --api-key mcp_prod_your-key-herenpx -y zephex setup --kilo --api-key mcp_prod_your-key-hereThat skips the browser sign-in, writes the editor config file, and saves the key to ~/.zephex. Without --api-key, the CLI opens zephex.dev, creates a CLI key for you, then writes the file — also one command, just with a browser step. ChatGPT is different: even with --api-key you still finish in ChatGPT with OAuth (no config file on disk).
npx -y zephex setup --crushnpx -y zephex setup --crush --projectnpx -y zephex setup --hermesnpx -y zephex setup --chatgptnpx -y zephex setup --kilonpx -y zephex setup --kilo --project| Scope | macOS | Linux | Windows |
|---|---|---|---|
| global | ~/.config/crush/crush.json | ~/.config/crush/crush.json | %APPDATA%\crush\crush.json |
| project | ./crush.json (repo root) | ./crush.json (repo root) | .\crush.json (repo root) |
| Scope | macOS | Linux | Windows |
|---|---|---|---|
| global | ~/.hermes/config.yaml | ~/.hermes/config.yaml | %USERPROFILE%\.hermes\config.yaml |
| Scope | macOS | Linux | Windows |
|---|---|---|---|
| global | ~/.config/kilo/kilo.jsonc | ~/.config/kilo/kilo.jsonc | %APPDATA%\kilo\kilo.jsonc |
| project | ./kilo.jsonc or ./.kilo/kilo.jsonc | ./kilo.jsonc or ./.kilo/kilo.jsonc | .\kilo.jsonc or .\.kilo\kilo.jsonc |
| global | ~/Library/Application Support/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json (legacy VS Code extension only) | ~/.config/Code/User/globalStorage/kilocode.kilo-code/settings/mcp_settings.json (legacy) | %APPDATA%\Code\User\globalStorage\kilocode.kilo-code\settings\mcp_settings.json (legacy) |
| project | ./.kilocode/mcp.json (legacy VS Code extension only) | ./.kilocode/mcp.json (legacy) | .\.kilocode\mcp.json (legacy) |
| Scope | macOS | Linux | Windows |
|---|---|---|---|
| global | No local file — chatgpt.com → Developer Mode → Create app | No local file — chatgpt.com → Developer Mode → Create app | No local file — chatgpt.com → Developer Mode → Create app |
From mcp-proxy/, run the verifier to print real file paths and JSON/YAML written on your machine (uses a temp HOME). On macOS/Linux the temp HOME uses ~/.config/…; on Windows the script sets APPDATA under that temp dir so paths match %APPDATA%\crush\crush.json and %APPDATA%\kilo\kilo.jsonc.
cd mcp-proxybun run scripts/verify-cli-setup-files.mjsLast verified on macOS (darwin arm64): Crush global ~/.config/crush/crush.json, Hermes ~/.hermes/config.yaml, Kilo ~/.config/kilo/kilo.jsonc with type: "local" and npx -y zephex@…. ChatGPT writes no file.
All editors cheat sheet · npx zephex · Connect MCP · MCP troubleshooting