Memory MCP
Related Servers
Alternatives to Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides Claude with a persistent local memory and structured knowledge graph to track project states, tasks, and historical decisions across different chat sessions. It enables users to recall information using keyword relevance, time-travel queries, and dependency analysis for complex project management.MIT
- FlicenseNot gradedqualityDmaintenanceProvides memory and project tracking for Claude Code via MCP, enabling semantic search over past transcripts, durable notes, and structured project management with milestones, epics, tickets, and todos.-
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client — Codex, Cursor, Gemini CLI, or a custom agent — to read and write Claude Code's per-project auto memory, retrieving linked Markdown memories within a token budget and optionally saving or deleting them. Keeps memories as plain files in Claude Code's own format, so multiple agents share one portable memory without vectors or a database.483 npm3MIT
- AlicenseNot gradedqualityDmaintenanceCross-project memory for Claude Code, enabling local semantic recall and secure, git-versioned markdown storage of reusable knowledge across repositories.MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent long-term memory and local RAG document search for Claude Desktop, fully offline. Enables memory save/search and document retrieval via MCP.MIT
- AlicenseAqualityCmaintenanceEnables AI assistants to maintain persistent project context across sessions by storing and retrieving structured information in markdown files organized in a memory bank directory.457Apache 2.0
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one stores information (memorize) and one retrieves information (recall). There is no overlap in functionality, and an agent would never confuse which tool to use for which operation.
Both tools follow the same verb_noun_tool pattern: memorize_memory_tool and recall_memory_tool. The naming is perfectly consistent with clear action verbs and matching structure throughout.
With only 2 tools, this server feels thin for a memory system. While memorize and recall cover basic operations, there are no tools for managing, organizing, updating, or deleting memories, which would be expected for a complete memory management system.
The tool surface is severely incomplete for a memory system. While it covers basic store and retrieve operations, there are no tools for updating existing memories, deleting memories, listing available memories, searching with filters, or managing memory organization. This creates significant gaps that will limit agent effectiveness.