Zephex is a hosted MCP gateway with ten codebase tools, plus a terminal CLI and browser web terminal on the same API key — so AI coding agents (and humans) work from real project context instead of guessing.
MCP SERVER · 10 DEV TOOLS · 20+ AI EDITORS
Stop your AI agent from guessing.
Zephex plugs real project context, code search, and dependency-safety checks into any AI editor through one connection. Or skip the agent entirely — the same tools work directly in your terminal.
Best if you do not have Node. ~3 MB CLI tarball; private Node 22 (~50 MB) only if missing. Mac, Linux, WSL. Windows: irm https://zephex.dev/install.ps1 | iex. Full CLI install, upgrade, Windows, Linux
Mode 2 · bash
❯ npx zephex get-context
◇ Scanning manifests…
get_project_context › acme-api
At a glance
TypeScript · Express · Supabase · Stripe
❯ npx zephex setup
✓ Ready — try get-context
❯npx zephex find-code "verifyToken"
src/middleware/auth.ts:12
Works everywhere
One config. Every editor.
One endpoint for every code editor. Same tools, same config — 20+ editors supported.
FAQ
Questions beforeyou connect
Quick answers for evaluation, setup, and security review.
A few minutes. Create a free key, run npx zephex setup (or paste the MCP config), and call tools from Cursor, Claude Code, Codex, OpenCode, VS Code, or the CLI. No servers to host.
Hosted MCP works with Cursor, Claude Code, Codex, OpenCode, VS Code, Windsurf, Zed, JetBrains, and other MCP clients — plus the terminal CLI and web terminal without any AI editor open.
The zephex terminal CLI installs via curl install.sh or npx zephex. From your project directory you run overview, deep --json, find, read, architecture, safe / check-package, check test, remember/recall, and more. Same backend tools as MCP; human-readable output or --json for agents and scripts.
A dashboard browser terminal at /dashboard/terminal that runs allowlisted Mode 2 commands over SSE — paste a public GitHub repo and run overview, find, deep, package checks without local install. Not a full shell. Shares your plan quota. Private repos: use local CLI or editor MCP.
No. Zephex does not use your prompts, tool inputs, tool outputs, or code to train AI models. Security and data-use pages spell out boundaries.
A local MCP server is tied to one machine and one editor. You re-install it for every project, teammate, and laptop. Zephex is hosted — one endpoint, one key, same tools in every editor plus CLI and web terminal.
Context7 injects fresh third-party library docs. Zephex reads your actual repo and packages — project context, code search, architecture, tests, supply-chain checks. Recommended stack: Context7 + GitHub MCP + Zephex. See /compare/recommended-mcp-stack.
No. Mem0-style products store chat memory. Zephex is live engineering context (files, deps, architecture, package risk). project_memory stores project decisions and gotchas you choose to remember — not contacts or long chat logs.
Yes. check_package (CLI: zephex safe / check-package) hits live registry data for typosquats, maintainer signals, CVEs, and upgrade breakage — including the workflow that flagged a convincing fake Stripe SDK.
555 requests per month on Free (1 tool call ≈ 1 request), across MCP, CLI hosted tools, and web terminal. Pro is 3,500 at $7/mo; Max is 10,000 at $19/mo. See Pricing and /docs/plans.