"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
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.
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
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
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 →
FAQ
Questions beforeyou connect
Quick answers for evaluation, setup, and security review.
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.
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.
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.
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.