Memory MCP
Related Servers
Alternatives to Memory MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceAn MCP server that stores project memory in Supabase, allowing AI tools to persist context, notes, and decisions across sessions. Enables Claude Code, Codex, and similar assistants to maintain long-term project continuity through persistent memory storage.2MIT
- AlicenseBqualityAmaintenancePersistent, local memory for AI coding agents that learns how you work, not just what you said. Supports Claude Code, Codex CLI, Cursor, and any MCP client.7467MIT
- AlicenseAqualityAmaintenancePersistent memory for AI coding agents, storing decisions, bug fixes, conventions, and discoveries in a local SQLite database and automatically recalling them when relevant. Works with Claude Code, Codex, Cursor, Gemini CLI, and other MCP-compatible agents.222MIT
- AlicenseNot gradedqualityCmaintenancePersistent memory for AI coding agents. Enables agents to save and recall decisions, patterns, bugs, and context across sessions via an MCP server with local SQLite storage.4 npm2MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to maintain persistent, cross-session memory of codebase architecture, naming conventions, and decisions through MCP tools. Eliminates repetitive project re-explanation by automatically injecting stored context into every session with local-first SQLite storage and optional team sharing capabilities.4MIT
- AlicenseAqualityCmaintenancePersistent cloud memory for AI coding assistants. 28 MCP tools for semantic search, auto-learning, task tracking, correction patterns, knowledge graphs, and session replay across Claude Code, Cursor, Windsurf, Cline, and any MCP client. Encrypted at rest. Team shared memory with author attribution.35415 npm7MIT
TDQS
Scored across 22 tools
Most tools are clearly distinct, but 'resolve_project' and 'create_project' have overlapping functionality (resolve auto-creates), and several save tools (capture_project_memory, save_file_memory, etc.) could be confused without reading descriptions.
All tool names follow a consistent verb_noun pattern with underscores, using clear Spanish verbs and nouns. No mixing of conventions or unclear abbreviations.
22 tools is on the high end of the acceptable range. Each tool has a defined purpose, but the count feels slightly heavy for a memory management system. Could be streamlined by merging some similar save functions.
Covers core operations: create/list/resume projects, session management, memory storage, search, import/export, and warnings. Minor gaps: no explicit delete or update tools for projects or memory items, but the existing tools cover most workflows.