chat-search-mcp
v0.1.11
Published
MCP server for searching Claude Code and Codex CLI chat session histories.
Maintainers
Readme
RepoChatMCP
Search Claude Code and Codex chat history like source code.
RepoChatMCP is a zero-dependency MCP server and CLI for searching local Claude Code and Codex session files. It normalizes both providers into one message model, exposes search and read tools over MCP, and can optionally build a persisted repository knowledge index from your chat history.
No database. No background service. No telemetry. Just your local JSONL session files.
Why Use It
- Search Claude Code and Codex history from one MCP server
- Read sessions by message range or lines around a match
- Grep chats with AND, OR, and regex patterns
- Build repo knowledge summaries from prior chats
- Run locally with zero runtime dependencies
Package And Commands
- Published npm package:
chat-search-mcp - Installed CLI commands:
chat-searchandchat-search-mcp - Runtime requirement: Node.js 22+
Install
Use the published npm package
Install it first:
npm install -g chat-search-mcp@latestThen use it:
chat-search status --repo /path/to/repo
chat-search search "authentication" --repo /path/to/repoUse the local repo checkout
git clone https://github.com/gzmagyari/RepoChatMCP.git
cd RepoChatMCP
npm install
node ./bin/chat-search.js status --repo .Claude Code Setup
Project MCP from a local checkout
Use this when you cloned the repo and want Claude Code to run the local source directly:
{
"mcpServers": {
"chat-search": {
"type": "stdio",
"command": "node",
"args": ["./bin/chat-search.js"]
}
}
}Claude Code runs project MCPs from the repo directory, so ./bin/chat-search.js works and the current repo becomes the default target.
Use the published npm package
Install it first:
npm install -g chat-search-mcp@latestmacOS / Linux:
{
"mcpServers": {
"chat-search": {
"type": "stdio",
"command": "chat-search-mcp",
"args": ["mcp"]
}
}
}Windows:
{
"mcpServers": {
"chat-search": {
"type": "stdio",
"command": "cmd",
"args": ["/c", "chat-search-mcp", "mcp"]
}
}
}Codex Setup
Local checkout:
[mcp_servers.chat_search]
command = "node"
args = ["C:/path/to/RepoChatMCP/bin/chat-search.js"]Published npm package on Windows:
[mcp_servers.chat_search]
command = "cmd"
args = ["/c", "chat-search-mcp", "mcp"]CLI Quick Start
# MCP server
chat-search mcp --repo /path/to/repo
# Show discovered session counts
chat-search status --repo /path/to/repo
# Search across chats
chat-search search "jwt token" --repo /path/to/repoIf --repo is omitted, the current working directory is used.
MCP Tools
| Tool | What it does |
|---|---|
| chat.list_sessions | Lists discovered Claude Code and Codex sessions for the repo |
| chat.search | Full-text search with relevance scoring |
| chat.grep | Pattern search with |, &, and regex support |
| chat.read_session | Reads messages from a session by index range |
| chat.read_lines | Reads lines around a keyword or regex match |
| chat.compaction_knowledge | Returns metadata plus an absolute file path for live compaction knowledge |
| chat.start_knowledge_index | Starts async knowledge indexing and returns a job ID immediately |
| chat.get_knowledge_index_status | Returns progress, counts, and terminal state for a knowledge indexing job |
| chat.cancel_knowledge_index | Requests cancellation of a running knowledge indexing job |
| chat.list_knowledge_batches | Lists persisted knowledge batches with canonical combined artifact paths |
| chat.read_latest_knowledge | Reads paginated text from the latest persisted combined artifact |
| chat.read_knowledge_batch | Reads paginated text from one persisted batch artifact |
| chat.list_knowledge_files | Lists per-chunk persisted knowledge files for one batch |
| chat.read_knowledge_file | Reads paginated text from one persisted per-chunk knowledge file |
| chat.search_knowledge | Searches persisted knowledge artifacts directly |
Example tool inputs
{ "query": "database pooling", "provider": "claude", "limit": 5 }{ "pattern": "authentication&jwt" }{ "sessionId": "8ac646f8-1bec-...", "startIndex": 0, "endIndex": 50 }{ "force": true }{ "provider": "codex", "limit": 10, "query": "database" }{ "jobId": "knowledge-job-20260403-080000000-abc123def0" }{ "batchId": "20260403-080000000-abc123def0", "kind": "knowledge", "offset": 0, "limit": 120 }{ "query": "billing webhook", "kind": "content_summary", "limit": 5 }Optional Knowledge Indexing
Knowledge indexing is disabled by default.
When disabled:
chat.compaction_knowledgereturns a live compaction snapshot file pathchat.start_knowledge_indexreturns a configuration message instead of starting a job- persisted knowledge can still be read later if
.repochatmcp/knowledge/already exists
When enabled:
chat.start_knowledge_indexcreates an async indexing job instead of blocking the MCP callchat.get_knowledge_index_statusreports discovery counts, chunk progress, files written, and failureschat.read_latest_knowledgeandchat.read_knowledge_batchreturn actual paginated knowledge text, not just file pathschat.list_knowledge_files,chat.read_knowledge_file, andchat.search_knowledgelet agents inspect persisted chunk files directly- combined persisted batch artifacts are written under
.repochatmcp/knowledge/combined/ .repochatmcp/is automatically added to the repo root.gitignore
Stored files:
.repochatmcp/knowledge/manifest.json.repochatmcp/knowledge/jobs/*.json.repochatmcp/knowledge/runs/*.md.repochatmcp/knowledge/combined/*.md
Indexing rules:
- minimum 100 new or changed messages before indexing runs
- split only when transcript size exceeds
CHAT_SEARCH_KNOWLEDGE_MAX_CHARS - Codex chunk calls run sequentially
- HTTP chunk calls run with limited concurrency
- each chunk writes both a structured
knowledgefile and a plaincontent_summaryfile - combined batch artifacts are persisted so agents can read one canonical file per batch
Backends
off: disabledauto: prefer HTTP if API config is present, otherwise use Codex CLIhttp: OpenAI-compatible HTTP requestscodex: Codex CLI over stdin
MCP env config
{
"mcpServers": {
"chat-search": {
"type": "stdio",
"command": "cmd",
"args": ["/c", "chat-search-mcp", "mcp"],
"env": {
"CHAT_SEARCH_KNOWLEDGE_BACKEND": "http",
"CHAT_SEARCH_KNOWLEDGE_BASE_URL": "https://openrouter.ai/api/v1",
"CHAT_SEARCH_KNOWLEDGE_MODEL": "moonshotai/kimi-k2-0905@groq",
"CHAT_SEARCH_KNOWLEDGE_API_KEY": "your-api-key",
"CHAT_SEARCH_KNOWLEDGE_MAX_CHARS": "500000",
"CHAT_SEARCH_KNOWLEDGE_HTTP_CONCURRENCY": "3"
}
}
}
}Supported env vars:
CHAT_SEARCH_KNOWLEDGE_BACKEND=off|auto|http|codexCHAT_SEARCH_KNOWLEDGE_MODELCHAT_SEARCH_KNOWLEDGE_BASE_URLCHAT_SEARCH_KNOWLEDGE_API_KEYCHAT_SEARCH_KNOWLEDGE_MAX_CHARSCHAT_SEARCH_KNOWLEDGE_TIMEOUT_MSCHAT_SEARCH_KNOWLEDGE_CODEX_BINCHAT_SEARCH_KNOWLEDGE_HTTP_CONCURRENCY
OpenRouter provider pinning:
- set
CHAT_SEARCH_KNOWLEDGE_BASE_URL=https://openrouter.ai/api/v1 - use
CHAT_SEARCH_KNOWLEDGE_MODEL=model@provider, for examplemoonshotai/kimi-k2-0905@groq @provideris only valid for the OpenRouter HTTP backend
Unified Message Model
Both Claude Code and Codex are normalized to:
{
provider: "claude" | "codex",
sessionId: "uuid-or-session-id",
index: 42,
timestamp: "2026-03-25T10:11:12.000Z",
type: "user" | "assistant" | "tool_call" | "tool_result" | "system" | "compaction",
role: "user" | "assistant" | "system" | "developer",
text: "message text"
}Where Sessions Are Read From
Claude Code:
~/.claude/projects/<encoded-repo-path>/*.jsonl
Codex:
~/.codex/sessions/<year>/<month>/<day>/*.jsonl~/.codex/archived_sessions/...
Configurable roots:
CHAT_SEARCH_CLAUDE_ROOTCHAT_SEARCH_CODEX_SESSIONSCHAT_SEARCH_CODEX_ARCHIVED
Development
npm testCurrent test suite: 79 tests covering discovery, normalization, search, MCP transport, async knowledge indexing jobs, direct persisted knowledge reads, and persisted knowledge indexing.
License
MIT
