How setup signs you in (one browser visit) Terminal npx zephex setup zephex.dev POST /api/cli/session Browser /cli/auth Dashboard GitHub / Google Poll GET /poll session_id open URL OAuth key ready Editor MCP file stdio or HTTP ~/.zephex credentials.json api_keys row user_id + HMAC writes writes creates Email shown once at setup — not stored in credentials.json (use dashboard for account) Stdio editors never re-auth per tool call — the API key is written once into config env. HTTP editors (Cursor) store Bearer in headers.
Setup is browser OAuth → API key → write editor config + ~/.zephex/credentials.json. You must fully restart the editor after setup. Account teardown: CLI account (logout vs disconnect vs reset).
Run this before editing JSON by hand. Catches stale npm, unpinned stdio, and project configs shadowing global setup.
npx -y zephex@latest setup --cursor # or --vscode, --opencode, --antigravity, … npx -y zephex@latest doctor npx -y zephex@latest list npx -y zephex@latest repair # Fully quit editor (Cmd+Q), reopen Hub: MCP troubleshooting · npx zephex
npx zephex doctorpasses but Cursor/VS Code/Antigravity shows 0 tools or "npx not found".
GUI apps do not load nvm, fnm, or Homebrew paths from your shell profile. Run npx -y zephex@latest repair — adds PATH hints to stdio env. Install Node via official pkg or brew so /usr/local/bin or /opt/homebrew/bin is on the system PATH. Fully quit the editor — window reload is not enough.
Zephex connects in repo A but not repo B.
Project-level files override global: .vscode/mcp.json, opencode.json, .mcp.json, .cursor/mcp.json. Global setup (default) removes project shadows — run npx -y zephex@latest setup without --project. Check npx -y zephex@latest list for every config path on disk.
Transport policy — stdio vs HTTP + repair STDIO (local file tools) HTTP (hosted tools only) VS Code, Zed npx -y zephex Antigravity repair migrates Continue, Hermes YAML + jsonc mcpcli repair pin + PATH Cursor Bearer + url Claude Code global HTTP Crush HTTP by design fixes not migrated npx zephex repair migrates HTTP → stdio for filesystem editors. Cursor, Claude Code (global HTTP), and Crush stay HTTP by design.
Non-JSON MCP configs — YAML, jsonc, or project-scoped paths.
Continue: ~/.continue/config.yaml or .continue/mcpServers/zephex.json — run npx -y zephex@latest setup --continue.Hermes: global ~/.hermes/config.yaml only — setup --hermes / disconnect --hermes.Kilo: kilo.jsonc with mcp parent key — setup --kilo then repair if shape is wrong.Run npx -y zephex@latest list to see every path on disk.
Setup finished but Antigravity never shows zephex connected.
Global path only: ~/.gemini/antigravity/mcp_config.json. CLI writes stdio — do not mix command and serverUrl in the same zephex entry. Fully quit Antigravity, reopen, start a new agent session. Verify via ⋯ → Manage MCP Servers → View raw config. Editor guide: Antigravity MCP setup
"zephex" does not appear in my editor after restart.
Confirm the config file is in the exact location for your editor. Validate the JSON is syntactically correct. No trailing commas and no // comments inside JSON files. Fully quit and reopen the editor. A window or tab reload is not sufficient for most editors. Check the editor's developer console or MCP log for error messages.
Every request returns {"error":"unauthorized"}.
Confirm the key is valid — generate a fresh key from Dashboard → API Keys if unsure. Confirm the header is exactly Authorization: Bearer YOUR_KEY. Check the key has not been deleted from the dashboard. Generate a new key and test again with the raw curl command from API Reference.
I see 0 tools in my editor.
Most editors require a full quit-and-reopen after adding MCP config. Once restarted, check the editor's MCP or tools panel. If you still see 0 tools, run the curl tools/list check from API Reference.
rate_limit_exceeded errors.
Check your current month's usage in the dashboard. If you have not used your full limit, contact support@zephex.dev . If you have used your limit, upgrade from the pricing page — Free (555 req/mo), Pro (3,500 req/mo), Max (10,000 req/mo).
Requests timeout or hang.
Zephex uses chunked HTTP streaming. Some corporate proxies strip chunked transfer encoding and cause hangs. Test with direct curl to separate a network issue from a config issue. If you are on a corporate network, ask IT whether Transfer-Encoding: chunked is allowed to zephex.dev.
We can help you get connected
Share your editor name, the error message (401, 429, empty tools/list), and your API key prefix — never the full key.