Universal Requirements

Before connecting any editor to Zephex, confirm the shared account, network, and HTTP transport requirements are already in place.

What You Need

Network Requirements

HTTPS access to zephex.dev on port 443.
The Zephex endpoint uses Streamable HTTP with chunked transfer encoding. Confirm your network or proxy does not strip Transfer-Encoding: chunked.
No local ports or firewall rules are required. Zephex is fully cloud-hosted.

Key Format

Your key must be sent exactly like this:

Authorization: Bearer mcp_prod_api-01.your-secret

No quotes around the key value.
The Bearer prefix, with a space after it, is required.
Valid keys use the format mcp_prod_api-01.... (shown masked in the dashboard as mcp_prod_••••-••••).

Editor Compatibility

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.