Use Klio with Codex

Connect OpenAI Codex to Klio over streamable HTTP. Keep the token in an environment variable so it never lands in a config file.

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

    Put this in your shell profile (~/.zshrc or ~/.bashrc).

    terminal
    export KLIO_TOKEN=klio_YOUR_TOKEN
  2. Add the server

    Either run the command, or add the block to ~/.codex/config.toml.

    terminal
    codex mcp add klio --url https://klio.dev/api/mcp --bearer-token-env-var KLIO_TOKEN
  3. Or edit the config

    ~/.codex/config.toml
    [mcp_servers.klio]
    url = "https://klio.dev/api/mcp"
    bearer_token_env_var = "KLIO_TOKEN"
  4. Check it works

    Run codex, then /mcp. Klio's tools are listed. Ask: “call klio whoami”.

Then paste the setup prompt

With Codex 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

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