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

Terminal tools — complete guide

Zephex Mode 2: run hosted MCP tools from your terminal without Cursor, Claude, or any AI agent. Same API key as editor MCP after npx zephex setup. Endpoint: https://zephex.dev/mcp

10

MCP tools

9

Terminal-capable

100+

CLI aliases

1

Setup command

QUICK REFERENCE

Primary command per tool. Expand each tool card below for full alias lists, flags, and copy-paste examples.

MCP toolAliasesStart hereWhen to use
get_project_context50+npx zephex get-contextFirst command in any repo
find_code31npx zephex find auth middlewareSearch, rename preview, usages
read_code31npx zephex outline src/cli.tsOutline large files, then symbol
explain_architecture9+npx zephex arch --focus authAfter get-context, before edits
check_test12npx zephex check-test "add rate limit"Test Pulse — health checks & diagnostics
check_package16+npx zephex safe lodashBefore npm install
project_memory3 slashesnpx zephex remember "…" · /memoryCross-session facts — recall before unfamiliar edits
keep_thinking3npx zephex think "debug 401" · /thinkOne-shot reasoning (editor: multi-turn sessionId)
Zephex_dev_info2npx zephex docs "Stripe webhooks" · /docsExpert KB lookup
audit_headers6+npx zephex check url https://… · /check-urlLive TLS + security headers on any URL

Live menus: npx zephex help terminal · npx zephex cli-guide

HOW A TERMINAL COMMAND RUNS
Terminal Mode 2 — How a Command Runs
YOUR MACHINETerminalbash · zsh · PSnpx zephexCLI 2.4+Local scaninline_files index~/.zephexAPI keyzephex.dev/mcphosted MCPcwdBearerhuman briefadd --json for the same payload your agent sees

No AI agent in the loop. Your shell runs npx zephex; the CLI uploads a search index from disk (inline_files) and calls the same hosted endpoint as your editor.

Verify local upload

You must see Using local project (N files from …) on project tools. If you see Using Git remote then errors, update to CLI 2.4+ or run from cd mcp-proxy && bun run build && npx ..

PROJECT TOOLS

get_project_context

Project brief — framework, database hints, scripts, monorepo detection, deploy signals.

When: First command in any repo. Before architecture or find-code.

50+ aliasesget-contextcontext.frameworkauth
Alias breakdown

Counts from cli.ts and cli-context-topic.ts

CategoryCountExamples
Core subcommands6get-context, get_context, context, .
Typo variants14getprojectcontext, project_context, …
Topic shortcuts34framework, database, auth, monorepo
Natural language20+"tell me about my project"
Copy-paste examples
shell
# Full project brief (stack, scripts, layout, deploy hints)npx zephex get-contextnpx zephex get_project_contextnpx zephex context # One section only — faster, less noisenpx zephex frameworknpx zephex databasenpx zephex authnpx zephex scripts # Plain English (no subcommand to memorize)npx zephex "tell me about my project"npx zephex "what database am I using" # Public repo without cloningnpx zephex get-context github:vercel/next.js # Cache + exportnpx zephex get-context --forcenpx zephex get-context -o PROJECT-BRIEF.mdnpx zephex get-context --json -o context.json
Flags
  • --topic framework — same as npx zephex framework
  • --json — raw MCP JSON for scripts
  • --force — ignore .mcp-context.json cache (24h TTL)
  • --cwd mcp-proxy — monorepo package root
  • -o file.md — write brief to disk

find_code

BM25-style code search over your uploaded project index. Grouped file paths and line numbers.

When: You know a string or symbol but not the file. Before a rename. To list all usages.

31 aliasesfindsearchrenameusagesdefs
All 31 subcommands
find-codefindsearchgreprgwhererenameusagesdefsdefinitionslocatepaste
Intent presets

Intent router rewrites your argv automatically

You typeBecomes
rename Xfind-code --exhaustive X (every file:line)
usages Symbolfind-code --scope usages Symbol
defs Symbolfind-code --scope definitions Symbol
paste code…Snippet search (≥8 chars)
Copy-paste examples
shell
# Searchnpx zephex find auth middlewarenpx zephex find encrypt --also cipher,E2E # Rename preview & usagesnpx zephex rename OldProductNamenpx zephex defs validateTokennpx zephex usages handleAuth # Snippet pastenpx zephex paste 'export async function handleAuth(' # CI / scriptsnpx zephex rename Crystal --json | jq '.data.files_summary[].file'

read_code

AST-based reading — file outline, symbol body, or batch files. Terminal shows summaries; use --json for full payload.

When: Large files (>300 lines): outline first, then symbol. After find-code gives you a path.

31 aliasesoutlinesymbolsummarizeexplainfiles
summary vs summarize

Easy to mix up — check this before running commands

