Integrations · Cursor
Run your .kolm inside Cursor in 60 seconds.
One command writes the MCP entry. Restart Cursor. Your compiled AI shows up as a tool the editor can call. The model runs on your machine. No API calls leave the box.
Step 01
Install the integration.
One command. The installer detects Cursor, writes the MCP server entry to ~/.cursor/mcp.json, and pins the kolm binary by absolute path. Re-running is idempotent.
kolm install cursor --apply
Step 02
Restart Cursor.
Cursor reads ~/.cursor/mcp.json at startup. After restart your compiled model shows up as an MCP tool inside the agent panel. No further configuration. No keys to paste.
# macOS osascript -e 'quit app "Cursor"' && open -a Cursor # Linux / Windows # just close and reopen Cursor
Step 03
Use it. The model runs locally.
Ask Cursor to 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 Cursor agent panel > classify this ticket using kolm.run support-triage > score this PR using kolm.run pr-review
What lands in ~/.cursor/mcp.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.
~/.cursor/mcp.json
{
"mcpServers": {
"kolm": {
"command": "/usr/local/bin/kolm",
"args": ["serve", "--mcp"],
"env": {
"KOLM_HOME": "~/.kolm"
}
}
}
}
What you get.
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.
Cursor 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). Cursor logs it. You can replay any call.
Idempotent install.
Re-running kolm install cursor --apply updates the entry in place. No duplicate servers. No drift.
Works offline.
Once the .kolm is on disk, the integration runs with no internet. Useful on a plane. Useful in an air-gapped VPC.
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.