Kiro IDE uses `.kiro/settings/mcp.json` for MCP servers. The format is identical to Kiro CLI — workspace configs override global.
OVERVIEW
Kiro is an AI IDE by AWS built on spec-driven development. It uses the standard `mcpServers` JSON format. Workspace-level configs at `<project>/.kiro/settings/mcp.json` take precedence over the global config at `~/.kiro/settings/mcp.json`. The format is identical to Cursor and most other editors.
CONFIG FILE LOCATION
Create this file: .kiro/settings/mcp.json in your project root. The `settings` subdirectory is required — do not put it directly in `.kiro/mcp.json`.
Paste the JSON exactly as shown. The format is the same as Cursor, so if you already have a working Cursor config, you can copy it directly.
Replace `mcp_sk_your_key_here` with the real key from Dashboard → API Keys.
{ "mcpServers": { "zephex": { "command": "npx", "args": ["-y", "zephex"], "env": { "ZEPHEX_API_KEY": "mcp_sk_your_key_here" } } }}Open the config directly from the IDE:
Verify the server loaded before using it.
The path must be `.kiro/settings/mcp.json` — not `.kiro/mcp.json`. The `settings` subdirectory is required.
Verify `npx` is on your PATH. Kiro launches processes from your system shell. Run `which npx` in your terminal to check.
Workspace config (`<project>/.kiro/settings/mcp.json`) overrides global (`~/.kiro/settings/mcp.json`). If both exist, workspace wins.
Validate the file has no trailing commas or comments. Run `cat .kiro/settings/mcp.json | python3 -m json.tool` to check.
If the editor still does not connect, return to Quickstart or check Connection Issues.