Add Zephex as a Streamable HTTP or SSE MCP server in Warp (Settings → Agents → MCP servers, or file-based ~/.warp/.mcp.json). Zephex endpoint: https://zephex.dev/mcp with Authorization Bearer — not npx.
Official Warp MCP documentation: Warp 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: ~/.agents/.mcp.json or <project>/.agents/.mcp.json
Warp file-based MCP uses command/args at the top level.
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 --warpSkip browser OAuth — paste a key from zephex.dev/dashboard/keys. Must start with mcp_prod_, mcp_dev_, or mcp_sk_.
npx -y zephex setup --warp --api-key mcp_prod_your-key-hereIf you edit by hand after setup: Transport: stdio (see ~/.agents/.mcp.json or <project>/.agents/.mcp.json).
{ "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
In the UI choose Streamable HTTP or SSE (URL) — paste url + headers. Or use file-based config below.
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.
Works in MCP + Add multi-server JSON or ~/.warp/.mcp.json mcpServers.
{ "mcpServers": { "zephex": { "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" } } }}Tip
Project .warp/.mcp.json requires manual approval to spawn — toggle it on in MCP settings after trusting the repo.
Note
Warp also reads MCP from Claude/Codex provider files when auto-spawn is enabled — prefer explicit Zephex URL config to avoid stdio drift.
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 Warp does not show Zephex tools — indexed for docs search.
How do I connect Zephex to warp?
Fastest: npx -y zephex setup --warp (browser sign-in, writes config, verifies 10 tools). Or paste manual config on this page, save, fully quit the app, reopen.
Where did setup save my warp MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
warp works in terminal but not in the editor
GUI apps often lack nvm/fnm PATH. Run npx -y zephex@latest repair, ensure Node is on system PATH, fully quit the editor.
How do I disconnect Zephex from warp?
mcpcli disconnect --warp — revokes key and strips config.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Warp agent: run check_package on a crate before cargo add in this Rust service repo.”
Terminal-native agent uses URL MCP from Warp Drive settings.
“get_project_context on the repo linked from ~/.warp/.mcp.json.”
File-based MCP follows you across Warp sessions.
“check_test: add circuit breaker around our payment client.”
Scoped backend changes before Warp runs shell commands.
“find_code RetryPolicy implementations.”
Search then edit in the same block session.
“audit_headers on https://api.staging.internal (if reachable from your network).”
Staging URL audit from dev machine.
“keep_thinking on an incident — Warp agent logs hypotheses in Zephex.”
Incident debugging with structured notes.
Warp agents use the repo tied to your session or .warp/.mcp.json. Paste github: URLs for code you have not cloned on this machine.
These situations usually mean the setup cannot work until you fix the underlying issue:
No tools
URL transport, not CLI Command npx.
Auth failed
Authorization: Bearer in headers.
Server stopped
Start from MCP servers UI; check logs.
npx in config
Use url + headers only.
Project file not spawning
Approve .warp/.mcp.json in settings.
Warp URL/SSE MCP — ten tools for block and agent workflows:
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.