Kiro CLI

Kiro CLI uses the hosted Zephex MCP URL with browser-based OAuth. The config contains only the URL, not an Authorization header or pasted API key.

OVERVIEW

Kiro CLI is the renamed Amazon Q Developer CLI, now part of the Kiro IDE ecosystem from AWS. If you previously used Amazon Q Developer CLI, your existing configs at `~/.aws/amazonq/` are migrated to `~/.kiro/` on first install. Zephex connects through the OAuth browser flow with Dynamic Client Registration. A working DCR endpoint on the Zephex server is required, otherwise Kiro falls back to an internal client ID that Zephex will reject.

CONFIG FILE LOCATION

~/.kiro/settings/mcp.json. Global config. Same location for both Kiro IDE and Kiro CLI.

PREREQUISITES

Kiro CLI installed from https://kiro.dev or via your AWS tooling workflow.
A Zephex account at zephex.dev/signup.
No API key needed. Authentication is handled through the OAuth browser flow.

CONFIG

Paste the JSON exactly as shown. Kiro only needs the hosted MCP URL. If you came from Amazon Q Developer CLI, the old `~/.aws/amazonq/default.json` path is dead and Kiro migrates it automatically on first run.

Do not add an Authorization header or paste an API key into this file. Kiro expects OAuth discovery. If you see `invalid_client` or `unauthorized_client`, the usual cause is a missing Dynamic Client Registration endpoint on the Zephex server.

~/.kiro/settings/mcp.json

{  "mcpServers": {    "zephex": {      "url": "https://zephex.dev/mcp"    }  }}

AUTH

Save the config file at ~/.kiro/settings/mcp.json.
Start Kiro CLI or restart the Kiro IDE.
On first connection Zephex triggers the OAuth flow.
A browser window opens. Log in to your Zephex account.
After login, Kiro stores the token and the connection is live.

VERIFY

Use the Kiro MCP UI to confirm the hosted server actually connected.

Run `kiro` and check the MCP tools panel.
You should see "zephex" listed as connected with 10 tools.

COMMON ISSUES

Config not found

Make sure the file is at `~/.kiro/settings/mcp.json`, not under the old `~/.aws/amazonq/` path.

"invalid_client" error

Kiro CLI requires the Zephex server to support Dynamic Client Registration. If DCR is not live, Kiro falls back to using `Q DEV CLI` as the client ID, which Zephex rejects. This is a server-side issue, not a user mistake.

Token prompt appears in a loop

Fully quit Kiro CLI or the Kiro IDE, then restart it so the saved token state is reloaded cleanly.

If the editor still does not connect, return to Quickstart or check Connection Issues.