Was this page helpful?
Installation
The Zephex CLI connects your editor to the hosted MCP server. Run npx zephex setup for guided installation, or let your editor call npx -y zephex as a stdio MCP server.
The setup command auto-detects your editor, asks for your API key, writes the correct config file, and verifies the connection — all in one step.
npx zephex setup? Which editor? (auto-detected: Cursor) → Cursor → Claude Code → VS Code → Windsurf → JetBrains → Other ? Your API key: mcp_prod_**** ✓ Wrote .cursor/mcp.json✓ Connection verified — 10 tools available✓ Done. Restart Cursor to activate.When your editor starts an MCP session, it runs npx -y zephex as a child process. The CLI acts as a thin stdio bridge: it receives JSON-RPC requests from your editor, forwards them to the hosted endpoint at https://zephex.dev/mcp with your API key, and streams responses back.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "your_key_here" } } }}The -y flag tells npx to skip the install confirmation prompt. This is required because editors run the command non-interactively.
You can run the CLI directly to test the connection or debug issues:
# Run as stdio MCP server (what your editor calls internally)ZEPHEX_API_KEY="your_key" npx -y zephexThis starts the stdio server. Send a JSON-RPC request to stdin and you will get a response on stdout. Useful for verifying your API key works before configuring an editor.
The package is lightweight — it downloads once and caches locally. Subsequent runs start in under 2 seconds.
Interactive wizard — detects editor, writes config, verifies connection.
Skip editor detection, write Cursor config directly.
Write Claude Code config to ~/.claude.json.
Write VS Code HTTP config to .vscode/mcp.json.