Add Zephex to .roo/mcp.json at your workspace root (or Roo’s global MCP settings). Zephex uses streamable-http to https://zephex.dev/mcp — internet required, no npx.
Official Roo Code MCP documentation: Roo Code 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: <project>/.roo/mcp.json (project root)
Roo Code reads .roo/mcp.json — setup writes stdio npx zephex so repo tools can read your workspace.
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 --rooSkip browser OAuth — paste a key from zephex.dev/dashboard/keys. Must start with mcp_prod_, mcp_dev_, or mcp_sk_.
npx -y zephex setup --roo --api-key mcp_prod_your-key-hereProject .roo/mcp.json — run from your repo root: Transport: stdio (see <project>/.roo/mcp.json (project root)).
{ "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
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.
Required type: "streamable-http". Do not use command/npx for Zephex.
{ "mcpServers": { "zephex": { "type": "streamable-http", "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" }, "disabled": false } }}Tip
Project .roo/mcp.json overrides global Roo MCP — edit the file Roo actually loads for this workspace.
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 Roo Code does not show Zephex tools — indexed for docs search.
How do I connect Zephex to roo-code?
Fastest: npx -y zephex setup --roo (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 roo-code MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
roo-code 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 roo-code?
mcpcli disconnect --roo — revokes key and strips config.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Roo Code: check_package task=upgrade from our locked vite version to latest 6.x — breaking changes first.”
Upgrade brief before Roo edits config and plugins.
“get_project_context on .roo/mcp.json project — monorepo or single package?”
Clarifies which package.json Roo should treat as primary.
“read_code the zod schema for UserInput in packages/shared.”
Shared-package symbol read without opening the whole package.
“check_package on a dependency Roo is about to add via auto-approve.”
Safety pause before automatic install.
“audit_headers on our customer admin portal URL.”
Admin surface header audit from Roo chat.
“keep_thinking while Roo fixes a flaky Playwright test — track attempts.”
Avoids retry loops in long Roo tasks.
Roo autonomous mode: .roo/mcp.json at workspace root — paste github: URLs for repos not opened as the VS Code folder.
These situations usually mean the setup cannot work until you fix the underlying issue:
No zephex in Roo
File must be .roo/mcp.json at workspace root with mcpServers wrapper.
0 tools
Use streamable-http + url, not command. Reload VS Code.
Auth failed
Authorization: Bearer <full key> in headers.
Wrong repo context
Not a connection issue — add github:owner/repo or absolute path in the prompt.
Legacy npx still runs
Delete command/args/env stdio entry for zephex.
Roo reads .roo/mcp.json — ten hosted tools for autonomous modes:
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.