Does lore require an API key?

No. It runs fully locally and does not require API keys.

How does search rank results?

It combines multilingual-e5-small vector embeddings with FTS5/BM25 keyword search using Reciprocal Rank Fusion.

Can projects be excluded from indexing?

Yes. Projects are indexed by default, and manage_projects can exclude or include them.

Where is lore's data stored?

The default database is ~/.lore/lore.db, with configuration stored in ~/.lore/config.json.

Lore

semantic-searchclaude-codecodexlocalknowledge-management

Search Claude Code and OpenAI Codex CLI conversations locally with hybrid semantic and keyword retrieval.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "hyunjae-labs-lore": {
      "command": "npx",
      "args": [
        "-y",
        "getlore"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

lore indexes Claude Code and OpenAI Codex CLI conversation files into a local SQLite database. It combines multilingual embeddings with FTS5/BM25 keyword search using Reciprocal Rank Fusion, and supports background indexing, project exclusions, session browsing, and context expansion. Use it when you need to retrieve decisions, debugging discussions, or other details from past coding sessions without sending data to a cloud service.

Use cases

Search past coding conversations by meaning or exact terms

Browse indexed sessions for a specific project

Expand search results with surrounding conversation context

Exclude projects from automatic indexing

Monitor or rebuild background indexing

Key features

Hybrid vector and keyword search

Claude Code and Codex CLI session indexing

Local ONNX embeddings and SQLite storage

Background and automatic session-end indexing

Project inclusion and exclusion management

Conversation-aware multilingual chunking

Capabilities & Tool Schemas (6)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Lore.

manage_projects

Exclude/include projects from indexing (opt-out model)

index

Start background indexing. All non-excluded projects. Modes: `incremental` (default), `rebuild`, `cancel

status

Check indexing progress, ETA, skip reasons, DB health

search

Semantic + keyword search across conversations

get_context

Expand search results with surrounding conversation

list_sessions

Browse indexed sessions by project

Documentation Overview

lore

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

Features

Hybrid search (vector + keyword) Combines multilingual-e5-small embeddings with FTS5/BM25 via Reciprocal Rank Fusion. Finds results by meaning and exact terms.
Multi-agent: Claude Code + Codex CLI Indexes both ~/.claude/projects/ (Claude Code) and ~/.codex/sessions/ (OpenAI Codex CLI) in the same DB. Codex sessions are grouped by cwd from session_meta, surfaced as codex-<path> virtual projects so you can search them together or filter to one agent.
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 session end A SessionEnd hook automatically indexes all new sessions in the background. No manual triggers needed.
Background indexing Manual index triggers return instantly. Monitor progress while you keep working. Search what's already indexed while the rest catches up.
Opt-out by default All projects are indexed automatically. Exclude the ones you don't want. No registration needed.
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

bash

# 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

bash

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

Alternative: global install (faster startup, works offline)

Terminal

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:

Code

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:

Index -- index() scans all projects automatically, runs in background
Search -- ask anything about past conversations
Exclude (optional) -- hide noisy projects you don't care about

Tools

Tool	Purpose
`manage_projects`	Exclude/include projects from indexing (opt-out model)
`index`	Start background indexing. All non-excluded projects. Modes: `incremental` (default), `rebuild`, `cancel`
`status`	Check indexing progress, ETA, skip reasons, DB health
`search`	Semantic + keyword search across conversations
`get_context`	Expand search results with surrounding conversation
`list_sessions`	Browse indexed sessions by project

Why This Exists

Claude Code stores every conversation as a JSONL transcript in ~/.claude/projects/, and OpenAI Codex CLI stores its rollouts in ~/.codex/sessions/YYYY/MM/DD/. After a few weeks, you have hundreds of sessions across dozens of projects, often spread across both agents -- 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 AI coding sessions: it understands turn boundaries, tool-use chains, and thinking blocks, and parses both Claude Code and Codex JSONL formats natively. It runs entirely locally with zero dependencies beyond Node.js.

How It Works

Code

~/.claude/projects/*/*.jsonl     ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl
        \                                       /
         \                                     /
          JSONL Parser (Claude Code + Codex formats, 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)

Codex sessions are grouped by cwd extracted from each file's session_meta line and surfaced as codex-<path> virtual projects in the index.

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

Config: Project exclusions stored in ~/.lore/config.json.

Configuration

Environment Variables

Variable	Default	Description
`LORE_DIR`	`~/.lore`	Data directory
`LORE_DB`	`~/.lore/lore.db`	Database path
`CLAUDE_PROJECTS_DIR`	`~/.claude/projects`	Claude Code transcripts location
`CODEX_SESSIONS_DIR`	`~/.codex/sessions`	OpenAI Codex CLI rollouts location

Performance

Measured on Apple Silicon (M-series):

Metric	Value
Search latency	20-30ms
Index speed	~10 sessions/sec
First search (cold model load)	~5s
DB size	~0.1MB per 10 sessions
Model size (downloaded once)	~112MB

Troubleshooting

"No sessions found"

Run manage_projects with action list to see available projects. All are indexed by default unless excluded.

Stale lock file

If indexing was interrupted, the lock file auto-cleans on next run (PID-based detection).

DB corruption

Delete ~/.lore/lore.db and re-index. Your source data (~/.claude/projects/) is never modified.

Development

bash

git clone https://github.com/hyunjae-labs/lore.git
cd lore
npm install
npm run build
npm test          # 135 tests

Tech Stack

Model Context Protocol SDK -- stdio transport
@huggingface/transformers -- multilingual-e5-small (INT8)
better-sqlite3 + sqlite-vec -- embedded vector DB
Reciprocal Rank Fusion -- hybrid search ranking

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Knowledge & Memory View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

294

Package downloads in the last 30 days.

Last commit

4mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Lore

It indexes Claude Code files from ~/.claude/projects/ and OpenAI Codex CLI sessions from ~/.codex/sessions/.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/hyunjae-labs-lore?style=directory)](https://allmcps.com/mcp/hyunjae-labs-lore)

HTML Embed

<a href="https://allmcps.com/mcp/hyunjae-labs-lore"><img src="https://allmcps.com/api/badge/hyunjae-labs-lore?style=directory" alt="Lore on AllMCPs" /></a>

Technical Specs & Signals

CategoryKnowledge & Memory

PricingFree

11/11 checks healthy over the last 33d

56Quality signal: Good · 56/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools27/30

Adoption & activity5/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 27d ago via OSV.dev · getlore (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🧠 Knowledge & Memory →Best MCP servers for Memory & Knowledge →Alternatives to Lore →Install in Claude Desktop Install in Cursor Install in VS Code

Lore

semantic-searchclaude-codecodexlocalknowledge-management

Search Claude Code and OpenAI Codex CLI conversations locally with hybrid semantic and keyword retrieval.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "hyunjae-labs-lore": {
      "command": "npx",
      "args": [
        "-y",
        "getlore"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Search past coding conversations by meaning or exact terms

Browse indexed sessions for a specific project

Expand search results with surrounding conversation context

Exclude projects from automatic indexing

Monitor or rebuild background indexing

Key features

Hybrid vector and keyword search

Claude Code and Codex CLI session indexing

Local ONNX embeddings and SQLite storage

Background and automatic session-end indexing

Project inclusion and exclusion management

Conversation-aware multilingual chunking

Capabilities & Tool Schemas (6)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Lore.

manage_projects

Exclude/include projects from indexing (opt-out model)

index

Start background indexing. All non-excluded projects. Modes: `incremental` (default), `rebuild`, `cancel

status

Check indexing progress, ETA, skip reasons, DB health

search

Semantic + keyword search across conversations

get_context

Expand search results with surrounding conversation

list_sessions

Browse indexed sessions by project

Documentation Overview

lore

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

Features

Hybrid search (vector + keyword) Combines multilingual-e5-small embeddings with FTS5/BM25 via Reciprocal Rank Fusion. Finds results by meaning and exact terms.
Multi-agent: Claude Code + Codex CLI Indexes both ~/.claude/projects/ (Claude Code) and ~/.codex/sessions/ (OpenAI Codex CLI) in the same DB. Codex sessions are grouped by cwd from session_meta, surfaced as codex-<path> virtual projects so you can search them together or filter to one agent.
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 session end A SessionEnd hook automatically indexes all new sessions in the background. No manual triggers needed.
Background indexing Manual index triggers return instantly. Monitor progress while you keep working. Search what's already indexed while the rest catches up.
Opt-out by default All projects are indexed automatically. Exclude the ones you don't want. No registration needed.
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

bash

# 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

bash

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

Alternative: global install (faster startup, works offline)

Terminal

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:

Code

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:

Index -- index() scans all projects automatically, runs in background
Search -- ask anything about past conversations
Exclude (optional) -- hide noisy projects you don't care about

Tools

Tool	Purpose
`manage_projects`	Exclude/include projects from indexing (opt-out model)
`index`	Start background indexing. All non-excluded projects. Modes: `incremental` (default), `rebuild`, `cancel`
`status`	Check indexing progress, ETA, skip reasons, DB health
`search`	Semantic + keyword search across conversations
`get_context`	Expand search results with surrounding conversation
`list_sessions`	Browse indexed sessions by project

Why This Exists

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?"

How It Works

Code

~/.claude/projects/*/*.jsonl     ~/.codex/sessions/YYYY/MM/DD/rollout-*.jsonl
        \                                       /
         \                                     /
          JSONL Parser (Claude Code + Codex formats, 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)

Codex sessions are grouped by cwd extracted from each file's session_meta line and surfaced as codex-<path> virtual projects in the index.

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

Config: Project exclusions stored in ~/.lore/config.json.

Configuration

Environment Variables

Variable	Default	Description
`LORE_DIR`	`~/.lore`	Data directory
`LORE_DB`	`~/.lore/lore.db`	Database path
`CLAUDE_PROJECTS_DIR`	`~/.claude/projects`	Claude Code transcripts location
`CODEX_SESSIONS_DIR`	`~/.codex/sessions`	OpenAI Codex CLI rollouts location

Performance

Measured on Apple Silicon (M-series):

Metric	Value
Search latency	20-30ms
Index speed	~10 sessions/sec
First search (cold model load)	~5s
DB size	~0.1MB per 10 sessions
Model size (downloaded once)	~112MB

Troubleshooting

"No sessions found"

Run manage_projects with action list to see available projects. All are indexed by default unless excluded.

Stale lock file

If indexing was interrupted, the lock file auto-cleans on next run (PID-based detection).

DB corruption

Delete ~/.lore/lore.db and re-index. Your source data (~/.claude/projects/) is never modified.

Development

bash

git clone https://github.com/hyunjae-labs/lore.git
cd lore
npm install
npm run build
npm test          # 135 tests

Tech Stack

Model Context Protocol SDK -- stdio transport
@huggingface/transformers -- multilingual-e5-small (INT8)
better-sqlite3 + sqlite-vec -- embedded vector DB
Reciprocal Rank Fusion -- hybrid search ranking

License

MIT

Read the full README →View source on GitHub →

Related MCP Servers

View all in Knowledge & Memory View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

npm downloads

294

Package downloads in the last 30 days.

Last commit

4mo ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Lore

It indexes Claude Code files from ~/.claude/projects/ and OpenAI Codex CLI sessions from ~/.codex/sessions/.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/hyunjae-labs-lore?style=directory)](https://allmcps.com/mcp/hyunjae-labs-lore)

HTML Embed

<a href="https://allmcps.com/mcp/hyunjae-labs-lore"><img src="https://allmcps.com/api/badge/hyunjae-labs-lore?style=directory" alt="Lore on AllMCPs" /></a>

Technical Specs & Signals

CategoryKnowledge & Memory

PricingFree

11/11 checks healthy over the last 33d

56Quality signal: Good · 56/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools27/30

Adoption & activity5/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 27d ago via OSV.dev · getlore (npm)

★ Featured

Moxie Docs MCP

MCP & Agent Skills for Automated Documentation, and codebase conventions + context

Explore Server →

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🧠 Knowledge & Memory →Best MCP servers for Memory & Knowledge →Alternatives to Lore →Install in Claude Desktop Install in Cursor Install in VS Code