zephex
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
←BackSign in
CLIGet StartedPricingMCP ToolsCommunityGuidesDocs
Get started freeSign in
DocsAPIToolsEditorsChangelogHelp

GET STARTED

WelcomeQuickstartSetup videoMCP Q&A (learn)BlogWhat is MCP?Plans & PricingZ-GASAB benchmarkBenchmark chart (live)Changelog

INSTALLATION

Terminal tools (complete)Connect MCPVS Code Marketplace extensionCLI (no AI agent)CLI init (first run)CLI account & logoutNPX (Recommended)Terminal CLI referenceCommand 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_packageloop_guardexplain_architectureZephex_dev_infoscope_taskaudit_headerskeep_thinking

GUIDES

Best PracticesToken EfficiencyUse CasesZephex vs Local MCPZephex vs Context7MCP 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.
DOCUMENTATION

Zephex MCP — One hosted endpoint for all your AI editors

Zephex is a cloud-hosted MCP proxy that gives your AI coding agents access to 10 powerful developer tools through a single API key. No local servers, no per-editor setup, no maintenance. Connect once, use everywhere.

Get your API keyQuickstart →
HOW IT WORKS

One endpoint. Ten tools. Zero local servers.

Your editor authenticates once with a Bearer token. The proxy routes each tool call to the right backend and returns a single response. Add or remove tools without ever touching your editor config.

Request Flow
HTTPS · JSON-RPC 2.0EditorMCP clientZephex Proxyauth · routeTool: read_codeTool: find_codeTool: 8 more…Bearer token

Your editor sends a single JSON-RPC call. The proxy authenticates, routes to the right tool, returns one response.

QUICK INSTALL

Get started in one command

Run this in your terminal. It walks you through API key creation and editor config automatically.

shell
npx zephex
USE CASES

npm package security audit with AI

Run live supply-chain checks from your editor — typosquats, CVEs, and migration risk without leaving the agent. Start with check_package for fast scans or loop_guard for deep intelligence across 12 ecosystems.

No-install hosted MCP server

Skip local Node MCP processes on every laptop. One Bearer token at https://zephex.dev/mcp — see Quickstart or Install.

Hosted vs local MCP

Compare configuration drift, team rollout, and when a remote endpoint wins in Zephex vs local MCP.

What counts as a request?

1 request = 1 MCP tool call. A typical coding session uses 20–80 requests. Limits and tiers are on Plans and Pricing.

Pricing at a glance

TierPriceRequests/mo
Free$0555
Pro$7/mo3,500
Max$19/mo10,000

Full pricing page · FAQ

START HERE

Quickstart

From zero to first tool call in under 5 minutes

→

Capabilities

All 10 tools: what they do and when to use them

→

Plans & Pricing

Free 555 req/mo, Pro 3,500, Max 10,000

→

Guides hub

Setup, comparisons, security tools, editor configs

→

Compare MCP

Hosted vs local, Zephex vs Context7

→
INSTALLATION

Choose your setup method

Every method uses the same endpoint and API key. Pick the one that matches your workflow.

NPX (Recommended)

One command, auto-configures your editor. Works with Cursor, Claude Code, VS Code, and more.

→

CLI

Full CLI with auth, key management, usage stats, and shell completions.

→

Terminal tools

find-code, get-context, architecture — run MCP tools in your shell (Mode 2).

→

HTTP API

Direct JSON-RPC over HTTPS. Use from any language or custom integration.

→
WHAT YOU CAN DO

What you can do with Zephex

Understand your project

Trace how a repo fits together — stack, scripts, dependencies, entry points — in one call.

Read & search code

AST-based symbol reading, ranked code search, and architecture analysis with diagrams.

Verify packages

Check any npm, pypi, or cargo package for typosquats, CVEs, and supply-chain risks.

Audit security

HTTP header audits, SSL checks, cookie flags, and CSP analysis on any deployed URL.

Reason through hard problems

Persistent thinking sessions that prevent circular debugging and track conclusions.

Look up expert knowledge

Database schemas, security patterns, frontend/backend best practices, deployment guides.

START HERE

Which tool should you call first?

Follow the decision flow. Never guess files. Every tool page has copyable prompt templates and real Before/After examples.

Which Tool Should You Call First?
New task or codebase?Never seen this repo?Get orientation fastget_project_context1 cheap call → stack + key filesComplex, risky, or long?Don't lose the threadkeep_thinkingPersistent investigation logYou have a clear task?Scope before you readscope_taskMinimal files + risk analysisThen narrow with one of these:find_codelocate anythingread_codeexact symbolexplain_architectureMermaid flowscheck_packagesafety firstaudit_headerslive URL auditEvery tool page has a "Recommended Prompt Template" + real Before/After examples.Copy them. Paste into Claude, Cursor, or Grok. Get dramatically better results.

Start here on any new task or unfamiliar codebase. Follow the arrows. Never guess files.

API KEYS

One key, all tools

Create API keys from the dashboard. Each key gives access to all 10 tools through the proxy. Use separate keys per environment (dev/staging/prod) so you can rotate without downtime.

Create API Key

Generate a new key from the dashboard right now

→

Key Management

Rotation, revocation, naming conventions, and security

→

Authentication

How Bearer auth works, token formats, and error codes

→
UNIVERSAL CONFIG

Works in every editor

This config structure works in Cursor, Claude Code, VS Code, Windsurf, and any editor supporting MCP. Paste it, add your key, restart.

json
{  "mcpServers": {    "zephex": {      "command": "npx",      "args": ["-y", "zephex"],      "env": {        "ZEPHEX_API_KEY": "YOUR_API_KEY"      }    }  }}
TOOLS

All 10 tools at a glance

Every tool is available on every plan. Click a tool to read its full reference.

ToolCategoryDescriptionAccess
get_project_contextProjectDetects framework, package manager, scripts, env vars
Read
scope_taskProjectPlain-English task → minimal focus file set
ReadCompute
read_codeCodeAST-based symbol/file/outline reading
Read
find_codeCodeBM25-ranked code search across the repo
Read
explain_architectureCodeEnd-to-end architecture analysis with Mermaid
ReadCompute
check_packagePackagesLive registry safety check (12 ecosystems)
Network
loop_guardPackagesDeep upgrade analysis: CVEs, breaking changes
Network
audit_headersExternalHTTP / TLS / cookie audit on any URL
Network
Zephex_dev_infoExternalExpert dev knowledge base lookup
Read
keep_thinkingReasoningPersistent structured reasoning sessions
Compute

See full details on the Capabilities page or any individual tool page.

EDITOR GUIDES

Pick your editor

Same endpoint, same auth. What changes is where the config file lives.

Claude Desktopclaude_desktop_config.json→ChatGPTDeveloper Mode app→Perplexity DesktopSettings → MCP→Crushcrush.json→Hermes~/.hermes/config.yaml→Kilo Codenpx setup --kilo · kilo.jsonc→Google Antigravitymcp_config.json→OpenCode~/.config/opencode/opencode.json→VS Code.vscode/mcp.json→Claude Code~/.claude.json→Cursor.cursor/mcp.json→Windsurfmcp_config.json→JetBrainsAI Assistant MCP→Kiro CLI~/.kiro/settings/mcp.json→Zed~/.config/zed/settings.json→Gemini CLI~/.gemini/settings.json→Clinecline_mcp_settings.json→Goose~/.config/goose/config.yaml→Codex CLI~/.codex/config.toml→Factory AI.factory/mcp.json→Copilot CLI~/.copilot/mcp-config.json→Kiro IDE.kiro/settings/mcp.json→WarpSettings → MCP Servers→Continue.continue/mcpServers/→Roo Code.roo/mcp.json→Trae.trae/mcp.json→
VERIFY

Test your connection

Run this curl to confirm your key works and the endpoint is reachable.

shell
curl -X POST https://zephex.dev/mcp \  -H "Authorization: Bearer YOUR_API_KEY" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
MORE

Best Practices

Tips for getting the most out of Zephex tools

→

Architecture

How the proxy routes requests to MCP backends

→

Troubleshooting

Common issues and how to fix them

→

Changelog

Latest product updates and releases

→

Usage & Limits

Rate limits, quotas, and how usage is tracked

→

Security

Encryption, data handling, and compliance

→