Configuration
Before connecting any editor to Zephex, confirm the shared account, network, and HTTP transport requirements are already in place.
zephex.dev on port 443.Transfer-Encoding: chunked.Your key must be sent exactly like this:
Authorization: Bearer mcp_prod_api-01.your-secretBearer prefix, with a space after it, is required.mcp_prod_api-01.... (shown masked in the dashboard as mcp_prod_••••-••••).Zephex uses HTTP transport over HTTPS. Any MCP client that supports HTTP transport with custom headers will work.
Editors that use stdio-only MCP transport are not compatible without a bridge. Zephex does not support stdio.