zephex
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
←BackSign in
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
Get started freeSign in
DocsAPIToolsEditorsChangelogHelp

GET STARTED

WelcomeQuickstartSetup videoMCP Q&A (learn)BlogWhat is MCP?Who is Zephex for?Plans & PricingZ-GASAB benchmarkBenchmark chart (live)Changelog

CLI

Install & upgradeStartAll install methodsnpx zephex setupCLI without an agentFirst run (init)Login, logout, keysCommand referenceTerminal Mode 2Slash commandsCLI in Docker

INSTALLATION

Connect MCPAll editors (one command)Crush, Hermes, ChatGPT, KiloVS Code Marketplace extensionOAuth & HTTP setupSetup walkthroughHTTP vs stdioWeb Terminal (dashboard)Web Terminal toolsTerminal tools (complete)Test PulseTest Pulse commandsdeep (Project Dossier)Project MemorySupply PulseSupply Pulse commandsinstall (GitHub / npm files)install file commandsCommand CompassHTTP API

API & KEYS

API Key ManagementKey Naming & FormatAuthenticationKey Dashboard

CONFIGURATION

Universal RequirementsSupported EditorsHow It WorksArchitectureCLAUDE.md TemplateAGENTS.md Template

EDITORS28 guides

Supported EditorsVS CodeVS Code extension (Marketplace)Claude CodeCursorWindsurfJetBrains

PLATFORM

macOSWindowsLinux

TOOLS10 tools

Capabilities OverviewTools OverviewTool FilteringTool Workflowsget_project_contextread_codefind_codecheck_packageexplain_architectureZephex_dev_infocheck_testaudit_headerskeep_thinkingproject_memory

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7Zephex vs GitHub MCPZephex vs SmitheryMCP EcosystemMarkdown Access

SUPPORT

Help CenterMCP troubleshootingTeam rolloutFAQConnection IssuesRate LimitsDowntime & ErrorsBillingTier GuidePro & Max guideUsage LimitsUsage Analytics

LEGAL

System StatusTerms (summary)Privacy (summary)Data UseSecurityAuthenticationSecurityData HandlingPrivacy PolicyTerms of Service

Quick Links

API Reference

Complete API documentation

Troubleshooting

Common issues and solutions

Community

Join our Discord community

Plugins

Editor and CLI integrations

Pricing

Free, Pro, and Max plans

Enter
Zephex_devzephex-devzephexzephexhello@zephex.dev
© 2026 Zephex. All systems operational.

CLI

CLI init — first-run onboarding

New laptop: curl -fsSL https://zephex.dev/cli/install.sh | bash then zephex init --terminal. The wizard opens zephex.dev/cli/auth (dashboard login, not docs). Credentials land in ~/.zephex/credentials.json. Same binary: zephex, mcpcli, zphx.

Login URL: https://zephex.dev/cli/auth (user login). Docs are reference only — init never sends you to a docs page to authenticate.

INSTALL MCPCLI / ZEPHEX

No Node? curl -fsSL https://zephex.dev/cli/install.sh | bash. Already have Node 22.5+? npx -y zephex@latest (terminal) or npx -y zephex@latest setup --cursor (editor). Install & upgrade. Same CLI: mcpcli, zepx, zphx, mcpz, zepcli, zephx, or zephex (after npm i -g zephex).

USUAL SETUP FAILURES

These are the bugs people actually hit when installing or when an agent runs setup. Full install/upgrade page: Install & upgrade the CLI.

