Kiro CLI should use the stdio MCP config shown below. Start with `npx -y zephex`, then fall back to absolute paths only if your environment cannot find `npx`.
OVERVIEW
Kiro CLI is the renamed Amazon Q Developer CLI, now part of the Kiro IDE ecosystem from AWS. For Zephex, the reliable setup is the stdio MCP config in `~/.kiro/settings/mcp.json` or `<project>/.kiro/settings/mcp.json`, passing your key through `ZEPHEX_API_KEY`.
CONFIG FILE LOCATION
~/.kiro/settings/mcp.json for a global setup, or <project>/.kiro/settings/mcp.json for a project-local one.
Paste the JSON exactly as shown. If you came from Amazon Q Developer CLI, use the new `~/.kiro/` path instead of the old `~/.aws/amazonq/` location.
Replace `mcp_sk_your_key_here` with your real Zephex API key before saving.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Use the Kiro MCP UI to confirm the MCP server actually connected.
Make sure the file is at `~/.kiro/settings/mcp.json`, not under the old `~/.aws/amazonq/` path.
Install Node.js so Kiro can launch `npx`, or switch the config to absolute `node` and `zephex` paths if your environment does not inherit PATH correctly.
This usually means Kiro launched without your shell PATH. Install `zephex` globally and use absolute executable paths as the fallback config.
If the editor still does not connect, return to Quickstart or check Connection Issues.