Skip to main content
Glama
Sign In
deenesjakoruzh
claude-find

claude-find

by Cavinooo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

claude-find

Pull deep memory from across your Claude Code sessions — when you need it.

demo

Semantic search over all your past Claude Code sessions. Finds context by meaning and keywords. Searches the raw conversation transcripts, not compressed summaries, so Claude gets the full picture: reasoning, constraints, failed approaches, and decisions.

Setup

brew install bun ollama
bunx claude-find setup

setup starts Ollama, pulls the embedding model, sets session retention to permanent, and registers the MCP server with Claude Code. Sessions are indexed in the background on startup. Searches work immediately and return progressively more complete results as indexing continues.

Install Bun and Ollama, then run bunx claude-find setup. It detects your platform and guides you through anything missing.

Related MCP server: Central Brain

Use it

In any Claude Code session:

/find that database migration we discussed last week
/find why we chose websockets over polling
/find the session where we kept getting timeout errors
/find refactoring the payment module across all projects

Claude searches your past sessions semantically, finds the relevant conversations, and synthesizes the context: what was tried, what failed, what constraints you set, and what decisions were made.

How it works

  1. Indexes all Claude Code session JSONL files from ~/.claude/projects/

  2. Extracts user + assistant messages, compact summaries, file paths from tool calls

  3. Enriches each chunk with metadata context (project, branch, files, date) for better retrieval

  4. Embeds conversation chunks using qwen3-embedding via Ollama (GPU accelerated)

  5. Searches with hybrid semantic + keyword (FTS5) merged via Reciprocal Rank Fusion

  6. Returns raw conversation chunks so Claude can synthesize with full context

After upgrading, run bunx claude-find index to rebuild the index with the latest improvements.

What makes this different

  • Searches raw transcripts. Nothing lost through compression.

  • Retroactive: works on all existing sessions immediately. No hooks needed.

  • Permanent history: setup disables Claude Code's 30-day session cleanup so your sessions are searchable forever.

  • Non-blocking: indexes in the background at startup. Searches work instantly, even mid-indexing.

  • Uses compact summaries: Claude's own session understanding, boosted in ranking.

  • Indexes tool call metadata: search by files touched, errors encountered.

  • Fast: Ollama + GPU keeps indexing fast and memory bounded.

Requirements

  • Bun runtime

  • Ollama (model auto-downloaded on first use)

  • Claude Code

License

MIT

Available Tools

1 tool
search_sessionsA

Search the full conversation history from past Claude Code sessions stored in ~/.claude/projects/. This tool has access to the complete raw transcripts of all previous sessions — including the actual back-and-forth discussion, reasoning, failed approaches, user constraints, and code decisions. Use this tool FIRST whenever the user mentions anything from a past session, asks 'what did we discuss', 'pull in context from', 'remember when we', 'how did we handle', or references any prior work. This tool searches semantically — the user doesn't need to remember exact words. Much more detailed than built-in memory.

Inputs: query (required), max_sessions, max_chunks, scope, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A4.4/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly defined.

    Naming Consistency5/5

    The single tool name 'search_sessions' follows a consistent verb_noun pattern, though there are no other tools to compare against.

    Tool Count3/5

    A single tool for searching is borderline thin; most servers of this scope would benefit from at least 2-3 tools (e.g., list_sessions, get_session). The count is at the low end of reasonable.

    Completeness4/5

    The tool covers the core search functionality well, but lacks complementary tools such as listing available sessions or retrieving full transcripts by ID, which would make the surface more complete.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • mcp-session-insight

      ArtLjn
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to query and analyze past Claude Code sessions, providing structured insights like file changes, decisions, errors, and git history across projects.
      11
      21 npm
      1
      MIT

    • context-bridge

      zachvp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude Code to search and retrieve past chat history from Claude.ai exports and Claude Code sessions, allowing the AI to reference previous conversations and decisions.
      MIT

    • cc-history

      Straska7
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides local-first, cross-session memory for Claude Code, enabling semantic search across past sessions to retrieve procedures, decisions, or answers without exposing secrets.
      Apache 2.0