Cli Setup
One command: sign in on zephex.dev, then the CLI writes kilo.jsonc with a local MCP server (npx zephex + ZEPHEX_API_KEY). That matches Kilo’s official mcp + type: local shape. If you still use the old VS Code extension globalStorage file, setup keeps writing stdio there instead.
npx -y zephex setup --kilonpx -y zephex setup --kilo --api-key mcp_prod_your-key-herenpx -y zephex setup --kilo --project| 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) |
Parent key: mcp. Transport: type: "local" + command ["npx","-y","zephex@…"] + environment.ZEPHEX_API_KEY. Default kilo.jsonc. Legacy extension path uses mcpServers stdio.
{ "mcp": { "zephex": { "type": "local", "command": ["npx", "-y", "zephex"], "environment": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" }, "enabled": true, "timeout": 10000 } }}