Skip to content
  1. Home
  2. Help center
  3. Account & billing
  4. Connect an AI client

Connect an AI client

Last updated:

KO hands your project data to an AI assistant: it reads reports, insights, journals and diagnostics and answers your questions in plain words, without opening the interface. That takes a key — you issue it yourself and paste it into your client as a ready-made line from the screen.

Issue a key

  1. In your personal settings, open Connect AI.
  2. Press Add key…
  3. In Name, write where this key will live: “laptop”, “team assistant”. The name is how you will know which key to revoke later.
  4. In Valid for, choose 30 days, 90 days, A year or No expiry.
  5. Optional: in Projects, tick the ones the key is limited to. Nothing ticked — the key sees every project you have access to. With many projects, use Find a project; Clear all drops the ticks.
  6. Press Issue.

The key appears in a line above the list. It is shown once: KO stores only its fingerprint, so the screen cannot show it again. Copy it now with Copy — or take a ready-made snippet from the How to connect block below, where the key is already inside.

If you did not save the key, issue a new one and revoke the old one. A string shown once cannot be brought back.

Connect Claude Code

In How to connect, take the Claude Code card: one command with the key already in it.

  1. Press Copy.
  2. Paste the line into your terminal and run it.

The command registers the server at user level, so it appears in all of your projects at once, not only in the directory you happen to be in.

Connect VS Code

The VS Code card gives you a .vscode/mcp.json file. The key is deliberately not inside it: the file lives in your repository and would go to git with the first commit, so the editor asks for the key itself and keeps it in its own secret store.

  1. Press Copy and put the file in your repository as .vscode/mcp.json.
  2. Open the file and press Start above the ko block.
  3. When the editor asks for the key, paste it. The key sits on the card under the file, next to its own Copy button.

If you need the server in every project rather than in one repository, run MCP: Open User Configuration from the command palette and paste the same servers block there.

Connect any other agent

The Any AI agent card is a ready-made prompt. Copy it into the chat of an agent that can edit files: Claude Code, Cursor, Copilot in agent mode. It writes the config itself and checks the connection for you.

Claude Desktop and claude.ai do not accept a static key: their connector only supports signing in. That way of connecting is on the way — until then, a key does not help those two.

The server address, if you ever need it by hand, is written at the bottom of the block as Server address.

Verify

Ask the assistant to list your projects — it will call the ko_list_projects tool. A list of projects instead of a refusal means the connection works.

On the KO side you see it in the Issued keys table: the Last call column shows a date instead of Never. The mark is written at most once a minute, so refresh the page after a minute rather than straight away.

What the assistant can read

The key opens eight tools, and every one of them only reads: the list of projects, a report, insights, the metric catalogue, the description of a report and of a project, a journal and diagnostics. There is no writing through the API — neither an assistant nor a program can change a setting or the data.

A key adds no rights, it only narrows them. It acts on your behalf and sees exactly what you see in KO: a project you were not given access to does not open through a key either. The Allowed column shows what the key may do; the tooltip holds the full permission keys.

Revoke a key you no longer need

In Issued keys, press ··· in the key’s row:

  • Rename — when it is no longer clear whose key it is and where it runs.
  • Revoke — the key stops working immediately, and everything connected with it stops receiving data. Revoking cannot be undone: you can only connect again with a new key.

Revoked and expired keys stay in the table — their State column says Revoked or Expired. When no live key is left, the screen says No live keys, and Show all brings the revoked and expired ones back into the table.

If it does not add up

  • The assistant says it has no access. Check the State column for your key: Revoked or Expired means it will not work again — issue a new one.
  • YOUR_KO_API_KEY ended up in the config. That is not a key but the place for one: this is how the examples look once the key can no longer be shown. Paste yours, or issue a new key.
  • The assistant sees fewer projects than you expected. The key is limited to a list of projects — the Projects column shows how many, and the tooltip which ones.
  • The KO tools never appeared in the agent. The config is written but the server is not running: in VS Code it starts with Start above the ko block, in other clients by restarting the session after the config changed.
  • Claude Desktop or claude.ai will not connect. That is not a fault: they do not accept a static key, and nothing on the KO side can work around it.

What is nearby

  • Settings → Access — who sees the project and what they may do. A key inherits your rights, it does not extend them.
  • How a report works — what exactly the assistant reads when it asks for a report.