zephex
Zephex é um gateway MCP hospedado criado para editores de código com IA. Ele oferece ao seu agente 10 ferramentas prontas para uso — verifique pacotes npm em busca de vulnerabilidades, audite cabeçalhos de segurança, leia e pesquise código, rastreie fluxos de requisições, obtenha contexto de projeto de qualquer repositório e muito mais. Uma chave de API, funciona instantaneamente com Claude Code, Cursor, VS Code, Windsurf e outros. Gratuito para começar em zephex.dev.
Documentação
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.
AI AgentTerminal — no AI needed
curlnpxpnpmbun
>curl -fsSL https://zephex.dev/install.sh | bash
Terminal CLI — Mac, Windows (WSL), Linux. Bundles Node when needed.
get started free
Terminal
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
Full CLI demo
Works everywhere
One config. Every editor.
One endpoint for every code editor. Same tools, same config — 27 editors supported.
FAQ
Questions beforeyou connect
Quick answers for evaluation, setup, and security review.
01How long does setup take?
Most users connect in a few minutes — create a key, paste one config snippet into your editor, and call the MCP endpoint. No long onboarding, no infrastructure to provision.
02Which clients are supported?
Zephex provides setup guidance for Cursor, Claude Code, VS Code, Windsurf, and JetBrains, and any other MCP-compatible client. If it speaks MCP, it works.
03Do you train AI models on my tool content?
No. Zephex does not use your prompts, tool inputs, tool outputs, or code to train AI models. Your data is routed and enforced at the boundary — nothing is retained for model training.
04How is Zephex different from running an MCP server locally?
A local MCP server is tied to one machine and one editor. You re-install it for every new project, every team member, and every environment. Zephex is hosted — one endpoint that works across all your editors, machines, and teammates from the moment you paste the config.
05How is Zephex different from Context7 or documentation MCP?
Context7 injects fresh third-party library docs into prompts. Zephex reads your actual repo and installed packages — code search, project context, and package audits. Many teams use both: docs MCP for framework APIs, Zephex for shipping in your codebase.
06Is Zephex a memory MCP that saves contacts or chat history?
No. Memory MCPs like Mem0 remember facts across sessions. Zephex is for live engineering: your file tree, dependencies, architecture, and supply-chain checks while you code — not contact saving or long-term chat recall.
07Can Zephex catch a bad npm package before install?
Yes. The check_package tool queries live registry data for typosquats, maintainer signals, and risk flags — the same workflow that flagged a convincing fake Stripe SDK. Use task=upgrade for version-to-version breaking changes and CVE detail.
08How many free MCP requests do I get?
555 requests per month on the free tier (one tool call = one request). See Pricing for Pro and Max limits.
30+ more answers · Who it's for · Compare MCP setups
Ready to route your_first endpoint?_
Create API keyRead the docs