Was this page helpful?
Installation
Zephex separates terminal credentials (~/.zephex/credentials.json) from editor MCP config files (~/.cursor/mcp.json, .vscode/mcp.json, etc.). Use the commands below directly in your shell — no AI agent required.
# Sign in (browser) + editor config + terminal credentialsnpx zephex setupnpx zephex setup --cursornpx zephex login --vscode # alias for setup # Check account & connectionnpx zephex statusnpx zephex doctornpx zephex usagenpx zephex keys # open dashboard keys page # Remove from editors (revokes key server-side)npx zephex disconnect --cursornpx zephex disconnect --all # Terminal sign-out only (editors unchanged)npx zephex logout # Fresh config after disconnectnpx zephex reconnect --claude-code # Disconnect + remove skill/rule files Zephex addednpx zephex reset --cursorInteractive help: npx zephex cli-guide account · npx zephex logout --help
setup writes both editor MCP config and terminal credentials. logout only removes ~/.zephex. disconnect revokes the key and strips editor config.
This is the most common confusion. They solve different problems. Implementation matches src/commands/logout.ts and src/commands/disconnect.ts — not interchangeable.
| Command | What it changes | Key on server | When to use |
|---|---|---|---|
logout | Deletes ~/.zephex/credentials.json (Windows: %USERPROFILE%\.zephex\credentials.json) | Still valid until you revoke it | Sign out of terminal tools only; keep Cursor/VS Code connected |
disconnect | Removes Zephex block from editor MCP JSON; revokes that key | Revoked | Stop MCP in an editor; rotate compromised key |
reconnect | Quiet disconnect + full setup again | New key after setup | 401 errors, expired key, fresh OAuth |
reset | disconnect + removes Zephex skill/rule files it added | Revoked | Clean uninstall from a machine |
# Example: keep Cursor MCP, stop terminal tools using your keynpx zephex logout# get-context will ask you to run setup again # Example: fully remove Zephex from Cursornpx zephex disconnect --cursor# Restart Cursor — Zephex tools gone| Command | Aliases | Purpose |
|---|---|---|
setup | login, sign-in | Browser OAuth → API key → editor MCP config + ~/.zephex |
logout | sign-out | Delete ~/.zephex only; editors unchanged |
disconnect | remove | Remove Zephex from editor JSON; revoke key server-side |
reconnect | — | disconnect --quiet + fresh setup |
reset | — | disconnect + remove skill/rule files |
status | — | Live MCP tools/list per installed editor config |
list | ls | Every supported editor — installed or not |
doctor | — | Node, network, MCP reachability, project index, API key |
keys | — | Masked keys + usage; links to dashboard |
usage | stats | Per-tool call counts this billing month |
tools | — | List / enable / disable MCP tools in editor config |
skills | — | Install or upgrade agent skill + rule markdown |
info | version, -v | Package version and install path |
help | -h, --help | Full reference; topics: terminal, tools, setup |
cli-guide | guide, howto | Mode 2 deep guide (topics: project, auth, monorepo, …) |
update | upgrade (no args) | How to npm install -g zephex@latest |
Run this in a terminal to prove setup, terminal tools, logout, and reconnect — no editor required for the middle steps.
Prove Mode 2 works from your shell before you connect Cursor or VS Code.
# Copy-paste test flow (no AI agent)npx zephex setupnpx zephex doctorcd your-app # folder with package.json + srcnpx zephex get-contextnpx zephex find-code "test"npx zephex safe lodashnpx zephex logoutnpx zephex setup # sign in again# Editor-only test (after setup --cursor)npx zephex status # should list 10 toolsnpx zephex disconnect --cursor# Restart Cursor → Zephex tools gonenpx zephex reconnect --cursor# Restart Cursor → tools backsetup and login are the same command. It:
npx zephex setupnpx zephex setup --cursor --projectnpx zephex setup --api-key mcp_prod_xxx # skip browser if you already have a keyMCP connection walkthrough: Connect Zephex MCP.
Terminal tools resolve the API key in this order:
ZEPHEX_API_KEY or MCP_API_KEY~/.zephex/credentials.json (written by setup)Manage keys in the dashboard: zephex.dev/dashboard/keys. Naming and formats: Key naming.
npx zephex doctor# Node version, network, MCP reachability npx zephex status# Tier, key prefix, connection state npx zephex list# Which editor config files reference Zephex npx zephex usage# Monthly request count vs plan limitUse the same editor flags as setup. --all removes every Zephex entry the CLI knows about on this machine.
npx zephex disconnect --cursornpx zephex disconnect --vscode --projectnpx zephex disconnect --allnpx zephex disconnect --quiet # used internally by reconnect600 on Unix; never commit API keys.logout does not revoke the key — use disconnect or revoke in the dashboard.npx zephex reconnect --cursor or create a new key and run setup with --api-key.Related: Authentication · API key management · Terminal CLI.