In-depth architectural comparison of the Claude Find and Acheron MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Claude Find
Knowledge & Memory · Local stdio
Quality: 43/100 (Fair) | Auth: No auth required
Acheron MCP Server
Knowledge & Memory · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Claude Find if you need specialized Knowledge & Memory tools running via a local process. Choose Acheron MCP Server if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Claude Find when:
You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: Indexes raw JSONL session transcripts from Claude Code, Uses GPU-accelerated qwen3 embeddings via Ollama, Hybrid semantic and keyword search with Reciprocal Rank Fusion.
Pull Deep Memory from across your Claude Code Sessions — when you need it.
Cross-surface persistent memory for Claude. Bridges context between Claude Chat, Code, and Cowork via local SQLite with full-text search. Save decisions, preferences, and insights in one surface, retrieve them in any other.
Claude Find is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Acheron MCP Server belongs to Knowledge & Memory using local stdio subprocess. Select Claude Find when you need capabilities focused on knowledge & memory and Acheron MCP Server when you require tools for knowledge & memory.
Remember something for later. Use this when the user says things like "remember this", "save this", "note this", "keep this for later", "don't forget", or when an important decision, preference, or insight comes up that should persist across conversations. This saves context that will be available in ALL Claude surfaces (Chat, Code, Cowork) — even in future sessions. Use proactively when you recognize something worth remembering: a decision made, a user preference expressed, a lesson learned, a key file identified, or a workflow established.
bridge_get_context
Retrieve the full details of a previously saved context by its ID. Use this after finding a context via search or list, when the user wants to see the complete content of a specific saved memory. Typically used as a follow-up: "show me that decision", "give me the full details on that one".
bridge_search_context
Search through everything that has been saved across conversations. Use when the user asks "what did I decide about...", "what do we know about...", "did I save anything about...", "find my notes on...", "what was that thing about...", or any question that might be answered by previously saved context. Also use proactively when the user asks a question that saved context might answer — check before saying "I don't have that information". Searches across all surfaces (Chat, Code, Cowork) and all projects.
bridge_list_contexts
Browse and filter all saved contexts. Use when the user asks "what have I saved?", "show me my decisions", "what do I have for this project?", "list my preferences", "what did we do recently?", "show everything tagged with...", or "what happened in Cowork?". Unlike search (keyword-based), this tool browses by category — filter by project, surface, type, tags, or date. Returns newest entries first.
bridge_delete_context
Permanently delete a saved context. Use when the user says "forget this", "delete that", "remove that note", "I don't need that anymore", or "that's outdated, remove it". Requires the context ID — use search or list first to find it.
bridge_status
Show a summary of all saved knowledge: how many contexts are stored, broken down by surface (Chat/Code/Cowork) and type (decisions, preferences, insights, etc.), database size, and date range. Use when the user asks "how much have I saved?", "give me an overview", "what's in my memory?", or "how big is my context database?".