Zephex — Hosted MCP Gateway for Cursor, Claude Code & VS Code

Sign in

Your AI editor keeps forgetting your project. Zephex fixes that.<br>Hosted MCP server — unified endpoint for Cursor, Claude Code, VS Code, Windsurf, and JetBrains. Get project context, code search, and package intelligence in every session. Free to start.

Get free API key ↓

How it works<br>Stop re-explaining your codebase.<br>Connect once.<br>Instead of wiring each editor separately, you point everything at zephex.dev/mcp once — and Zephex handles validation, routing, and limits from there.<br>One config per editor. Same endpoint, same tools, everywhere.<br>Rotate or revoke keys from the dashboard — not buried in config files.<br>10 tools activate instantly across every connected editor.

CursorClaude CodeVS CodeWindsurfJetBrains/mcpzephex.devKey validationRate limitingTool routingUsage trackingBilling

Connect once<br>Paste one config and move on<br>Choose your editor, drop in the config, and you're connected.

MCP toolbox<br>10 tools your AI uses to actually know your codebase<br>Built-in tools that scan your real repo, your live packages, and your running architecture — so your AI works with what's actually there, not what it remembers or guesses.

get_project_context<br>Fast, high-signal project brief.<br>check_package<br>Real-time npm package verification.<br>audit_package<br>Breaking changes, CVEs, migration steps.<br>explain_architecture<br>Traces real request/auth/data flows.<br>read_code<br>AST-based symbol reading for safe changes.<br>find_code<br>Fast repo-wide ripgrep.<br>audit_headers<br>Security audit for HTTP/TLS endpoints<br>Zephex_dev_info<br>Extracts content and metadata from a URL.<br>scope_task<br>Get minimal files to read for a task.<br>thinking<br>Plan, verify, and keep session memory.

get_project_context<br>Instant codebase snapshot. Your AI knows your stack before you type the first prompt.

Summarizes the repo’s stack and key integration points (auth, hosting, billing, queues) based on what’s actually present in code and config.<br>When to use<br>You just opened a new repo<br>You need the stack + key entry points<br>You want a safe overview before changing code

View all toolsAPI docs

Real results<br>Developers shipping safer code with Zephex

"My Zephex MCP just saved me from a bad Stripe upgrade. Two prompts in Claude Code. check_package → Stripe is clean, no red flags."<br>— r/ClaudeAI<br>"AI editors are awesome — until they waste half your session just relearning your project. That's why I built Zephex."<br>— @zephex_dev<br>"I connected Zephex MCP to Claude Code, ran two prompts on our Stripe setup, and the output shocked me."<br>— YouTube

Built for real workflows<br>Who uses Zephex<br>Teams that need MCP to feel operational: one endpoint, one control layer, less config drift.<br>One endpointOne control layerLess config drift

Profile 01<br>Solo developers

One setup that survives repo switches, editor changes, and client work.

Where it breaks<br>You bounce between side projects, contract repos, and multiple editors. Native MCP means duplicated config, duplicated tools, and drift every time something changes.

What changes with Zephex<br>Keep one endpoint and one tool surface. Use separate keys for local and client work without rebuilding the whole MCP setup each time.

Repo hoppingMulti-editor setupSeparate local and client keys

Profile 02<br>Startups and product teams

A shared control layer for local, staging, and production work.

0+

requests per month free

0+

code editors supported

endpoint, no local setup

Zephex vs. local MCP and documentation tools<br>Scans your codebase, not a cached library<br>ZephexScans your actual codebase and live npm data<br>OthersReads indexed docs that may be days or weeks old

ZephexKnows your installed package versions, your auth flows, your real architecture<br>OthersKnows what the docs say — not what's actually running in your repo

ZephexOne hosted endpoint — no local server, no npx, no bridge packages<br>OthersLocal install required per editor, per machine, per project

ZephexAPI key management, usage tracking, key rotation from one dashboard<br>OthersManual config file edits per environment

This is why Zephex users catch breaking changes Context7 misses — it reads your repo, not a cached library.See the tools →

Plans<br>Simple pricing, clear limits.<br>Start free. Upgrade when you need more requests, more backends, or custom key scopes.

$0/mo<br>FREE

Requests300 / mo<br>API Keys3<br>MCP Backends1<br>Key scopesFull only

Start free

Recommended<br>$7 / 3.5k req

$7/mo<br>PRO

7-day free trial — full Pro access, cancel anytime<br>Requests3,500 / mo<br>API KeysUnlimited<br>MCP Backends10<br>Key scopesCustom

Choose Pro →

$19 / 10k req

$19/mo<br>MAX

Requests10,000 / mo<br>API KeysUnlimited<br>MCP Backends20<br>Key scopesCustom

Choose Max →

API access<br>Create a key, send one header, call tools.<br>Generate the key in the dashboard, use it as a Bearer token, confirm tools/list, and route actual MCP traffic through the same endpoint.<br>Step 01<br>Create the key

Step 02<br>Send Bearer auth

Step 03<br>Confirm tools

Step 04<br>Route traffic

Read API docsCreate API...