Kiro
Add Runstack MCP in Kiro IDE/CLI — .kiro/settings/mcp.json with streamable HTTP or stdio.
Source: https://runstack.engineer/docs/mcp-kiro
kiro
Kiro (AWS) is an AI IDE/CLI with native MCP. Configure Runstack's MCP tools at https://app.runstack.engineer/mcp with Authorization: Bearer rnsk_…. Get a key at API Keys.
Config files
Kiro reads mcp.json at two scopes (mirrors Gemini CLI / VS Code pattern):
- Global:
~/.kiro/settings/mcp.json— applies to all projects - Workspace:
.kiro/settings/mcp.json— project-specific (travels with repo, use for team-shared servers)
Use workspace scope for project-specific servers; use global for personal defaults. Both use the same mcpServers shape.
Add a server via UI
In Kiro IDE: Settings → MCP → Add Server → paste one of the JSON blocks below. Kiro also supports Import from … for migration.
Manual JSON
Remote (Streamable HTTP) — recommended
{
"mcpServers": {
"runstack": {
"url": "https://app.runstack.engineer/mcp",
"headers": {
"Authorization": "Bearer rnsk_YOUR_API_KEY"
},
"disabled": false,
"autoApprove": []
}
}
}
Some Kiro builds require type: "streamableHttp" alongside url (like Cline). If tools do not load, add "type": "streamableHttp".
Local (stdio) — via @rnsk/mcp
{
"mcpServers": {
"runstack": {
"command": "npx",
"args": ["-y", "@rnsk/mcp"],
"env": {
"RUNSTACK_API_KEY": "rnsk_YOUR_API_KEY"
},
"disabled": false
}
}
}
CLI
For Kiro CLI, configure the same file and run:
kiro mcp list
kiro mcp add --name runstack --url https://app.runstack.engineer/mcp --header "Authorization: Bearer rnsk_..."
Verify
In Kiro chat: “Use Runstack to search for Linear tools”. Confirm runstack is green/active and methods search_tools / execute_tool are listed. OAuth for Gmail, GitHub, etc. still routes through Runstack's initiate_connection when check_authentication says token_missing.
Governance (Enterprise)
Settings → Governance → MCP Registry URL can enforce an allow-list of MCP servers. Ensure https://app.runstack.engineer/mcp is allow-listed if your org uses a registry JSON.