Use Klio with Kiro
Pair Kiro's specs with a live board. Add Klio as a remote MCP server for one workspace or all of them.
!Before you start: create a token in Klio under Settings → Connect agents, and use it in place of klio_YOUR_TOKEN.
Add Klio to Kiro's MCP config
Use .kiro/settings/mcp.json for this workspace or ~/.kiro/settings/mcp.json for every workspace.
{ "mcpServers": { "klio": { "url": "https://klio.dev/api/mcp", "headers": { "Authorization": "Bearer klio_YOUR_TOKEN" } } } }Reconnect
Open the Kiro panel → MCP servers and reconnect. Klio's tools appear under it.
Check it works
Ask Kiro: “call klio whoami”.
Then paste the setup prompt
With Kiro connected, this puts the repo on your board and starts building with you. Replace the highlighted part.
Use Klio (klio.dev) as the project board for this repo. It's connected over MCP as "klio". 1. Call whoami to check the connection. If it fails, stop and tell me what to fix. 2. Find this repo's project with list_projects. If there isn't one, create it with create_project: name it after the repo and pick a short key. 3. Record what's already here: call sync_stack with package.json (and any other manifests), add features that already work as done stories, and half-finished work as stories in progress. 4. What I'm building next: <describe it in a sentence or two> Call brief_feature, write small stories with acceptance criteria, show me the plan, and save it with create_feature once I approve. 5. Build it one story at a time: start_issue before you write code, check_criterion as each criterion really passes, complete_issue with a short summary once it's tested. Don't start a second story while one is in progress, and leave Done to me. 6. Before you stop, hand me anything only I can do (secrets, DNS, billing) with flag_for_human.
Other agents
Claude CodeTerminal agentCodexTerminal agentCursorEditorWindsurfEditorVS Code + GitHub CopilotEditorZedEditorClineVS Code extensionGemini CLITerminal agentopencodeTerminal agentAny MCP clientGeneric
Endpoint: https://klio.dev/api/mcp. Menus and file paths can move between Kiro releases; if a step looks different, the server URL and header are what matter.