zephex
Zephex is a hosted MCP gateway built for AI coding editors. It gives your agent 10 ready-to-use tools — check npm packages for vulnerabilities, audit security headers, read and search code, trace request flows, get project context from any repo, and more. One API key, works instantly with Claude Code, Cursor, VS Code, Windsurf, and others. Free to start at zephex.dev.
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
"I connected Zephex MCP to Claude Code, ran two prompts on our Stripe setup, and the output shocked me."
— YouTube
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.
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.
Ready to route your_first endpoint?_
Create API keyRead the docs
相關伺服器
PDF to PNG
A server that converts PDF files to PNG images. Requires the poppler library to be installed.
File Merger
A simple utility to combine multiple files into a single file.
Music Collection MCP Server
Access and manage local music collections with advanced metadata, classification, and analytics.
Edit File Lines MCP Server
Make precise line-based edits to text files within allowed directories.
ZIP MCP Server
Compress and decompress ZIP files, with support for multi-file packaging, password protection, and encryption.
FilerMoverMcp
A file mover tool that stages and executes file moves safely. Works as both a CLI tool and an MCP server for AI agents.
MCP Source Tree Server
Generates a JSON representation of a directory's source file tree, respecting .gitignore patterns.
Filesystem MCP Server
A Ruby server for performing filesystem operations like reading and writing files within specified directories.
AgentMcp
A local server that allows AI to execute Windows CMD commands, read/write files, and manage directories within a specified path.
Recon
Recon indexes your codebase into a knowledge graph and exposes it via 14 MCP tools. AI agents get dependency mapping, blast radius analysis, safe multi-file rename, execution flow tracing, Cypher queries, semantic search, and PR review — without reading every file. Supports 13 languages, live re-index in ~50ms, and zero config setup.