Use Klio with Kimi Code

Add Klio to Kimi Code CLI so it can pick up a story, tick its criteria as they pass and hand it back for review.

Connect by signing in

Kimi Code supports MCP sign-in, so there's no token to copy. You approve it in Klio and choose which projects it can reach; disconnect it any time in Settings → Agents.

1. Add Klio with only its URL

   No headers.

   ~/.kimi-code/mcp.jsonCopy

   {
     "mcpServers": {
       "klio": {
         "url": "https://klio.dev/api/mcp"
       }
     }
   }

2. Sign in

   Start Kimi Code and log in to the server. Your browser opens Klio's approval screen.

   terminalCopy

   /mcp-config login klio

Or connect with a token

For setups where you'd rather paste a token, or a version of Kimi Code without sign-in.

1. Add Klio to mcp.json

   Use ~/.kimi-code/mcp.json for every project, or .kimi-code/mcp.json in one repo. You can also run /mcp-config in Kimi Code to add it interactively.

   ~/.kimi-code/mcp.jsonCopy

   {
     "mcpServers": {
       "klio": {
         "url": "https://klio.dev/api/mcp",
         "headers": {
           "Authorization": "Bearer klio_YOUR_TOKEN"
         }
       }
     }
   }

2. Check it works

   Ask Kimi Code: “call klio whoami”. For a full check, paste the verification prompt: it runs the whole loop on a sandbox story and gives Kimi Code a badge.

Then paste the setup prompt

With Kimi Code 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

Endpoint: https://klio.dev/api/mcp. Menus and file paths can move between Kimi Code releases; if a step looks different, the server URL and header are what matter.