Docs / Guides Build
Connecting Claude Code
Register the EKOS MCP server and use the ekos-knowledge and memory skills.
Register the server
claude mcp add ekos -- ekos --config /path/to/ekos.toml mcp serve --workspace /path/to/workspace
claude mcp get ekos # Status: Connected
Scopes: add -s user to make it available in every project (it then serves the same ledger everywhere), or leave the default for the current project only.
Restart Claude Code after changing a registration. In a running session, /mcp reconnects.
What Claude can do
| Ask | Claude uses |
|---|---|
| "What tables do we have about orders?" | ekos_search, ekos_ekl |
| "What does this function return / what depends on it?" | ekos_query, ekos_dependents |
| "What breaks if I change X, three levels deep?" | ekos_impact |
| "What changed since yesterday?" | ekos_diff |
| "Why does EKOS think that?" | ekos_state, ekos_audit |
The repository ships two Claude Code skills, ekos-knowledge and memory, under .claude/skills/, that teach Claude when and how to use these tools.
Common problems
| Symptom | Cause / fix |
|---|---|
| "search index schema is stale … open writable to self-heal" | A newer EKOS added an indexed field. Run ekos ledger repair (or any writable ekos build) once, then reconnect |
| Tools return another project's data | The server's --workspace points elsewhere. Check claude mcp get ekos |
| Tools missing after upgrading | Restart Claude Code; the tool list is fetched at connect time |