Multi-Memory MCP Server
Related Servers
Alternatives to Multi-Memory MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA persistent memory server for AI agents that stores structured notes in a local SQLite database with full-text search and graph-based relationships. It features 32 specialized tools for managing long-term context, including version history, automated TTL expiration, and complex filtering.10 npmMIT
- AlicenseNot gradedqualityDmaintenanceA persistent memory server that implements a local knowledge graph using the Kuzu embedded database to store entities, relationships, and observations. It enables AI models to maintain structured long-term context through searchable nodes and comprehensive tag-based organization.8 npmMIT
- AlicenseNot gradedqualityBmaintenanceA lightweight, powerful local memory server for AI agents supporting text, entities, and relations. Enables persistent codebase understanding and user preference management.145 npm56MIT
- AlicenseNot gradedqualityDmaintenanceA privacy-focused local memory server that provides long-term semantic storage and retrieval for AI agents using SQLite and ChromaDB. It enables LLMs to persist and query text, chat histories, and PDF documents across sessions through the Model Context Protocol.MIT
- FlicenseAqualityCmaintenanceA lightweight, local memory server for AI coding assistants that stores durable knowledge (decisions, facts, gotchas) in a tree structure, enabling persistent context across sessions with efficient retrieval via summaries and FTS5 search.942 npm4-
- AlicenseNot gradedqualityDmaintenanceA lightweight server that provides persistent memory and context management for AI assistants using local vector storage and database, enabling efficient storage and retrieval of contextual information through semantic search and indexed retrieval.2MIT
TDQS
Scored across 11 tools
Each tool targets a specific resource or action: entities, relations, observations, categories, graph reading, and search. The deletion tools are clearly differentiated by object type (entities, observations, relations, categories). Retrieval tools (open_nodes, read_graph, search_nodes) serve distinct purposes.
All tool names follow a verb_noun pattern with lowercase and underscores (e.g., create_entities, delete_observations). However, the verbs vary: 'add' vs 'create' for creation, and 'open' is an unusual choice for retrieval, introducing slight inconsistency.
With 11 tools, the server covers the essential operations for managing a knowledge graph (CRUD for entities, relations, observations, plus categories, graph reading, and search). The count is well within the typical 3-15 range and feels appropriate for the domain.
The tools cover create, read, delete, and search operations, but lack update functionality for entities and relations (e.g., update_entity, update_relation). Also, categories can only be listed and deleted, not created or renamed. These gaps limit completeness.