Connection Issues

"zephex" does not appear in my editor after restart.

1. Confirm the config file is in the exact location for your editor.
2. Validate the JSON is syntactically correct. No trailing commas and no // comments inside JSON files.
3. Fully quit and reopen the editor. A window or tab reload is not sufficient for most editors.
4. Check the editor's developer console or MCP log for error messages.

Every request returns {"error":"unauthorized"}.

1. Confirm the key is valid — generate a fresh key from Dashboard → API Keys if unsure.
2. Confirm the header is exactly Authorization: Bearer YOUR_KEY.
3. Check the key has not been deleted from the dashboard.
4. Generate a new key and test again with the raw curl command from API Reference.

I see 0 tools in my editor.

1. Most editors require a full quit-and-reopen after adding MCP config.
2. Once restarted, check the editor's MCP or tools panel.
3. If you still see 0 tools, run the curl tools/list check from API Reference.

rate_limit_exceeded errors.

1. Check your current month's usage in the dashboard.
2. If you have not used your full limit, contact support through the feedback form.
3. If you have used your limit, upgrade to Pro (3,500 req/mo) or Max (10,000 req/mo) from the pricing page.

Requests timeout or hang.

1. Zephex uses chunked HTTP streaming. Some corporate proxies strip chunked transfer encoding and cause hangs.
2. Test with direct curl to separate a network issue from a config issue.
3. If you are on a corporate network, ask IT whether Transfer-Encoding: chunked is allowed to zephex.dev.