npx -y zephex setup --kiro writes stdio to ~/.kiro/settings/mcp.json (writeKiroConfig in setup.ts). type http is optional.
Official Kiro CLI MCP documentation: Kiro CLI 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: ~/.kiro/settings/mcp.json or <project>/.kiro/settings/mcp.json
Kiro hot-reloads stdio config — matches working Kiro setups in the wild.
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 --kiroSkip browser OAuth — paste a key from zephex.dev/dashboard/keys. Must start with mcp_prod_, mcp_dev_, or mcp_sk_.
npx -y zephex setup --kiro --api-key mcp_prod_your-key-heremcpServers command/args/env: Transport: stdio (see ~/.kiro/settings/mcp.json or <project>/.kiro/settings/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
kiro-cli mcp add with --type http or edit ~/.kiro/settings/mcp.json — then run /mcp inside a session to confirm zephex loaded.
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/args/env — recommended.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Hosted URL only if you use github: paths for repo tools.
{ "mcpServers": { "zephex": { "type": "http", "url": "https://zephex.dev/mcp", "headers": { "Authorization": "Bearer mcp_sk_your_key_here" }, "disabled": false } }}Tip
Project .kiro/settings/mcp.json wins over ~/.kiro when both define zephex.
Note
Kiro IDE uses the same ~/.kiro/settings/mcp.json path — different app, same file shape.
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 Kiro CLI does not show Zephex tools — indexed for docs search.
How do I connect Zephex to kiro-cli?
Fastest: npx -y zephex setup --kiro (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 kiro-cli MCP config?
Run npx -y zephex@latest list — it prints every config path on this machine that references Zephex.
kiro-cli 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 kiro-cli?
mcpcli disconnect --kiro — revokes key and strips config.
You do not call tools yourself — ask your agent in plain language. Try these once Zephex is connected:
“kiro-cli chat: get_project_context on ~/.kiro/settings/mcp.json project or global cwd.”
HTTP mcp.json loads zephex for /mcp slash command visibility.
“read_code the main agent loop in our CLI package.”
Symbol read for CLI maintainers.
“check_package on uv/typer-related deps before kiro-cli mcp add workflow.”
Python CLI ecosystem safety.
“check_test: add --json output flag to three subcommands.”
Scoped cmd/ tree changes.
“find_code error types returned from MCP client wrapper.”
Debug connection issues faster.
“Zephex_dev_info for MCP OAuth vs API keys — which fits our CLI?”
Integration design without guessing MCP spec details.
Run /mcp in an interactive kiro-cli session to confirm zephex loaded. Project .kiro/settings/mcp.json overrides user ~/.kiro/settings/mcp.json.
These situations usually mean the setup cannot work until you fix the underlying issue:
Server not loaded
Valid ~/.kiro/settings/mcp.json JSON.
0 tools
type http + url + headers.
mcp add error
Match kiro-cli version flags from kiro.dev docs.
OAuth prompt
Zephex uses Bearer only — not OAuth.
Tools excluded
See Kiro validation rules for tool name length.
kiro-cli mcp.json type http — ten tools; verify with /mcp:
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.