Behavry Integration — Amazon Kiro
Amazon Kiro supports MCP servers via Streamable HTTP and stdio transports. Configuration uses the mcpServers JSON format.
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 attempting enrollment.
Prerequisites
- Behavry stack running (
make devordocker compose up) - Amazon Kiro installed
- Python 3.11+
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.
Quick Setup
make setup
Manual Configuration
Add to ~/.kiro/settings/mcp.json:
Streamable HTTP (recommended)
{
"mcpServers": {
"behavry": {
"transport": "streamable-http",
"url": "http://localhost:8000/mcp/v1/",
"headers": {
"Authorization": "Bearer <behavry-jwt>"
}
}
}
}
stdio
{
"mcpServers": {
"behavry": {
"command": "behavry-mcp-stdio",
"args": ["--server-url", "http://localhost:8000"],
"env": {
"BEHAVRY_CLIENT_ID": "<client_id>",
"BEHAVRY_CLIENT_SECRET": "<client_secret>"
}
}
}
}
Activate
- Open Kiro → Settings → MCP Servers
- The Behavry server should appear with a connected status
- If not visible, click Reload MCP Servers or restart Kiro
Verify
- Invoke a tool in Kiro
- Check http://localhost:5173 → Live Activity for the event
Token Refresh
make tokens
Kiro picks up the new token on the next MCP request without requiring a restart.