CommandActual tool
npx zephex summaryget_project_context — topic quick
npx zephex summary src/foo.tsread_code — outline + summarize
npx zephex explainexplain_architecture
npx zephex explain src/foo.tsread_code file summary
Copy-paste examples
shell
# File summary (outline + plain-language overview)npx zephex summarize src/app/page.tsxnpx zephex explain src/lib/stripe.ts # Table of contents only (large files)npx zephex outline src/cli.ts # One function or class bodynpx zephex symbol handleAuth # Batch readnpx zephex files src/a.ts src/b.ts # summary alone = project brief; summary + path = file outlinenpx zephex summary              # → get-context --topic quicknpx zephex summary src/foo.ts   # → read_code outline

explain_architecture

System map — entry points, layers, auth/billing flows, external services, hotspots.

When: After get-context when you need “how does X work in this codebase?” Use --focus to narrow.

9+ aliasesarchitecturearchhow-it-works"how does auth work"
Natural language routing
  • npx zephex "how does auth work" → architecture --focus auth
  • npx zephex "how does payment flow work" → billing focus
  • Keyword routing in cli-intent-router.ts — no LLM in the CLI
Copy-paste examples
shell
# System mapnpx zephex architecturenpx zephex archnpx zephex how-it-works # Focus one areanpx zephex arch --focus authnpx zephex architecture --focus billing # Plain Englishnpx zephex "how does auth work" # explain alone = architecture; explain + file = read_codenpx zephex explain src/foo.ts

check_test

Test Pulse — run tests, return structured health: broken areas, fix_first, coverage, triage.

When: After code changes. Chain: find-code → check-test → read-code on focus files.

12 aliasescheck-testscope-taskscopeplanfiles-for
Copy-paste examples
shell
npx zephex check-test "add Stripe webhooks"npx zephex scope "fix auth bug" --max-files 5npx zephex plan "migrate to app router"npx zephex check-test --area auth
PACKAGE & KNOWLEDGE TOOLS

check_package

Registry safety, CVEs, upgrade paths — works without a project folder. Paste a package name or npm install line.

When: Before npm install. In a repo, CLI reads package.json and lockfile for installed version.

16+ aliasessafecheck-packageexpresslast
Copy-paste examples
shell
# Safety (before npm install)npx zephex expressnpx zephex safe lodashnpx zephex is react safe to install # Upgrade & CVEs (CLI loop-guard → check-package --task upgrade)npx zephex check-package next --task upgrade --from-version 14.2.0npx zephex loop-guard next --from-version 14.2.0 # In your repo (auto version from lockfile)cd my-app && npx zephex expressnpx zephex last
Flags & CI
text
--task check|upgrade|security|migrate|debug--from-version <ver>   Version you are on (upgrade/CVE scope)--ecosystem pypi|cargo|gem|go|maven|…   (12 registries)--verbose, -v          Downloads, timing, deprecation detail--json                 Full CLI report (CI / jq)--strict               Exit 1 on high risk or unpublished
project_memory vs loop-guard CLI

Terminal loop-guard is a legacy alias for check-package --task upgrade. The MCP tool project_memory is different — save/search project facts via npx zephex remember, recall, memory list. Prefer check-package --task upgrade for upgrades. Docs: project memory, check_package.

keep_thinking · Zephex_dev_info · audit_headers · project_memory

Reasoning, expert KB, live URL audit, and cross-session project memory — all available in the terminal.

When: think/docs for one-shot; check url for live headers; remember/recall for facts across sessions.

12+ aliasesthinkdocscheck urlrememberrecall
Commands
  • keep_thinking: npx zephex think "debug 401" — one-shot; multi-turn sessions are editor-only
  • Zephex_dev_info: npx zephex docs "Stripe webhooks"
  • audit_headers: npx zephex check url https://example.com · aliases: site-audit, audit-headers
  • project_memory: npx zephex remember "…" · recall auth · memory list
FULL WORKFLOW — COPY THIS
shell
# Day 1 — new codebase (no AI agent)cd ~/projects/acme-apinpx zephex setupnpx zephex get-contextnpx zephex architecture --focus authnpx zephex find-code "middleware"npx zephex outline src/server/routes.tsnpx zephex check-test "add rate limiting to login" # Before npm installnpx zephex safe some-new-packagenpx zephex check-package next --task upgrade --from-version 14.2.0
FLAGS (ALL PROJECT TOOLS)
FlagEffect
--jsonRaw MCP response (CI, jq, agent parity)
--cwd <dir>Monorepo package root
--no-localUse git remote instead of folder upload
--path github:o/rExplicit public repo
--api-keyOverride ~/.zephex / ZEPHEX_API_KEY
-q, --quietLess stderr / footer
--forceget-context cache refresh only
SETUP & ACCOUNT
shell
npx zephex setupnpx zephex doctornpx zephex logout          # terminal onlynpx zephex disconnect --cursor

Endpoint: https://zephex.dev/mcp · Keys: zephex.dev/dashboard/keys

RELATED PAGES
  • CLI without an AI agent
  • Connect MCP
  • get_project_context · find_code · read_code
  • Tool Workflows · Tools Overview