Connection Issues

Most setup failures come down to config location, stale editor sessions, or Bearer auth mistakes. Reduce the problem to the shared endpoint and one tools/list call first.

zephex DOES NOT APPEAR IN MY EDITOR

Check that the config file is in the correct location for your editor.
Fully restart the editor. A window reload is not enough for most clients.
Validate the JSON is syntactically correct: no trailing commas, no comments in JSON.
Check the editor MCP logs for parsing or auth errors.

UNAUTHORIZED

I SEE UNAUTHORIZED ON EVERY REQUEST

Confirm the key starts with zph_.
Confirm the header is exactly Bearer YOUR_KEY.
Check that the key was not revoked or deleted in the dashboard.
Generate a fresh key and retry if you suspect copy or rotation issues.

RATE LIMITS

I SEE rate_limit_exceeded

Check current usage in the dashboard.
If usage looks wrong, contact support with the failing key ID and timestamp.
If you exceeded your monthly limit, upgrade to Pro for 3,000 requests.

UNEXPECTED RESULTS

TOOLS RETURN EMPTY OR UNEXPECTED RESULTS

Confirm the tool arguments are valid for the hosted environment.
Cloud-hosted Zephex cannot read arbitrary files from your private local filesystem.
For repo analysis, use a reachable repo path or the supported integration flow rather than a private local path.

TIMEOUT

Zephex uses HTTP streaming. Confirm your client supports chunked responses and that your network allows outbound HTTPS to zephex.dev.

timeout-check.sh

curl -v https://zephex.dev/mcp \  -H "Authorization: Bearer YOUR_KEY" \  -H "Content-Type: application/json" \  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'