Connect Open Kioku as a local MCP server so Claude Code can search your code, resolve symbols, trace impact, build plans, and verify edits from a local index.
Install, index, connect, prompt. Indexing time depends on repo size; Open Kioku commands run locally on your machine.
Install the CLI globally. The npm wrapper pulls the native binary for macOS, Linux, or Windows automatically.
$ npm install -g open-kioku
Navigate to your project directory and run the indexer. Open Kioku scans files, extracts symbols, builds a dependency graph, and creates local SQLite + Tantivy search indexes under .ok/.
$ ok index .
Generate the MCP configuration for Claude Code. The command prints a JSON snippet — paste it into your Claude Code MCP settings file.
$ ok mcp install claude --repo .
{
"mcpServers": {
"open-kioku": {
"command": "ok",
"args": [
"mcp",
"serve",
"--repo",
"/absolute/path/to/repo",
"--read-only"
]
}
}
}Add this prompt to your CLAUDE.md file or system instructions. It tells Claude Code to gather evidence from Open Kioku before every edit and verify changes afterward.
Use Open Kioku before editing. Check repo_status, search_code, get_definition,
get_references, impact_analysis, and find_tests_for_change. Build a plan with
plan_change first, then edit, and verify after the edit with verify_change.Every Open Kioku tool runs locally against your indexed repo. No hosted index or embeddings service required, read-only by default.
Build an evidence-backed edit plan with primary context, impact candidates, validation targets, and boundary policies — before touching a single file.
After editing, verify the change stayed within the plan's boundaries and didn't break expected contracts.
BM25-ranked code search returning snippets with file paths, line ranges, and confidence scores.
Jump to the definition of any symbol — functions, classes, types — from the local symbol index.
Find every reference to a symbol across the codebase using indexed graph edges, not text matching.
Trace which modules, callers, and dependents a proposed change would affect before it happens.
Identify which tests cover the files and symbols you're about to change, so the agent runs the right ones.
Check index health, file counts, symbol totals, and last-indexed timestamps at a glance.
Assemble a focused context window of relevant files, symbols, and tests for a specific task.