What you seeWhyFix
command not found: zephexcurl | bash cannot change PATH in the parent shell.source ~/.zephex/env.sh then open a new tab. which zephex should be ~/.zephex/bin/zephex.
npx zephex setup hangs or is huge (~260 MB)Published npm zephex still lists unused server deps. npx installs them.Use curl -fsSL https://zephex.dev/cli/install.sh | bash (~3 MB). Then zephex connect --cursor if you want the editor.
Node 18 / 20 — engines errornpx/npm/bun need Node 22.5+. Cloud Shell and many laptops are still 20.Do not upgrade Node just for us. Run the curl installer — it bundles Node 22 under ~/.zephex/node.
Agent says 0 tools / old tool namesStale npx cache or Grok/editor cached descriptors (23 files vs 10 live tools).npx -y zephex@latest doctor then repair. Grok: rm cached zephex tool JSON, grok mcp doctor zephex.
Login opened but CLI still “not signed in”QR/browser completed, poll did not write credentials, or you ran a different binary than the one that started login.zephex login or mcpcli login on the same machine. Check ~/.zephex/credentials.json exists (do not paste the key into chat).
Editor works, terminal does not (or the reverse)Editor MCP config and ~/.zephex/credentials.json are separate.Terminal: zephex login or mcpcli login. Editor: npx -y zephex@latest setup --cursor (or --claude). Same account.
HTTP MCP but find/read cannot see local filesHosted HTTPS cannot read the laptop disk. Cursor HTTP is fine for some tools; file tools need stdio.zephex repair — switches filesystem editors to stdio (npx -y zephex).
Windows: bash installer failedcmd.exe cannot run the Mac/Linux script.PowerShell: irm https://zephex.dev/install.ps1 | iex. WSL: use the curl line inside WSL, not on the host.
Mixed C:\Users\… and /home/you/.zephexWindows host and WSL are two installs.Install once in the environment that actually runs the shell or the editor.
doctor: CLI install is ~260 MBOld npm install -g left unused packages under ~/.zephex/npm-global.Re-run the curl installer. Credentials stay. voice-venv is unrelated (optional STT).
INIT COMMANDS
shell
# Install (no Node required)curl -fsSL https://zephex.dev/cli/install.sh | bashsource ~/.zephex/env.sh # Or if Node 22.5+ is already installednpm install -g zephex && mcpcli setup # First run — browser opens zephex.dev login (NOT docs)zephex init --terminalmcpcli init # Terminal only (no editor MCP config)mcpcli init --terminal # Skip picker — connect Cursor after loginmcpcli init --cursor # Non-interactive (CI / scripts) — terminal sign-in onlymcpcli init -y # After init — try inside your project foldermcpcli get-contextmcpcli find-code "auth"mcpcli learn # Account lifecycle (all 22+ editors — same flags)mcpcli connect --cursormcpcli connect --claude-codemcpcli disconnect --vscodemcpcli reconnect --zedmcpcli logoutmcpcli logout --allmcpcli updatemcpcli update --applymcpcli doctor
WHAT INIT DOES
  1. Checks Node (22.5+ for npx; curl installer bundles Node if missing) and reachability of zephex.dev.
  2. Asks: terminal CLI only, editor MCP, or both.
  3. Opens browser OAuth at zephex.dev (GitHub / Google / email — same as dashboard).
  4. Saves API key to ~/.zephex for mcpcli get-context, find-code, etc.
  5. Optionally runs editor setup (writes .cursor/mcp.json, etc.).
  6. Prints next-step commands (learn, get-context, logout, disconnect).
INIT VS SETUP VS LOGIN
CommandBest forBrowser opens
mcpcli initBrand-new users — guided first runzephex.dev/cli/auth
mcpcli setupPick editor, scope, skill modezephex.dev/cli/auth
mcpcli loginAlias for setupzephex.dev/cli/auth
PACKAGE NAMES (SAME CLI)

Install once: npm install -g zephex. Then any bin name works:

npm packageCommand names
zephex (canonical)zephex, mcpcli, zepx, zphx, mcpz, zepcli, zephx
@tanstratum/mcpclimcpcli, zephex
@tanstratum/zphxzphx, mcpcli, zephex
shell
mcpcli initzephex initzphx init --terminalnpx -p zephex mcpcli init
TERMINAL TOOLS (NO NPX)

zephex and mcpcli are the same program. Type whichever you remember: zephex overview and mcpcli overview do the same thing. Also: zepx · zphx · mcpz · zepcli · zephx.

shell
cd your-appzephex get-contextmcpcli get-contextzephex find-code "auth"mcpcli find-code "auth"zephex overviewmcpcli overviewzephex doctormcpcli doctor

Help: mcpcli help terminal · mcpcli ask --help

UPGRADE AFTER INIT
shell
# Check installed vs npm latestzephex update --checkmcpcli update --check # Apply (CLI tarball into ~/.zephex — not npm install -g)zephex update --applymcpcli update --apply # Same effect — safe to re-run; keeps credentialscurl -fsSL https://zephex.dev/cli/install.sh | bashsource ~/.zephex/env.sh # Windows# irm https://zephex.dev/install.ps1 | iex # Refresh agent skill files after upgradezephex skills --upgrademcpcli skills --upgrade # Verifyzephex infomcpcli infozephex doctormcpcli doctor
RELATED DOCS
  • CLI account — logout, disconnect, reconnect
  • Terminal tools without an AI agent
  • Full CLI command reference
  • Install methods (npm, npx, bun)