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

AGENTS.md Template

AGENTS.md is an open format file that tells AI coding agents how to work in your project before they plan any change.

It is read automatically by OpenAI Codex, GitHub Copilot, Cursor, Windsurf, and most other coding agents. Think of it as a project briefing that every agent reads before touching your code.

The Zephex template below tells your agents which endpoint to use, which tools exist, and the order to call them for the best results.

THE TEMPLATE
text
# Zephex MCP Configuration ## MCP Endpoint- URL: https://zephex.dev/mcp- Auth: Authorization: Bearer YOUR_API_KEY- Protocol: JSON-RPC 2.0 over Streamable HTTP- Tool count: 10 hosted tools ## Mandatory Tool OrderAlways follow this sequence for coding tasks:1. check_test — Identify the minimal files to read BEFORE reading anything2. get_project_context — Run once per session for project orientation3. read_code — Read specific functions/classes (not whole files)4. find_code — Search for patterns before writing new code5. keep_thinking — Track reasoning state for complex or high-risk tasks ## Available Tools Reference| Tool | Purpose | When to Call ||---|---|---|| check_test | Minimal file set for the task | FIRST, before any file reads || get_project_context | Project brief + full file tree | Once per session (covers structure) || read_code | AST symbol extraction + callers | Instead of reading full files || find_code | Repo-wide pattern search | Before implementing anything new || explain_architecture | Request/auth/data flow tracing | Before touching auth or DB code || check_package | npm package verification | Before adding dependencies || project_memory | Remember project decisions via local SQLite | During code review / new session || audit_headers | HTTP/TLS security audit | After every deploy || Zephex_dev_info | Expert KB (search → get) | Auth, DB, security patterns—not URL scraping || keep_thinking | Structured reasoning + session state | Complex debugging, high-risk changes | ## Rules- Never read a full file when read_code with a symbol name will do- Never implement something new before running find_code to check if it exists- Always call check_test at the start of non-trivial tasks- Call audit_headers after any deployment to production ## Project Context[Fill in your project-specific notes here: stack, key directories, naming conventions, deployment targets]
PLACEMENT RULES

Agents read AGENTS.md in this order, with the nearest file winning:

  1. The directory where you run the agent.
  2. Parent directories up to the repo root.
  3. Home directory ~/.agents.md for global defaults.

Put the template at ./AGENTS.md for a project-specific setup, or ~/.agents.md if you want Zephex instructions to apply across all projects on the machine.

WHICH FILES TO USE
FileWorks with
CLAUDE.mdClaude Code only
AGENTS.mdOpenAI Codex, GitHub Copilot, Cursor, Windsurf, JetBrains, and most others

For full coverage, create both files. They can contain identical content.

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