Was this page helpful?
Support
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.
Local stdio servers run on your machine and are fast/private but create N×M config drift across editors, machines, and teammates. A hosted MCP gateway (remote HTTP) like Zephex gives every editor and every teammate the same 10 tools through one key and one endpoint. You get central usage analytics, key rotation, and production-grade tools (package CVE scanning, header audits, stateful keep_thinking) without shipping heavy scanners to every laptop. The tradeoff is one network hop and the rate limits of your plan.
Free: 555 requests/month. Pro: 3,500 ($7/mo). Max: 10,000 ($19/mo). When you exceed it you receive HTTP 429 with a Retry-After header — share your link for +300 bonus requests or upgrade. Limits reset at the start of the next calendar month.
Google’s managed MCP servers are excellent when your data already lives in BigQuery, Cloud Storage, or Firebase and you want IAM/OAuth + zero-ops. Zephex is the practical hosted gateway for general developer workflows across any stack: AST code reading, task scoping with risk assessment, real package migration + CVE intelligence across 12 ecosystems, HTTP header audits, and multi-step reasoning that actually persists state. It works with Cursor, Claude Code, Zed, JetBrains, Gemini CLI, and the full 19+ editor list from a single key. Use Google services for Google data; use Zephex for everything else an agent needs to understand and change real codebases.
Code is processed ephemerally for the duration of the tool call only. Zephex does not train on customer code and does not retain source beyond what is required to answer the current request. See the security and data-use pages for the full model.
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: 555 requests/mo. Pro ($7/mo): 3,500 requests. Max ($19/mo): 10,000 requests. Share your link for +300 bonus requests when someone clicks it.
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.