Integrations · Claude Code
Compile your AI. Use it in Claude Code.
One command writes the MCP server entry into ~/.claude/settings.json. Reload Claude Code. Your compiled recipe is now a first-class tool. Local execution. No keys to paste. No outbound traffic from the recipe path.
Step 01
Install the integration.
The installer detects Claude Code and writes mcpServers.kolm into ~/.claude/settings.json. Existing keys in the settings file are preserved. Re-running is idempotent.
kolm install claude-code --apply
Step 02
Reload Claude Code.
On next launch Claude Code reads ~/.claude/settings.json and starts the kolm MCP server in the background over stdio. You see kolm.compile, kolm.run, kolm.inspect, and kolm.query in the tool list.
# quit and relaunch Claude Code # then in any project, ask: > what kolm tools do you have available?
Step 03
Call the tool.
Claude Code invokes kolm.run over MCP. The recipe runs locally against your .kolm artifact. Every call carries _kolm metadata (artifact hash, K-score, recipe id) that Claude logs in the session transcript.
> use kolm.run pr-review on this diff > use kolm.run support-triage on this ticket > show me the K-score for the last call
What lands in ~/.claude/settings.json
The installer merges this block into your existing settings. Other keys (theme, model preferences, hooks) stay untouched. The command is the absolute path of the kolm binary, so PATH changes don't break the integration.
~/.claude/settings.json
{
"mcpServers": {
"kolm": {
"command": "/usr/local/bin/kolm",
"args": ["serve", "--mcp"],
"env": {
"KOLM_HOME": "~/.kolm"
}
}
}
}
What you get.
Stdio transport.
Claude Code launches the kolm process and talks to it over stdin/stdout. No port to allocate. No HTTP unless you pass --http.
Four tools exposed.
kolm.compile mints a recipe. kolm.run executes one. kolm.inspect verifies the artifact. kolm.query hits your RAG sidecar.
Per-call provenance.
Every response includes _kolm metadata: artifact hash, recipe id, K-score, run id. Claude shows it inline. Replay any call.
Settings merge, not overwrite.
If you've customized ~/.claude/settings.json already, the installer keeps everything else. Only mcpServers.kolm is touched.
Skill files compose.
Drop a CLAUDE.md in your project and Claude Code picks up project-level kolm rules alongside the MCP tools.
Dry-run first.
Without --apply the installer prints the diff it would write. Read it. Then re-run with the flag.
Ready to compile.
If you don't have the CLI yet, the quickstart walks you through compiling your first recipe. If you want every MCP tool the kolm server exposes, the spec page is the reference.