SharedMemory MCP Server
OfficialRelated Servers
Alternatives to SharedMemory MCP Server
No user-submitted related servers found.
Related Servers
FlicenseNot gradedqualityDmaintenanceGives Claude Desktop, Cursor, Cline, and other MCP-compatible AI tools persistent memory, enabling them to store and recall information seamlessly across sessions.2 npm1-- AlicenseCqualityAmaintenancePersistent, 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.76758 PyPI70MIT
- AlicenseAqualityBmaintenancePersistent memory for Claude Code. Automatically indexes every conversation and provides production-grade hybrid search (BM25 + vectors + reranker) via MCP tools. 100% local, zero config, zero API keys, zero invoice.1634 npm7MIT
- 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
- AlicenseNot gradedqualityCmaintenanceLocal persistent memory for AI coding tools. Stores project context and conversation recall locally via MCP.2 npm14MIT
- AlicenseNot gradedqualityAmaintenancePersistent, local-first memory for your AI chats. Save context in one chat, load it in another — across Claude web, Claude Code, Cursor, Cline, and Claude Desktop. One store, on your own disk, reachable from every tool via MCP, CLI, REST, or SDK.1,095 npmApache 2.0
TDQS
Scored across 18 tools
Most tools have distinct purposes, but 'get_entity' and 'profile' are very similar in function, which could cause confusion. Descriptions help differentiate them, but the overlap is notable.
The predominant pattern is verb_noun lowercase with underscores, but 'profile' and 'decide' are verb-only outliers, breaking perfect consistency. Overall, the naming is still predictable.
18 tools cover a wide range of memory operations without being excessive. Each tool serves a clear, non-redundant role in storing, retrieving, managing, and deciding based on knowledge.
The tool surface covers CRUD, search, context assembly, and decision-making. Missing volume creation/deletion and advanced ability management, but the core memory workflows are well-served.