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.

Configuration

CLAUDE.md Template for Zephex Users

CLAUDE.md is the file Claude Code reads at session start. If you reference Zephex tools there, Claude Code can use them proactively instead of waiting for manual prompting.

THE TEMPLATE

Create a file called CLAUDE.md in your project root and paste this:

text
# Project Instructions for Claude Code ## MCP Tools Available (via Zephex) You have access to Zephex MCP tools. Use them proactively: - **check_test**: Call this FIRST before any non-trivial coding task. It returns the minimal files to read and existing utilities to reuse.- **get_project_context**: Call once per session for orientation. Do not call it repeatedly.- **read_code**: Use instead of reading full files when you only need a specific function or class.- **find_code**: Use to locate patterns, env vars, or symbols before assuming they don't exist.- **explain_architecture**: Call when making changes to auth, database access, or billing flows.- **audit_headers**: Call after every deploy to check security header configuration.- **keep_thinking**: Call for complex multi-step debugging or high-risk changes to maintain session state. ## Tool Usage Rules 1. Always call check_test before starting a coding task - it saves context2. Use read_code instead of reading whole files - pass the function/class name3. Use find_code before implementing anything new - it may already exist4. Call get_project_context at session start, not mid-session ## Project-Specific Notes - Runtime and package manager: Document the exact runtime, package manager, and build tool used here.- Key paths: List the directories Claude should inspect first for product code, tests, and configs.- Validation commands: Add the exact test, lint, and build commands Claude should run before finishing work.- Constraints: Record naming rules, architecture boundaries, deployment constraints, and anything Claude must avoid changing.
CUSTOMIZING IT

The Project-Specific Notes section is where you add your own stack details, key directories, naming conventions, deployment targets, and other repo-specific guidance. The tool instructions above it are generic and work across projects.

WHERE TO PUT IT
  • Project-level: ./CLAUDE.md in the repo root. This applies only to Claude Code sessions in that project.
  • Global: ~/.claude/CLAUDE.md. This applies to every Claude Code session on the machine.

Use the global path if you want Zephex tool guidance everywhere. Use the project root if you want more tailored instructions per repository.

FOR ALL OTHER EDITORS: AGENTS.MD

AGENTS.md is the cross-tool standard that works with OpenAI Codex, GitHub Copilot, Cursor, Windsurf, and most other coding agents. It uses the same concept as CLAUDE.md but works universally.

Create AGENTS.md at your project root:

text
# Zephex MCP Tools Available ## EndpointURL: https://zephex.dev/mcpAuth: Bearer YOUR_API_KEYProtocol: JSON-RPC 2.0 over HTTPS ## Tool Usage Rules1. Call check_test FIRST before any coding task — it returns the minimal file set to read2. Call get_project_context once per session for orientation — not repeatedly3. Use read_code with a symbol name instead of reading full files4. Use find_code to search for patterns before assuming something doesn't exist5. Call keep_thinking for complex multi-step debugging to maintain session state ## Available Tools- check_test: Returns minimal files for a task (call this FIRST)- get_project_context: Project brief — stack, auth, hosting, key integrations, full file tree- read_code: AST-based symbol extraction with callers and imports- find_code: Fast repo-wide pattern search- explain_architecture: End-to-end request and auth flow tracing- check_package: Verify npm package exists, compare versions- project_memory: Remember and recall project decisions, gotchas, and conventions across sessions via local SQLite- audit_headers: HTTP/TLS security header audit- Zephex_dev_info: Expert knowledge base—search then get by slug (auth, RLS, Stripe, security)- keep_thinking: Structured reasoning with persistent session state ## Project Notes[Add your project-specific context here]

Place it at ./AGENTS.md in your project root for most editors, or ~/.agents.md for global defaults.

WHICH FILE SHOULD YOU USE?
FileWorks with
CLAUDE.mdClaude Code only
AGENTS.mdOpenAI Codex, GitHub Copilot, Cursor, Windsurf, JetBrains, and most others

For maximum coverage, create both files with the same content. Most codebases now have both.

EDITOR COMPATIBILITY
EditorReads AGENTS.mdReads CLAUDE.md
OpenAI Codex✓✗
GitHub Copilot✓✗
Cursor✓✗
Windsurf✓✗
JetBrains AI✓✗
Claude Code✗✓