Sign inOpen the board

Connect any MCP client

Klio speaks the Model Context Protocol over streamable HTTP. Any agent that supports remote MCP servers with headers can connect.

!Before you start: create a token in Klio under Settings → Connect agents, and use it in place of klio_YOUR_TOKEN.

  1. Point the client at Klio

    Streamable HTTP, JSON responses, bearer auth.

    terminal
    URL:     https://klio.dev/api/mcp
Header:  Authorization: Bearer klio_YOUR_TOKEN

  2. Check the token

    The health endpoint tells you whether a token works, without an MCP client.

    terminal
    curl -s https://klio.dev/api/mcp/health \
  -H "Authorization: Bearer klio_YOUR_TOKEN"

  3. Stdio-only agents

    Use the Klio CLI as a bridge: it speaks stdio to your agent and HTTP to Klio. Configure your agent to run klio mcp.

    terminal
    npm i -g ./packages/cli   # from the Klio repo
klio login --url https://klio.dev --token klio_YOUR_TOKEN
klio mcp

  4. Check it works

    Call the whoami tool. It returns your name, workspace and projects.

iErrors tell you what's wrong: -32001 no token sent, -32002 the header isn't Authorization: Bearer klio_…, -32003 the token isn't recognised (revoked or from another server).
iCalling from a script? Send a descriptive User-Agent (e.g. my-agent/1.0). Some default library agents, like Python's Python-urllib, can be blocked by Cloudflare's browser check before they reach Klio.

Then paste the setup prompt

With your agent connected, this puts the repo on your board and starts building with you. Replace the highlighted part.

The setup prompt
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 CopilotEditorZedEditorKiroEditorClineVS Code extensionGemini CLITerminal agentopencodeTerminal agent
PreviousopencodeNextMCP tools

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