Claude Find vs Memocall — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Claude Find vs Memocall
In-depth architectural comparison of the Claude Find and Memocall 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
Memocall
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 Memocall 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.
Recall past Claude Code conversations from any project. Lists and searches your sessions, then loads one on demand as clean, compact Markdown — with outline, turn-range, and in-session search for large sessions. Read-only over local /.claude transcripts; collapses tool calls to stay under the context cap. npx -y memocall
Category & Scope
Tools & Capabilities Breakdown
Claude Find Tools (6)
Indexes raw JSONL session transcripts from Claude Code
Uses GPU-accelerated qwen3 embeddings via Ollama
Hybrid semantic and keyword search with Reciprocal Rank Fusion
Includes metadata like project, branch, files, and dates
Background indexing with immediate searchable results
Disables session cleanup for permanent history retention
Memocall Tools (5)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Claude Find is categorized under Knowledge & Memory and uses a local stdio subprocess. In contrast, Memocall belongs to Knowledge & Memory using local stdio subprocess. Select Claude Find when you need capabilities focused on knowledge & memory and Memocall when you require tools for knowledge & memory.
List your recent Claude Code conversations across ALL projects, grouped by project directory. Use this to answer 'what sessions have I worked on recently?' or to find a past session before loading it. Returns each session's title, date, turn count, and id.
search_sessions
Search your past Claude Code conversations (across all projects) by keyword — matches session titles, first messages, and project paths. Use when the user refers to a past conversation by topic (e.g. 'the session where we set up the license system'). Returns matching sessions with their ids.
load_session
Load the context of a past Claude Code conversation as compact Markdown (human turns, collapsed tool-call summaries, and assistant replies — tool outputs are elided). Provide either a session `id` (from list_sessions/search_sessions) or a free-text `query` to find it. Use this to pull a previous conversation's context into the current session. For a very large session, either pass `turns` to load a specific window (turn numbers come from session_outline), or prefer session_outline / search_in_session.
session_outline
Get a quick MAP of a past Claude Code conversation: the numbered list of the user's prompts, one line each. Very cheap even for huge sessions. Use this to see what a session covered, or to find which turn numbers to then load with load_session's `turns`. Identify the session by `id` or free-text `query`.
search_in_session
Find specific turns WITHIN one past Claude Code conversation by keyword — returns only the matching turns (with their turn numbers). Use when the user asks what was decided or discussed about a topic inside a known or large session (e.g. 'what did we decide about retries in that session'). Pick the session by `id` or `session` (free-text); `query` is the keyword to find inside it.