Connect once
Configure your editor or client to talk to a single `/mcp` endpoint instead of wiring every backend manually.
Use Zephex to make your development work 10x faster
Zephex is a hosted Model Context Protocol proxy with one unified MCP endpoint, API-key authenticated routing, and MCP tools for Cursor, Claude, VS Code, and Windsurf.
How it works
What Zephex Does
Replace fragmented MCP setup with one secure endpoint and one API key flow.
Route safely
Zephex validates the API key, enforces limits, and routes tool calls across your connected backends.
Operate with visibility
Track usage, keys, and billing in one dashboard so your team can manage access and costs confidently.
A toolbox for faster, safer changes
Use these MCP tools to understand a repo, find the right code, and pull current docs — with clear guidance on when to use each tool.
get_project_context
Get a verified snapshot of the repo.
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
Built for real workflows
Who It’s For
Zephex supports individual developers and teams that need reliable MCP operations.
Solo developers
Ship faster with a cleaner setup path and fewer moving parts when you switch projects or editors.
Startups and product teams
Keep one integration surface while your stack changes, and avoid ad-hoc key sharing across environments.
Platform and ops teams
Enforce rate limits, rotate/revoke keys, and monitor usage from one control layer.
.cursor/mcp.json
Trust at a glance
Security & Data Use at a Glance
These are verified controls from the current Zephex implementation and policies.
API keys are not stored in plaintext
Server-side key validation uses hashing, and dashboard flows support key revocation and rotation.
Tier-based limits and abuse protection
Rate limiting and usage enforcement help protect infrastructure from abuse and runaway traffic.
Clear data handling policy
Data Use and Privacy pages explain what is processed to run the service and what is not used for model training.
Simple pricing that scales with you
Start free, upgrade when you need more requests and backends.
Most Popular
Pro
$7/mo
7-day free trial
First-time offer
$7/month
- 3,000 requests/month
- Up to 10 backends
- Email support
Max
$19/mo
0Included
Priority support + highest limits
- 10,000 requests/month
- Up to 20 backends
- Priority support
Prices in USD. Usage limits reset monthly. Keep API keys secret.
API keys, explained
Your API key authenticates every request to Zephex. Create it in the Dashboard, then add it to your client once.
- 1Create an API key in Dashboard → API keys.
- 2Send it as a Bearer token in the Authorization header.
- 3Call the MCP endpoint and start using
tools/listandtools/call.
Authenticate
Authorization: Bearer mcp_sk_••••••••••••••••••••••••••••••••
Call MCP
curl -X POST https://zephex.dev/mcp \
-H "Authorization: Bearer mcp_sk_xxx" \
-H "Content-Type: application/json" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'Never share your API key. Rotate it immediately if it’s exposed.
FAQ
Common Questions
Quick answers for first-time evaluation and setup.
How long does setup take?
Most users can connect in a few minutes: create a key, paste one config snippet, and call the MCP endpoint.
Which clients are supported?
Zephex provides setup guidance for Cursor, Claude Code, VS Code, Windsurf, JetBrains, and other MCP-compatible clients.
Do you train AI models on my tool content?
No. Zephex states that prompts, tool inputs, tool outputs, and code are not used to train AI models.
How should I handle API keys safely?
Treat keys like secrets: keep them out of public repos, rotate exposed keys immediately, and use separate keys per environment.