Was this page helpful?
Add this to your Kilo Code MCP configuration (project .kilocode/mcp.json or global MCP settings in the Kilo UI). Zephex uses streamable-http to https://zephex.dev/mcp — internet required, no npx. See Kilo Code MCP docs for how Kilo Code handles MCP on their side.
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.
You can configure through Kilo’s MCP UI (HTTP / streamable HTTP) or by editing JSON. Both must end with the same url, headers, and disabled: false.
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" and url https://zephex.dev/mcp. 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
If both global and project MCP files exist, know which one Kilo loads for this workspace — wrong file edits are the #1 silent failure.
After saving your config, confirm Zephex is connected before you rely on it in real work.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“Kilo agent mode: scope_task for adding Stripe billing portal to our Next.js app.”
Scoped plan inside VS Code before Kilo edits routes and API handlers.
“get_project_context on this workspace — Kilo sees the VS Code root folder.”
Usually works when .kilocode/mcp.json sits at the repo root.
“read_code the middleware.ts edge handler only.”
Precise read for Vercel-style middleware files.
“check_package on @tanstack/react-query v5 migration target.”
Pre-install check before Kilo updates package.json.
“find_code all usages of useServerAction in app/.”
App router search without manual ripgrep in Kilo chat.
“audit_headers on our preview deployment URL from the last PR.”
Preview env security check from the IDE.
You do not pick tools from a menu — ask your agent in normal sentences. Half of the tools only need a package name or URL; the other half need to know which codebase you mean (your Mac/Windows project folder or a GitHub repo).
These situations usually mean the setup cannot work until you fix the underlying issue:
Wrong transport type
Use "streamable-http" with url — not stdio or command/npx.
401 Unauthorized
Header Authorization: Bearer mcp_sk_... in JSON or UI — no extra quotes around the key in the UI field.
Config saved but server missing
Reload VS Code window. Confirm file path is workspace/.kilocode/mcp.json.
Tools work for packages but not code
Open the correct workspace folder at repo root, or pass github: or absolute path in the prompt.
0 tools listed
Set disabled: false, enable server in Kilo MCP UI, start new agent session after reload.
Kilo streamable-http server exposes ten tools in agent mode inside VS Code:
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.
audit_package
Deep package intelligence: CVEs with severity, breaking changes between versions, migration notes, and peer-dependency conflicts.
explain_architecture
Generates Mermaid diagrams for auth flows, service boundaries, and module dependencies so the agent reasons about structure instead of guessing.
scope_task
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.