Connecting services and preparing your dashboard.
The fastest answers to the setup and behavior questions new users ask most often.
No. Zephex is cloud-hosted. The only local change is the MCP config you add in your editor. You do not need npm packages, local Node processes, or bridge servers just to connect.
Yes, as long as the code is available on the machine you are working from. The code-analysis tools operate on project paths or file paths, not GitHub URLs. Private repos are not fetched automatically from GitHub by the hosted endpoint.
Running MCP servers locally means managing Node processes, updating packages, and configuring each client separately. Zephex hosts the proxy for you — same endpoint, same access controls, no local infrastructure.
Cursor, Claude Code, VS Code, Windsurf, JetBrains, and any other MCP-compatible client. If the editor supports the MCP spec, it works with Zephex.
Most users connect in under 2 minutes — create an API key in the dashboard, add one config snippet to the editor, restart once. No npm install, no local servers.
No. Zephex does not use customer prompts, tool inputs, tool outputs, or code for model training. See the Data Use page for the full policy.
Revoke it immediately from the dashboard and create a new one. Keys are shown once at creation — if you miss copying it, rotate to a fresh key.
Yes. Create separate keys for local, staging, and production. Each key can have different backend access and rate limits.
Free tier: 300 requests/mo. Pro ($7/mo): 3,500 requests. Max ($19/mo): 10,000 requests. All tiers include unlimited API keys.
Upgrade to a higher tier, wait for the reset window, or contact support. Rate limits are per API key and displayed in the dashboard.
Contact support within 14 days of payment for a refund on Pro or Max tiers. Free tier has no charges.
Yes. Contact support for custom tiers, SLAs, dedicated infrastructure, and custom integrations.
