npx -y zephex setup --antigravity writes stdio to ~/.gemini/antigravity/mcp_config.json (global only). serverUrl HTTP is optional.
Official Google Antigravity MCP documentation: Antigravity MCP docs
Without MCP, your agent guesses project layout and misses supply-chain risk. Zephex connects one hosted endpoint so every session gets the same ten tools — no per-machine npm installs, no version drift across the team.
HTTP and stdio setups both need a key from your Zephex dashboard. OAuth-only flows (ChatGPT, Claude.ai web) sign you in in the browser instead — skip this section for those.
Matches the published CLI (mcp-proxy/src/commands/setup.ts). One command signs you in, writes the correct transport, and verifies 10 tools.
Account teardown: logout vs disconnect · Connect MCP walkthrough
Search docs for “where is my MCP file” — the answer is always: run list first, then open the path it prints.
Documented paths: ~/.gemini/antigravity/mcp_config.json (global only)
Antigravity wizard writes command/npx + env (not serverUrl) so filesystem tools work.
Runs the same code as mcp-proxy/src/commands/setup.ts — OAuth in browser, creates a CLI key, writes your editor config, verifies tools.
npx -y zephex setup --antigravitySkip browser OAuth — paste a key from zephex.dev/dashboard/keys. Must start with mcp_prod_, mcp_dev_, or mcp_sk_.
npx -y zephex setup --antigravity --api-key mcp_prod_your-key-hereGlobal ~/.gemini/antigravity/mcp_config.json: Transport: stdio (see ~/.gemini/antigravity/mcp_config.json (global only)).
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}After CLI install, fully restart the app if tools do not appear. Manual JSON/TOML blocks below are equivalent — use them when CLI commands are unavailable.
Full comparison: HTTP vs stdio · npx zephex reference
Antigravity uses ~/.gemini/antigravity/mcp_config.json (global only). npx zephex setup --antigravity writes stdio (npx bridge); optional manual serverUrl + Bearer for hosted HTTP.
Replace mcp_sk_your_key_here with your key from Dashboard → API Keys. Copy the full key once at creation — paste into Authorization: Bearer … for HTTP configs, or into ZEPHEX_API_KEY for stdio/npx configs.
command npx — writeAntigravityConfig in setup.ts (global path only).
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Manual remote; do not keep stdio block if you switch.
{ "mcpServers": { "zephex": { "serverUrl": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" } } }}Tip
CLI setup writes stdio to global path only — quit Antigravity fully and start a new agent session after setup.
Note
Antigravity shares the Gemini config tree — do not put this block in .cursor/mcp.json or .vscode/mcp.json.
Run these in a terminal when the editor UI is unclear — catches stale npm, wrong transport, and project shadows.
npx -y zephex@latest listnpx -y zephex@latest doctornpx -y zephex@latest repair# Fully quit the editor (Cmd+Q / Alt+F4), reopen, start a new agent sessionAfter saving your config, confirm Zephex is connected before you rely on it in real work.
Questions people ask when Google Antigravity does not show Zephex tools — indexed for docs search.
Antigravity setup finished but not connected
Global path only. Quit app fully. New agent session. Run setup --antigravity + doctor. No mixed stdio + serverUrl.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Antigravity agent: get_project_context on github:vercel/next.js — focus on package scripts.”
Remote repo intelligence with serverUrl MCP — no local clone required.
“explain_architecture for our Gemini extension’s message flow.”
Diagram clarifies modules before Antigravity edits TypeScript.
“check_package on an MCP SDK prerelease tag before we pin it.”
Version risk surfaced before package-lock changes.
“read_code the tool registration function in our MCP bridge.”
Symbol-level read for extension code.
“audit_headers on our marketing site deployed on Firebase Hosting.”
Header grade independent of IDE workspace.
“check_test: add structured logging to all Cloud Function handlers.”
Scoped file set for a multi-folder Google Cloud project.
Antigravity agents read .gemini/antigravity/mcp_config.json — say github:owner/repo or the opened project path when a tool needs your codebase.
These situations usually mean the setup cannot work until you fix the underlying issue:
Setup ran but Antigravity shows disconnected
Global path only (~/.gemini/antigravity/mcp_config.json). Fully quit app, new agent session. Run npx -y zephex@latest setup --antigravity.
Mixed stdio and serverUrl in same entry
Pick one transport — setup writes stdio; remove serverUrl block or remove command/args if using manual HTTP.
Wrong config path
Use ~/.gemini/antigravity/mcp_config.json, not .cursor, .vscode, or project .gemini/.
npx not found in editor
GUI lacks shell PATH — run npx -y zephex@latest repair; ensure Node is on system PATH.
0 tools listed
Valid JSON under mcpServers; View raw config; restart Antigravity completely.
Tools work but empty repo context
Add github:owner/repo or project path in the prompt.
Antigravity agents reach Zephex through serverUrl — ten tools, one OAuth or Bearer setup:
get_project_context
Reads your project structure, dependencies, scripts, env vars, and framework markers in one call. Replaces manually opening package.json, tsconfig, and multiple config files at the start of every session.
read_code
AST-based code extraction: pass a symbol name and get the implementation without reading entire files. Supports symbol lookup, batched file reads, and structural outlines for large files.
find_code
Ranked search across the repo for definitions, usages, and patterns. Faster than blind grep when the agent does not know where a symbol lives.
check_package
Live registry lookup for npm, PyPI, Cargo, and Go modules. Surfaces typosquat risk, maintainer changes, and suspicious version jumps before you run install.
explain_architecture
Generates Mermaid diagrams for auth flows, service boundaries, and module dependencies so the agent reasons about structure instead of guessing.
check_test
Turns a task description into the smallest file set to read or edit, with risk ratings and caller impact notes.
audit_headers
Grades a deployed URL for CSP, HSTS, TLS, cookies, and redirects. Returns fix snippets for common hosts (Vercel, Cloudflare, Nginx).
keep_thinking
Structured multi-step debugging: tracks hypotheses and conclusions so long investigations do not loop.
Zephex_dev_info
Expert patterns for authentication, databases, frontend frameworks, deployment, and mobile stacks when the agent needs vetted guidance.
project_memory
Persists decisions, gotchas, and conventions per project in ~/.zephex/memory (SQLite FTS5). recall before unfamiliar areas; remember after discoveries. Local stdio only on npx zephex.