Skip to main content

​
Add the server

Then confirm it registered:
You should see klio with ten tools: recall, remember, observe, plan, decide, note, artifact_put, artifact_get, space, forget.
X-Vex-Agent: claude-code is what makes attribution work later — it is how you tell which agent left a given decision. Pick a stable string and keep it consistent across machines.

​
Make recall reflexive

Claude Code will use the tools when it judges them relevant, but memory pays off when reading is automatic. Add this to CLAUDE.md at your repo root:
Repo-level CLAUDE.md is the right home for this — it travels with the project, so every teammate’s Claude Code picks up the same habit.

​
Scope it to the repo

If you run several projects, give each one its own space so a question about one does not pull answers from another:
X-Vex-Project accepts a git remote URL. If the repo has no remote configured, pass the repository’s root directory path instead — Klio resolves both the same way.
Project resolution fails open — an unrecognised value falls back to org-wide rather than erroring. It is a relevance filter, not a security boundary.

​
Local install

If you are self-hosting, klio init wires Claude Code for you rather than you running claude mcp add by hand:
See Self-hosting.

​
Troubleshooting

Run claude mcp list. If klio is absent the server was never added; if it is present but failing, the key is usually wrong — a bad key returns 401.
Most often the write went somewhere else. Check that both agents use the same key (same org), and that you are not writing with space set but reading without it.
Without instruction, a model treats tools as optional. Add the CLAUDE.md block above — an explicit “call recall first” changes behaviour immediately.