Was this page helpful?
Installation
Zephex is a hosted MCP server at https://zephex.dev/mcp. You connect it once per editor with the Zephex CLI — browser sign-in, API key, correct config file, connection check. This page is the main setup path; you do not need an AI agent to run these commands.
From any folder (Node 18+). The wizard opens your browser, creates a CLI-scoped key, writes the editor MCP config, and verifies tools.
# One command — pick your editor (or use a flag)npx -y zephex setupnpx -y zephex setup --cursornpx -y zephex setup --vscodenpx -y zephex setup --claude-codenpx -y zephex setup --windsurf --project # After setup: restart the editor (or Reload Window)# Verify from terminal (no AI needed):npx zephex doctornpx zephex statusnpx zephex listlogin is an alias for setup: npx zephex login --cursor = same as setup.
--api-key).npx -y zephex for most others.~/.zephex/credentials.json for terminal tools.You must restart the editor (or use Reload Window) after setup. MCP servers load at startup.
Skip the interactive picker with one flag. Pair --project for repo-local config (e.g. .cursor/mcp.json).
| Editor | Command |
|---|---|
| Cursor | npx zephex setup --cursor |
| Claude Code | npx zephex setup --claude |
| Claude Desktop | npx zephex setup --claude-desktop |
| VS Code | npx zephex setup --vscode |
| OpenCode | npx zephex setup --opencode |
| Codex CLI | npx zephex setup --codex |
| Gemini CLI | npx zephex setup --gemini |
| Antigravity | npx zephex setup --antigravity |
| TRAE | npx zephex setup --trae |
| Windsurf | npx zephex setup --windsurf |
| Zed | npx zephex setup --zed |
| Warp | npx zephex setup --warp |
| Kiro IDE / Kiro CLI | npx zephex setup --kiro |
| JetBrains AI Assistant | npx zephex setup --jetbrains |
| Factory Droid | npx zephex setup --droid |
| Cline | npx zephex setup --cline |
| Kilo Code | npx zephex setup --kilo |
| Continue | npx zephex setup --continue |
| GitHub Copilot CLI | npx zephex setup --copilot |
Full list: Supported editors · per-editor guides under Editors.
You can use Zephex from the shell before connecting any editor. Setup still saves ~/.zephex/credentials.json so Mode 2 works immediately.
No AI agent in the loop. Your shell runs npx zephex; the CLI uploads a search index from disk (inline_files) and calls the same hosted endpoint as your editor.
# Copy-paste test flow (no AI agent)npx zephex setupnpx zephex doctorcd your-app # folder with package.json + srcnpx zephex get-contextnpx zephex find-code "test"npx zephex safe lodashnpx zephex logoutnpx zephex setup # sign in againComplete Mode 2 guide: CLI without an AI agent (9 hosted tools in terminal).
Prove Mode 2 works from your shell before you connect Cursor or VS Code.
| Mode | Who runs tools | How you start |
|---|---|---|
| Mode 1 — Editor MCP | Your AI agent in Cursor, Claude, VS Code, … | npx zephex setup --cursor (or any editor flag) |
| Mode 2 — Terminal CLI | You in bash/zsh/PowerShell — human-readable output | Same setup saves credentials; then npx zephex get-context |
Both modes use the same API key and https://zephex.dev/mcp. Terminal guide: CLI without an AI agent.
# In Cursor / Claude / VS Code chat, ask the agent:"What MCP tools do you have?"# You should see 10 Zephex tools (get_project_context, read_code, find_code, …)From terminal: npx zephex doctor checks Node, network, and MCP; npx zephex status shows key + tier; npx zephex list shows which editor configs exist on disk.
Create a key at zephex.dev/dashboard/keys, then paste into your editor file.
Cursor / Claude Code (hosted HTTP):
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_prod_your_key_here" } } }}VS Code, OpenCode, Windsurf, … (stdio bridge):
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_prod_your_key_here" } } }}HTTP vs stdio details: HTTP vs stdio.
# Remove Zephex from one editor + revoke key server-sidenpx zephex disconnect --cursornpx zephex disconnect --all # Fresh sign-in and config rewritenpx zephex reconnect --vscode # Terminal-only sign-out (editor configs unchanged)npx zephex logoutFull account reference: CLI account & auth.
npx zephex doctor.npx zephex reconnect --cursor.cd into the app folder.More: MCP troubleshooting · npx zephex · Setup walkthrough.