Was this page helpful?
Installation
MCP supports two transport modes. Most editors use stdio (a local process bridges to the server). VS Code uses HTTP (direct HTTPS connection). Both connect to the same hosted endpoint and give you the same 10 tools.
With stdio, your editor launches npx -y zephex as a child process. The CLI reads JSON-RPC requests from stdin, forwards them to the hosted endpoint over HTTPS, and writes responses to stdout. Your editor treats it like a local server even though the actual processing happens in the cloud.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "your_key" } } }}EDITORS THAT USE STDIO
Cursor, Claude Code, Windsurf, JetBrains, Zed, Cline, Goose, Warp, Gemini CLI, Codex CLI, Continue, Roo Code, Trae, Factory AI, OpenCode, Copilot CLI, Kiro IDE, Kiro CLI
WHEN TO USE STDIO
Use stdio when your editor supports it (most do). It is the most compatible option and works behind corporate firewalls that might block direct WebSocket or SSE connections.
With HTTP, your editor connects directly to https://zephex.dev/mcpover HTTPS. No local process is needed. The editor sends JSON-RPC requests as HTTP POST bodies and receives responses in the same connection. This is called "Streamable HTTP" in the MCP specification.
{ "servers": { "zephex": { "type": "http", "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer your_key" } } }}EDITORS THAT USE HTTP
VS Code (native MCP support uses HTTP with prompted API key input)
WHEN TO USE HTTP
Use HTTP when your editor supports it natively and you want zero local processes. The connection is direct — no npx, no Node.js child process, no local CLI. Slightly faster startup since there is no process spawn overhead.
✓ Works with 18 editors
✓ Works behind firewalls
✓ No CORS issues
△ Requires Node.js for npx
△ Small startup delay (~1-2s first run)
✓ No local process needed
✓ Instant startup
✓ No Node.js dependency
△ Fewer editors support it natively
△ May be blocked by strict firewalls
Both transports connect to the same hosted endpoint (https://zephex.dev/mcp) and authenticate with the same API key. You get the same 10 tools regardless of which transport your editor uses. The only difference is how the request gets from your editor to the server.
Not sure which to pick? Use stdio — it works with every editor and is the default for npx zephex setup. See the full editor list for specific config instructions.