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

GET STARTED

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

INSTALLATION

Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Terminal CLI referenceCommand CompassCLI commandsCLI in DockerCLI: All editors (one command)CLI: Crush, Hermes, ChatGPT, KiloOAuth & HTTP setupInstall overviewHTTP APISetup WalkthroughHTTP vs stdio

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_packageloop_guardexplain_architectureZephex_dev_infoscope_taskaudit_headerskeep_thinking

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7MCP EcosystemMarkdown Access

SUPPORT

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

LEGAL

SecurityData 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.

Installation

CLI init — first-run onboarding

Run mcpcli init (or zephex init) on day one. The wizard checks Node and network, opens browser sign-in at zephex.dev/cli/auth — the same dashboard login page as setup, not documentation. Credentials land in ~/.zephex/credentials.json for terminal tools. Same binary works as mcpcli, zephex, zphx, zepx after npm install -g zephex.

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

Short commands: after npm install -g zephex, use mcpcli setup (same as npx zephex setup). Requires Node.js 18+ — no Node? see options. Same CLI: mcpcli, zepx, zphx, mcpz, zepcli, zephx, or zephex (after npm i -g zephex).

INIT COMMANDS
shell
# Install (if needed)npm install -g zephex && mcpcli setup # First run — browser opens zephex.dev login (NOT docs)mcpcli 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.js 20+ 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)

After npm install -g zephex, every bin runs the same CLI: mcpcli · zephex · zepx · zphx · mcpz · zepcli · zephx

shell
cd your-appmcpcli get-contextmcpcli find-code "auth"mcpcli read-code --mode outline src/index.tsmcpcli ask "what stack is this" --path github:docker/mcp-registrymcpcli architecturemcpcli deps

Help: mcpcli help terminal · mcpcli ask --help

UPGRADE AFTER INIT
shell
# Check installed vs npm latestmcpcli updatemcpcli update --check # Apply upgrade (global install)mcpcli update --apply # Refresh agent skill files after upgrademcpcli skills --upgrade # Verifymcpcli infomcpcli doctor
RELATED DOCS
  • CLI account — logout, disconnect, reconnect
  • Terminal tools without an AI agent
  • Full CLI command reference
  • Install methods (npm, npx, bun)