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 referenceWeb 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

SecurityData 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.

Support

Rolling Zephex out to your team

One hosted endpoint means every developer gets the same tools — without syncing local MCP configs across laptops.

WHY TEAMS CHOOSE HOSTED MCP

Every developer maintains a different local MCP stack. Onboarding means Slack threads and broken configs.

With Zephex: Share one quickstart snippet. Track usage per key in the dashboard. Rotate keys without changing the endpoint.

Compare hosted vs local MCP and vs filesystem MCP before your security review.

RECOMMENDED KEY STRATEGY
  • Per developer, per environment — e.g. cursor-dev-alice, ci-staging. Never share one key in Slack.
  • CI keys — read-only scopes where possible; rotate when people leave.
  • Naming — follow key naming conventions so usage analytics stay readable.
EDITOR STANDARD

Pick a default transport per editor class: stdio for Cursor/Claude Code, HTTP for VS Code. Publish internal snippets from supported editors so onboarding is copy-paste.

USAGE & LIMITS

Each key has a monthly request budget (1 request = 1 tool call). Monitor usage in the dashboard before engineers hit 429. See plans for tier limits.

SECURITY REVIEW

Share data handling and security docs with infra/legal. Code is processed ephemerally for tool calls — Zephex does not train on customer source.

PILOT CHECKLIST
  1. 3 engineers connect via quickstart
  2. Run check_package on a real dependency upgrade PR
  3. Run get_project_context on the main monorepo
  4. Review dashboard usage after one week
  5. Upgrade tier if the team consistently hits limits