Your AI editor keeps forgetting your project. Zephex fixes that.

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

Stop re-explaining your codebase.

Connect once.

Instead of wiring each editor separately, you point everything at zephex.dev/mcp once and Zephex handles validation, routing, and limits from there.

• One config per editor. Same endpoint, same tools, everywhere.
• Rotate or revoke keys from the dashboard — not buried in config files.
• 10 tools activate instantly across every connected editor.

Connect once

Paste one config and move on

Choose your editor, drop in the config, and you're connected.

MCP toolbox

10 tools your AI uses to actually know your codebase

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

Fast, high-signal project brief.

check_package

Real-time npm package verification.

audit_package

Breaking changes, CVEs, migration steps.

explain_architecture

Traces real request/auth/data flows.

read_code

AST-based symbol reading for safe changes.

find_code

Fast repo-wide ripgrep.

audit_headers

Security audit for HTTP/TLS endpoints

Zephex_dev_info

Extracts content and metadata from a URL.

scope_task

Get minimal files to read for a task.

thinking

Plan, verify, and keep session memory.

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.

When to use

• You just opened a new repo
• You need the stack + key entry points
• You want a safe overview before changing code

View all toolsAPI docs

Real results

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

— r/ClaudeAI

"AI editors are awesome — until they waste half your session just relearning your project. That's why I built Zephex."

— @zephex_dev

"I connected Zephex MCP to Claude Code, ran two prompts on our Stripe setup, and the output shocked me."

— YouTube

Built for real workflows

Who uses Zephex

Teams that need MCP to feel operational: one endpoint, one control layer, less config drift.

One endpointOne control layerLess config drift

Profile 01

Solo developers

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

Where it breaks

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

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

Startups and product teams

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

0+

requests per month free

0+

code editors supported

0

endpoint, no local setup

Zephex vs. local MCP and documentation tools

Scans your codebase, not a cached library

ZephexScans your actual codebase and live npm data

OthersReads indexed docs that may be days or weeks old

ZephexKnows your installed package versions, your auth flows, your real architecture

OthersKnows what the docs say — not what's actually running in your repo

ZephexOne hosted endpoint — no local server, no npx, no bridge packages

OthersLocal install required per editor, per machine, per project

ZephexAPI key management, usage tracking, key rotation from one dashboard

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

Simple pricing, clear limits.

Start free. Upgrade when you need more requests, more backends, or custom key scopes.

$0/mo

FREE

Requests300 / mo

API Keys3

MCP Backends1

Key scopesFull only

Start free

Recommended

$7 / 3.5k req

$7/mo

PRO

7-day free trial — full Pro access, cancel anytime

Requests3,500 / mo

API KeysUnlimited

MCP Backends10

Key scopesCustom

Choose Pro →

$19 / 10k req

$19/mo

MAX

Requests10,000 / mo

MCP Backends20

Key scopesCustom

Choose Max →

API access

Create a key, send one header, call tools.

Generate the key in the dashboard, use it as a Bearer token, confirm tools/list, and route actual MCP traffic through the same endpoint.

Step 01

Create the key

Step 02

Send Bearer auth

Step 03

Confirm tools

Step 04

Route traffic

Read API docsCreate API key

Endpoint

https://zephex.dev/mcp

Authorization

Bearer <your-api-key>

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 should I handle API keys safely?

Treat every key like a secret: keep them out of public repos, rotate any exposed key immediately, and use isolated keys per environment. Zephex makes this easier with scoped key policies from your dashboard.

05What happens if an MCP server crashes or times out?

Zephex surfaces the failure in your operational dashboard in real time. The boundary enforcer catches tool-call errors before they propagate and logs them with full trace context so you can diagnose without reproducing.

06Can I use Zephex with sensitive or proprietary data?

Yes. The single-endpoint model means you control exactly what crosses the boundary. Scoped keys and policy rules let you permit or block specific tools, namespaces, and output shapes — without modifying your client configuration.

07How 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.

08What happens when I hit my request limit?

Requests over your plan ceiling are blocked and surfaced in your dashboard so you can see exactly where the spike happened. You can upgrade at any time — limits reset monthly, and there is no surprise overage billing on Free or Pro.

09Does Zephex work with AI agents and automation pipelines?

Yes. Anything that can send an HTTP request with a Bearer token can call the /mcp endpoint. That includes automated agents, CI workflows, and custom scripts — not just interactive editors. Scoped keys let you give automation a narrower surface than your personal key.

10Can I see which tools my AI is calling?

Yes. Every tool call is logged in your dashboard — name, timestamp, key, and result status. This makes it easy to see what your AI is actually using, catch runaway usage patterns, and verify the right tools are hitting the right backends.

Ready to route your_first endpoint?_

Create API keyRead the docs