session-recall
Related Servers
Alternatives to session-recall
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides 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
- AlicenseNot gradedqualityDmaintenanceLocal memory search for Codex and Claude Code conversations. It keeps history on your machine, builds a local graph index, and returns compact evidence from past sessions.5MIT
- FlicenseNot gradedqualityBmaintenanceLocal semantic search over Claude Code sessions and shell command history, exposed to Claude Code as an MCP tool. Everything is indexed into one vector space and runs entirely on your machine.2-
- AlicenseNot gradedqualityCmaintenanceEnables searching and retrieving Claude Code conversation history via hybrid semantic and keyword search, allowing the agent to access its own past interactions.4MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to search and retrieve past coding-tool conversations across Claude Code, Claude Desktop, Codex, and Cursor through a local, read-only index.1MIT
- AlicenseAqualityDmaintenanceSemantic search across Claude Code conversations. Hybrid vector + keyword search, fully local, background indexing.625 npm8MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: expand_around navigates near an anchor, grep does substring search, recall_search performs semantic search, recent_sessions lists sessions, and step moves between turns. No overlap that would cause confusion.
Most names follow a verb_noun pattern (expand_around, recall_search, recent_sessions), but grep and step are single-word names that break the pattern. Still, they are clear and not mixed conventions like camelCase.
5 tools is well-scoped for a session recall server. It provides search, listing, and navigation without being overwhelming or too sparse.
The tool surface covers core needs (search, list, navigate) but lacks a direct way to fetch a specific session's full transcript by ID. This is a minor gap that agents can work around using recent_sessions and expand_around.