recall: give Kilo the memories Claude Code already keeps (local MCP entry for kilo.json)

[fainir]

If you use Claude Code and Kilo in the same repo, Kilo starts from zero: Claude Code's memories (your corrections, how you like to work, where things live) sit in Markdown files under ~/.claude/projects/<project>/memory/ that only Claude Code reads.

I built recall, a zero-dependency MCP server that serves those same memories to any MCP client. In the Kilo CLI, add it to ~/.config/kilo/kilo.json (or ./kilo.json for one project), using the local server format from Kilo's MCP docs:

{
  "mcp": {
    "recall": {
      "type": "local",
      "command": ["npx", "-y", "@fainir/recall", "--claude-code", "/path/to/your/repo", "--read-only"],
      "enabled": true
    }
  }
}

Kilo then gets memory_list, memory_get, memory_recall (follows [[wiki-links]] between memories, trimmed to a token budget) and memory_due. Drop --read-only to add memory_write and memory_delete, which write in Claude Code's own format, so both agents share one memory. I checked the command above from a clean home folder today: it starts and lists those four tools. I have not tried it inside the VS Code extension yet; there it should be Settings, MCP, Add Server, local, with the same command.

No vectors, no database, nothing leaves your machine. It finds the same folder Claude Code uses, down to its folder-naming rule.

Repo (MIT): https://github.com/fainir/recall - on npm as @fainir/recall and in the official MCP Registry. I'm the author.

Feedback welcome, especially from anyone who moves between Kilo and Claude Code.