Lore MCP Server

lore

Semantic search across your Claude Code conversations. Find anything you've ever discussed -- across all projects, all sessions, any branch.

Features

• Hybrid search (vector + keyword) Combines multilingual-e5-small embeddings with FTS5/BM25 via Reciprocal Rank Fusion. Finds results by meaning and exact terms.

• Fully local, zero API keys Everything runs on your machine. ONNX Runtime for embedding, sqlite-vec for storage. No data leaves your device.

• Auto-index on search Search returns instantly using the existing index. The current session is then indexed in the background so new content appears in the next search. No hooks, no cron jobs, no blocking.

• Background indexing Manual index triggers return instantly. Monitor progress while you keep working. Search what's already indexed while the rest catches up.

• Project-selective Register only the projects you care about. Add or remove anytime. Unregistering deletes indexed data to keep things clean.

• Conversation-aware chunking Splits by logical turns (user question + full assistant response chain), not arbitrary token windows. Handles tool-use chains, thinking blocks, and multi-step interactions correctly.

• 100+ languages Korean, Japanese, Chinese, English, and 90+ more. CJK-aware token estimation for accurate chunking.

Quick Start

Add to Claude Code

# No install needed — always runs latest version
claude mcp add -s user lore -- npx getlore

# Or for a single project only
claude mcp add -s project lore -- npx getlore

Add to OpenAI Codex CLI

# No install needed
codex mcp add lore -- npx getlore

npm install -g getlore

# Then register with your tool:
claude mcp add -s user lore -- getlore   # Claude Code
codex mcp add lore -- getlore            # Codex CLI

# Manage your install:
getlore --version   # Check installed version
getlore update      # Update to latest

Usage

Once connected, the AI can use lore's tools directly:

You: "What did we discuss about auth refactoring last week?"

Claude: [calls lore search] Found 3 relevant conversations...
        In your "my-webapp" project on March 15, you decided to...

First time setup:

1. Browse projects -- lore shows all your Claude Code projects
2. Register -- pick which ones to index
3. Index -- runs in background, takes ~15 seconds per project
4. Search -- ask anything about past conversations

Tools

rebuild mode requires confirm: true as a safety gate — the parameter is hidden from the tool schema, so the AI must ask you before triggering a destructive reindex.

Why This Exists

Claude Code stores every conversation as a JSONL transcript in ~/.claude/projects/. After a few weeks, you have hundreds of sessions across dozens of projects -- discussions about architecture decisions, debugging sessions, code reviews, and design explorations.

But there's no way to search through them. You can't ask "what approach did we take for the auth middleware?" or "which project had that database migration discussion?"

Existing tools either require cloud APIs, spawn zombie processes, or treat conversations as generic documents. lore is purpose-built for Claude Code sessions: it understands turn boundaries, tool-use chains, and thinking blocks. It runs entirely locally with zero dependencies beyond Node.js.

How It Works

~/.claude/projects/*/*.jsonl
        |
   JSONL Parser (extracts user/assistant messages, skips noise)
        |
   Turn-pair Chunker (groups by logical conversation turns)
        |
   Transformers.js (multilingual-e5-small, INT8 quantized, 384d)
        |
   sqlite-vec + FTS5 (hybrid vector + keyword storage)
        |
   Reciprocal Rank Fusion (combines both signals for ranking)

Storage: Single SQLite file at ~/.lore/lore.db with WAL mode for concurrent reads.

*Config: