recall
Related Servers
Alternatives to recall
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI coding agents to store and retrieve persistent, project-scoped memories as Markdown files keyed to a repository, so decisions, conventions, and gotchas carry over between sessions. Any MCP client can list, search, read, write, update, and delete memories, with Claude Code gaining automatic injection at session start and auto-capture at session end.66 npmPolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityBmaintenanceGives every MCP-capable AI agent a shared, local-first memory store, letting them save, search, update, and delete preferences, decisions, and facts kept as plain Markdown files versioned in git. Memories are ranked by relevance on recall and shared across Claude Code, Cursor, Codex, and any other MCP client.MIT
- AlicenseNot gradedqualityCmaintenancePersistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.1MIT
- AlicenseAqualityDmaintenanceGives Claude Code, Claude Desktop, Cursor, VS Code Copilot, and other MCP-compatible tools persistent memory.1848 npm1MIT
- AlicenseAqualityCmaintenanceEnables coding agents to keep durable long-term memory in a folder of human-readable Markdown notes: search and read notes by ranked recall, encode new ones, link related ideas, retire contradicted notes in favor of replacements, and re-validate them — all backed by a disposable SQLite index. Plugs into Claude Code, Claude Desktop, Cursor, or any MCP client.7MIT
- AlicenseNot gradedqualityAmaintenanceGives AI coding agents persistent, cross-session memory by storing task insights as interlinked markdown knowledge cards and recalling relevant ones before new work begins. Uses plain files and git sync instead of a vector database or embeddings, and exposes this through MCP tools for Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, and other clients.9 npmISC
This server cannot be deployed
TDQS
Scored across 4 tools
The four tools have mostly distinct roles: list the catalog, get one memory, recall a graph of linked memories, and surface stale memories. memory_get and memory_recall overlap slightly because both read named memories, but recall's link traversal and token budget distinguish it.
All tools use the same snake_case memory_ prefix and a short predictable action label. The pattern is consistent across list, get, recall, and due.
Four tools are well-scoped for a read-focused memory recall server. Each tool covers a distinct retrieval need without obvious padding.
The surface covers listing, full reading, linked recall, and freshness checks, which are the core recall workflows. Keyword/content search and memory write/update operations are absent, but those may be outside this server's stated scope.