zephex
⌘K
Get StartedPricingMCP ToolsDocs
←Back×Sign in
Get StartedPricingMCP ToolsDocs

Documentation

Start with the endpoint and API key flow, then branch into editor setup or tool reference.

GET STARTED

What is MCP?IntroductionQuickstartAPI ReferenceUniversal RequirementsZephex vs Local MCPBest PracticesToken EfficiencyCLAUDE.md TemplateAGENTS.md TemplateMCP EcosystemMarkdown Access

EDITORS

OpenCodeOAuthVS CodeClaude CodeCursorWindsurfJetBrainsKiro CLIOAuthZedOAuthGemini CLIOAuthClineOAuthGooseCodex CLIOAuthFactory AIOAuth

OPERATING SYSTEMS

macOSWindowsLinux

TOOLS

get_project_contextread_codefind_codecheck_packageaudit_packageexplain_architectureZephex_dev_infoscope_taskaudit_headersthinking

SUPPORT

PlansPro & Max GuideUsage & AnalyticsConnection IssuesRate LimitsBillingSecurityFAQChangelog

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
raw-file-reads.txt
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
ToolTypical outputWhat it replacesSavings
get_project_context400–700 tokens15,000–40,000 tokens of file reads97%
scope_task300–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%
thinking200–500 tokens/callReasoning loops and repeated readsContext stability
REAL SESSION COMPARISON
without-zephex.txt
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
with-zephex.txt
get_project_context → orientation                  →     520 tokensscope_task → "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 scope_task.
  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 thinking when reasoning gets complex.