Cli Setup
One command: sign in on zephex.dev in the browser, then the CLI merges a zephex block into crush.json. This is a normal MCP config file on disk — not a separate “remote-only” install path.
# Easiest if you don't have a key yet (browser sign-in, then writes crush.json):npx -y zephex setup --crush # Already have a key from zephex.dev/dashboard/keys (must start with mcp_):npx -y zephex setup --crush --api-key mcp_prod_your-key-here # Project-scoped (writes ./crush.json in cwd):npx -y zephex setup --crush --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) |
Parent key: mcp. Transport: type: "http" + url + headers.Authorization Bearer. Charm crush.json schema — not mcpServers.
{ "$schema": "https://charm.land/crush.json", "mcp": { "zephex": { "type": "http", "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" } } }}