Installation
Some editors connect to Zephex over HTTPS with Bearer auth instead of local stdio. This page covers the shared pattern — then link to your editor-specific guide.
Use stdio (npx -y zephex) when your editor spawns a local process — Cursor, Claude Code, Windsurf, JetBrains. Use HTTP + Bearer token when the editor expects a remote URL (VS Code, Claude.ai, many OAuth flows). Same API key, same 10 tools.
Replace YOUR_API_KEY with a key from Dashboard → API Keys. Endpoint is always https://zephex.dev/mcp.
{ "servers": { "zephex": { "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } } }}Native HTTP MCP in .vscode/mcp.json
Custom connector + OAuth
Developer Mode → Create App
grok.com/connectors → Custom
OAuth in opencode.json
context_servers + HTTP
settings.json transport
MCP settings with remote URL
.kiro/settings/mcp.json
tools/list — you should see 10 Zephex tools.Bearer mcp_..../.well-known/oauth-protected-resource.Stuck? See MCP troubleshooting.