MCP.Market

Claude Find MCP server

by Cavinooo·io.github.Cavinooo/claude-find·v0.2.5·11 stars
No reviews yet

Pull Deep Memory from across your Claude Code Sessions — when you need it.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
New

11 stars

Reviews

Write one

Nobody has reviewed Claude Find yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Claude Find tools (1)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • search_sessions

    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',

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan11 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 109 days ago8/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Claude Find compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
1
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
11
more than 88% of 28,688 servers

What its tools let an agent do: 1 read

Install Claude Find in Claude Code, Cursor or VS Code

Runs npx -y claude-find on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add claude-find -- npx -y claude-find
Add to Cursor

What the publisher says

From the Claude Find repository's README, as published. We do not edit it. Read it on GitHub

claude-find

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

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.

Linux / Windows

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

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

Nothing above is checked by us. What we check is on the safety report.

Claude Find: common questions

Is Claude Find MCP server safe?
Mostly: it is graded B (82/100). Read the Claude Find safety report
How do I install Claude Find?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Claude Find need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Claude Find maintained?
The last commit was 147 days ago (2026-06-10). The latest release is v0.2.5.
What can I use instead of Claude Find?
Servers from other publishers that do the same job: Deja Vu MCP server.
How does Claude Find compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 1 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Claude Find

Same job from other publishers: the closest match first, then the best rated.

  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A