This documentation walks through the core concepts and the minimal flow from your first API key to a working tools/list call from any MCP-compatible editor.
API keys are your authentication token. Create as many as you need. Rotate or revoke individually from the dashboard. Each key inherits the rate limits from its assigned plan.
Generate one API key per environment and keep the endpoint fixed.
Point your editor at /mcp and send the same Bearer header everywhere.
Start with tools/list so transport and auth are confirmed before you debug prompts.
Keep distinct keys for local development, staging, and production. This lets you rotate or revoke a single environment without disrupting the others.
Generate a single bearer token from your dashboard. It works across every editor, environment, and tool. No per-tool credentials are needed.
Use a different key for local, staging, and production. Rotate exposed keys immediately from the dashboard without touching editor configs.
# local developmentZEPHEX_API_KEY="mcp_dev_local-01.your-secret" # stagingZEPHEX_API_KEY="mcp_staging_web-01.your-secret" # productionZEPHEX_API_KEY="mcp_prod_api-01.your-secret"Every request goes to this URL. Use it as the MCP server URL in your editor config. The same endpoint works for all editors.
https://zephex.dev/mcpThe first successful request confirms the only moving parts that matter: the endpoint, the Bearer header, and a working JSON-RPC body.
curl -X POST https://zephex.dev/mcp \ -H "Authorization: Bearer YOUR_API_KEY" \ -H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'The same https://zephex.dev/mcp URL works in VS Code, Claude Code, Cursor, Windsurf, and JetBrains. Configure it once. No per-editor server fleet, no local processes, and no bridge packages just to reach the same tool surface.
One Bearer token authenticates every tool call. Create, rotate, and revoke keys from the dashboard. Use separate keys for local, staging, and production so one exposed key never takes down your whole setup.
Project context, code reading, architecture tracing, package intelligence, URL inspection, security auditing, scoped task planning, and structured reasoning are available as soon as your key is active.
Every request counts against your plan. Free includes 300 requests per month, Pro includes 3,500, and Max includes 10,000. You can see exact usage in real time from the dashboard instead of guessing at month end.
RUNNING MCP LOCALLY
Each editor needs its own server config. You manage npx commands or local processes per machine, per repo, and per editor. API keys scatter across config files, and you do not get a clean usage view unless you build one yourself.
USING ZEPHEX
One config per editor, one key per environment, one dashboard for all of it. The tool surface stays the same whether you are in Cursor on your laptop, VS Code on a remote machine, or Windsurf in a Codespace.
Every editor uses the same endpoint and the same auth model. What changes is where the config lives and what kind of restart is required before the tool list refreshes.
If you care more about the machine you are on than the editor you are using, start here. These pages map home-directory paths, project-root file locations, and verification commands for macOS, Windows, and Linux.
Every editor that supports native HTTP MCP servers accepts this config structure. Copy the snippet into the editor-specific config location, update the header with your API key, and restart the editor session.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "YOUR_API_KEY" } } }}