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

VS Code extension (Marketplace)

Install Zephex from the Visual Studio Marketplace to use ten codebase tools in VS Code agent mode: project context, code search, test health, package/CVE checks, and more. Sign in once; your API key stays in SecretStorage—not in mcp.json.

Install
shell
# Quick Open (Ctrl/Cmd+P):ext install zephex.zephex-mcp # 1. Command Palette → Zephex: Sign In# 2. Agent/chat → Configure tools → enable Zephex# 3. Ask: "What stack is this repo?"

Marketplace: zephex.zephex-mcp. Requires VS Code 1.101+. The same VSIX loads in Cursor and Windsurf when they support VS Code extensions.

VS Code also has an @mcp server gallery for config-only servers. Zephex is a Marketplace extension that registers an MCP provider—search Zephex in Extensions, not @mcp zephex.

Why this extension (stdio)

The extension starts npx -y zephex locally with your API key so tools can read files on disk. HTTP https://zephex.dev/mcp in mcp.json often makes VS Code hang on OAuth during initialize—disable duplicate HTTP entries and use only the extension's Zephex server in the MCP picker. See HTTP vs stdio.

Windsurf/Cursor configs may autodiscover a second zephex entry and crash spawn. Run npx zephex doctor to find conflicts.

Connect
  • Sign in — Zephex: Sign In (same session/poll API as Connect Zephex MCP).
  • API key — dashboard/keys → Zephex: Enter API Key (mcp_prod_* or mcp_sk_*).
  • Output — View → Output → Zephex for debug lines (keys are never logged).
Ten tools

Canonical slugs (do not use legacy names like scope_task or audit_package):

  • get_project_context — stack, folders, entry points
  • find_code / read_code — search and read symbols
  • explain_architecture — how subsystems connect
  • check_test — Test Pulse: run/detect tests and triage failures
  • check_package — package safety; task=upgrade|security for CVEs
  • project_memory — remember/recall across sessions
  • audit_headers — live URL security review
  • keep_thinking / Zephex_dev_info — reasoning and playbooks

Full reference: All 10 MCP tools · Connect MCP

CLI setup (without extension)

npx zephex setup --vscode writes user-scope stdio mcp.json (not project .vscode/mcp.json from ~). Setup merges with existing MCP servers.

shell
npx -y zephex setup --vscodenpx zephex doctor
CLI without an AI agent

Terminal Mode 2 uses the same account and tools—no chat UI. Useful for SSH, scripts, or direct commands.

shell
npx zephex doctornpx zephex status

CLI without an AI agent · Terminal CLI reference

Open VSX (optional)

Some Cursor/VSCodium paths use Open VSX in addition to Microsoft Marketplace. Zephex is published on Marketplace first; Open VSX publish is optional (Eclipse ECA + namespace token — see extension PUBLISH.md in the monorepo).

Related

  • VS Code manual MCP config
  • Cursor setup
  • Connect MCP (all editors)
  • CLI without an AI agent
  • All 10 MCP tools