Integrations · Zed
Run your .kolm inside Zed in 60 seconds.
One command writes the context_servers entry. Restart Zed. Your compiled AI shows up as a tool the assistant can call. The model runs on your machine. No API calls leave the box. Native to Zed's MCP support, no plugin required.
Step 01
Install the integration.
One command. The installer detects Zed, writes the context_servers entry to your Zed settings.json, and pins the kolm binary by absolute path. Re-running is idempotent.
kolm install zed --apply
Step 02
Restart Zed.
Zed re-reads the user settings.json at startup. After restart your compiled model shows up as an MCP context server inside the assistant panel. No further configuration. No keys to paste.
# cmd-q then re-launch osascript -e 'quit app "Zed"' && open -a "Zed"
Step 03
Use it. The model runs locally.
Open the assistant in Zed (cmd-shift-A) and call your kolm tool. The recipe runs in-process. Zero outbound API calls. The same byte-exact .kolm artifact you compiled on the laptop is what the editor invokes.
# in the Zed assistant > @kolm.run support-triage classify this ticket > @kolm.run pr-review score this PR
What lands in Zed's settings.json
Open the file after running the installer. This is the entire change. No telemetry. No phone-home. The command is the absolute path of the kolm binary the installer detected, so the entry stays valid even if your PATH changes.
~/.config/zed/settings.json (macOS / Linux)
{
"context_servers": {
"kolm": {
"command": "/usr/local/bin/kolm",
"args": ["serve", "--mcp"],
"env": {
"KOLM_HOME": "~/.kolm"
}
}
}
}
What you get.
Native MCP.
Zed ships context_servers out of the box. No plugin. No extension. Just a settings entry.
Local execution.
The MCP server runs in-process over stdio. No daemon. No HTTP unless you opt in with --http on port 8765.
Zero outbound calls.
Zed talks to the kolm process. The kolm process executes the recipe against your local model. Nothing leaves the machine.
Reproducible.
Every tool call ships _kolm metadata (artifact hash, recipe id, K-score). Zed logs it. You can replay any call.
Idempotent install.
Re-running kolm install zed --apply updates the entry in place. No duplicate servers. No drift.
Dry-run first.
Drop the --apply and the installer prints what it would write. Audit it. Then re-run with --apply.
Ready to compile.
If you don't have the CLI yet, the quickstart is one page. If you want the MCP surface itself, the spec page lists every tool the kolm server exposes.