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 referenceWeb 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

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.

Guides

Token Efficiency

Every AI coding session has a token budget. Zephex tools are designed to minimize token use while maximizing signal.

A typical model context window is 100,000 to 200,000 tokens. Every file read, tool result, and copied snippet burns that budget. For coding sessions, token budget is working memory.

THE PROBLEM WITH STANDARD TOOL APPROACHES
text
Agent reads package.json              →  2,100 tokensAgent reads README.md                 →  4,500 tokensAgent reads src/index.ts              →  8,200 tokensAgent reads app/api/route.ts          →  6,100 tokensAgent reads lib/auth.ts               →  3,800 tokensAgent reads middleware.ts             →  2,400 tokens─────────────────────────────────────────────────────Total consumed for project orientation: 27,100 tokensActual useful signal extracted:          ~600 tokens

In that example, the agent spent 27,100 tokens to extract about the same information get_project_context returns in roughly 450 to 700 tokens.

ZEPHEX TOOL OUTPUT SIZES <TokenSavingsComparisonFlow />
ToolTypical outputWhat it replacesSavings
get_project_context400–700 tokens15,000–40,000 tokens of file reads97%
check_test300–600 tokens3–8 unnecessary file reads70–90%
read_code200–800 tokensFull file read (2,000–10,000 tokens)85–95%
find_code100–400 tokensManual grep or multiple file reads90%
explain_architecture800–1,500 tokensReading 5–10 related files85%
keep_thinking200–500 tokens/callReasoning loops and repeated readsContext stability
REAL SESSION COMPARISON
text
Start session: read 6 files for orientation        →  27,100 tokensFind the right function: read 3 more files         →  18,400 tokensUnderstand auth flow: read middleware + 2 helpers  →  11,200 tokens──────────────────────────────────────────────────Before writing a single line of code:              56,700 tokens consumed
text
get_project_context → orientation                  →     520 tokenscheck_test → "add rate limiting to /api/webhooks"  →     380 tokensread_code → find the existing rateLimiter.ts       →     290 tokens──────────────────────────────────────────────────Before writing a single line of code:               1,190 tokens consumed
The same task. 47x fewer tokens consumed before writing code.
TIPS FOR TOKEN-EFFICIENT SESSIONS
  1. Always start with check_test.
  2. Use read_code with a symbol name, not a whole file.
  3. Call get_project_context once per session.
  4. Use find_code before read_code.
  5. Use keep_thinking when reasoning gets complex.