Universal Requirements

Every editor integration shares the same hosted endpoint, the same Bearer auth model, and the same verification loop. Keep these constant before debugging anything client-specific.

ACCOUNT

You need a Zephex account. Free tier is enough to connect and validate the flow.
You need at least one active API key created from the dashboard.
You need an editor or client that supports HTTP MCP configuration.

CREDENTIALS

The only required secret is the API key in a Bearer header. Use separate keys for local, staging, and production so usage and revocation stay isolated.

headers.txt

Authorization: Bearer YOUR_API_KEYZEPHEX_ENDPOINT=https://zephex.dev/mcp

TRANSPORT

HOSTED MCP ENDPOINT

https://zephex.dev/mcp

Zephex is a cloud-hosted proxy. There is no stdio transport, no local MCP package to install, and no separate per-editor endpoint. The same URL is reused everywhere.

VERIFICATION

FIRST CHECK

Verify tools before prompting an agent

Restart the editor, open a fresh session, and confirm the tool list is non-empty. If it is not, stop and validate the endpoint and Bearer header before changing anything else.