Kiro Integration¶

Give Kiro access to MisakaNet's indexed failure-recovery lessons via MCP.

Setup¶

Add the MisakaNet entry to your Kiro MCP config.

User scope — ~/.kiro/settings/mcp.json:

{
  "mcpServers": {
    "misakanet": {
      "url": "https://misakanet.org/mcp"
    }
  }
}

Project scope — .kiro/settings/mcp.json at the repository root (committable):

{
  "mcpServers": {
    "misakanet": {
      "url": "https://misakanet.org/mcp"
    }
  }
}

Kiro reads mcpServers (same key as Claude Code), but uses url for remote MCP endpoints. No type field needed — Kiro infers the transport from the url value.

Optional: attach a token (unlocks write tools)¶

{
  "mcpServers": {
    "misakanet": {
      "url": "https://misakanet.org/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MISAKANET_TOKEN"
      }
    }
  }
}

Get a token: misakanet_register → node_id + token (see token-acquisition).

Usage¶

In Kiro's chat, ask:

"Search MisakaNet for DCO sign-off failure"
"Find lessons about pip install timeout"
"What does MisakaNet know about GitHub token issues?"

Demo Queries¶

Query	What you'll get
DCO sign-off failed	Fix workflow with `--amend --signoff`
pip install timeout	SSL/proxy timeout solutions
GitHub token exposed	Secret scanning response pattern
database locked	SQLite WAL mode + timeout fix
Feishu document cleared	API deletion safety pattern

Troubleshooting¶

Issue	Fix
Tools not showing up	Verify key is `mcpServers` and `url` is set (no `type` field needed)
Config not picked up	Check file location: user scope `~/.kiro/settings/mcp.json`, project scope `.kiro/settings/mcp.json`
"connection failed"	Ensure URL is `https://misakanet.org/mcp` (not `http`); remote endpoint requires HTTPS