lore — Claude Code MCP server: one searchable memory across agents
Pools session transcripts from several coding agents into a single local database any MCP client can search. Useful when the window compacted and you need that earlier debugging thread back.
claude mcp add lore -- npx -y @jordanhindo/loreWhat lore does
Lore writes everything to ~/.lore/lore.db on your own machine. Every connected agent reads the same store, so a session you ran in Claude shows up from Cursor too. The index keeps identifiers such as getUserById and file names searchable as whole tokens instead of splitting them apart.
Filling the store is a single command: lore setup detects the harnesses on the box and indexes each one. You can also point it at a directory yourself, for instance lore index ~/.claude/projects for Claude or lore index ~/.codex/sessions --source codex. Cursor and openclaw are picked up through --source. The npm package ships the lore skill plus lore-recall, lore-brief, lore-handoff and lore-dev-verification.
Node 22 or newer is required. When npm install trips over better-sqlite3, the build from source is the other route. A global CLI goes stale quietly, and lore status --json exposes the mismatch by reporting a schemaVersion above supportedSchemaVersion.
What it helps with
- recover what one agent learned from another agent's session
- pick up a debugging thread lost to context compaction
- index Claude and Codex transcripts into the same store
- search code identifiers and file names without losing them to tokenisation
- hand off work between sessions as a brief or handoff note
Example prompts for the agent
- Set up lore and prove search works against my past sessions
- Look in lore for how we fixed the error in
auth.tslast time - Index
~/.claude/projectsincluding the subagent transcripts
How to install lore
Platform CLI
claude mcp add lore -- npx -y @jordanhindo/lorePlatform CLI
codex mcp add lore -- npx -y @jordanhindo/loreConfig file
{
"mcpServers": {
"lore": {
"command": "npx",
"args": [
"-y",
"@jordanhindo/lore"
]
}
}
}Config file
{
"servers": {
"lore": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@jordanhindo/lore"
]
}
}
}Platform CLI
gemini mcp add lore npx -y @jordanhindo/loreStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about lore
How do I install lore in Claude Code?
Run claude mcp add lore -- npx -y @jordanhindo/lore, then reload the client.
What does lore do?
It indexes your agents' session transcripts into a local database and serves them over MCP. Work captured in a transcript stays searchable once the context window has compacted.
Does lore need the CLI installed globally?
For indexing and lore status, yes: npm install -g @jordanhindo/lore@latest, with Node 22+. After that lore setup locates the history directories on its own.
