Behavry Integration — Amazon Kiro

Amazon Kiro speaks MCP over Streamable HTTP using the mcpServers JSON format. It connects to Behavry's unified MCP gateway (/mcp/v1) with the agent's client credentials as an HTTP Basic header.

Enterprise MCP Registry

If your organization manages a Kiro MCP registry, ask your Kiro admin to add the Behavry proxy to the allow-list before enrolling.

---

Prerequisites

• A running Behavry instance (your control-plane URL, or http://localhost:8000 for a local stack)
• Amazon Kiro installed
• An enrolled agent (gives you the client_id / client_secret)

---

1. Enroll the agent

In the dashboard: Agents → Enroll Agent → Kiro (Amazon). Behavry provisions the agent and gives you the config block to paste, with credentials filled in.

2. Config file locations

Scope	Path
Global	~/.kiro/settings/mcp.json
Workspace	<workspace>/.kiro/settings/mcp.json
Legacy (Q Developer CLI)	~/.aws/amazonq/mcp.json (not read by Kiro)

Kiro migrated from Amazon Q Developer CLI (November 2025); legacy configs at ~/.aws/amazonq/mcp.json must be migrated manually.

3. Config block

Merge under the mcpServers key:

{
  "mcpServers": {
    "behavry": {
      "url": "https://<your-behavry-host>/mcp/v1",
      "headers": {
        "Authorization": "Basic <base64(client_id:client_secret)>"
      }
    }
  }
}

---

Activate

1. Open Kiro → Settings → MCP Servers
2. behavry should appear with a connected status
3. If not visible, click Reload MCP Servers or restart Kiro

Verify

Invoke a tool in Kiro. The tool call appears in the dashboard → Live Activity.

---

Troubleshooting

401 Unauthorized — Credentials wrong or agent revoked. Re-enroll and paste the fresh block.

Server not connecting — Confirm the url ends in /mcp/v1, the backend is reachable (curl https://<your-behavry-host>/health), and (for enterprise registries) that the proxy is allow-listed.