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

INSTALLATION

Web Terminal tools (plain English)Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Test Pulse (check test)Test Pulse commandsProject MemorySupply Pulse (supply)Supply Pulse commandsTerminal CLI referenceSlash commands (37 palette)Web Terminal (dashboard)Command 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_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.

Installation

Zephex CLI in Docker

Run the full Zephex CLI inside a container when you cannot install Node.js on the host, or you want an isolated environment. Mount your home directory so setup can write editor MCP configs and ~/.zephex/credentials.json on your real machine.

CLI — DOCKER COMMANDS
shell
# No Node.js on the host — use official Node image + npxdocker pull node:22-alpine # Interactive setup (writes ~/.cursor, ~/.claude.json, ~/.zephex on your machine)docker run -it --rm \  -v "$HOME:/root" \  -w /root \  node:22-alpine \  npx -y zephex setup # Terminal tools after setup (same volume mount)docker run -it --rm \  -v "$HOME:/root" \  -w "$(pwd):/work" \  -w /work \  node:22-alpine \  npx -y zephex get-context docker run -it --rm \  -v "$HOME:/root" \  -w /root \  node:22-alpine \  npx -y zephex doctor

Why mount $HOME? Setup writes paths like ~/.cursor/mcp.json and ~/.zephex/credentials.json. Without the volume, configs stay inside the ephemeral container and disappear when it exits.

RUN TOOLS IN YOUR REPO

Terminal tools upload your current directory as inline_files by default. Mount the project path as the working directory:

shell
cd /path/to/your-app docker run -it --rm \  -v "$HOME:/root" \  -v "$(pwd):/work" \  -w /work \  node:22-alpine \  npx -y zephex get-context docker run -it --rm \  -v "$HOME:/root" \  -v "$(pwd):/work" \  -w /work \  node:22-alpine \  npx -y zephex find-code "auth middleware"

Public OSS without a local clone: npx zephex get-context github:owner/repo (network from container must reach GitHub and zephex.dev).

SHELL ALIAS

Avoid typing the long docker run line every time:

shell
# ~/.bashrc or ~/.zshrc — use zephex like a local binaryalias zephex='docker run -it --rm -v "$HOME:/root" -w /root node:22-alpine npx -y zephex' zephex setup --cursorzephex logoutzephex find-code "middleware"

For project-scoped commands, extend the alias with -v "$(pwd):/work" -w /work or wrap in a small shell function.

PRE-BUILT IMAGE

Install zephex globally in the image so startup is faster than npx every run:

text
FROM node:22-alpineRUN npm install -g zephexENTRYPOINT ["zephex"]
shell
docker build -t zephex-cli .docker run -it --rm -v "$HOME:/root" -w /root zephex-cli setupdocker run -it --rm -v "$HOME:/root" -w /root zephex-cli listdocker run -it --rm -v "$HOME:/root" -w /root zephex-cli logout
WINDOWS NOTES
  • Use Docker Desktop with WSL2 backend; prefer paths inside the WSL filesystem for volume mounts.
  • Credentials path inside Linux container: /root/.zephex/credentials.json maps to your mounted home.
  • Native Windows terminal (outside WSL): run npx zephex with Node for fewer mount issues, or use WSL for Docker workflows.

Platform guide: Windows.

LIMITATIONS
  • Container boot adds latency vs native npx.
  • Editors on the host still need restart after setup — Docker only writes config files.
  • stdio MCP in editors still spawns npx -y zephex on the host unless you configure HTTP-only.

Other install paths: Install methods · npx zephex · Connect MCP.