memocat-mcp
Related Servers
Alternatives to memocat-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides durable memory for AI agents with structured storage, semantic search, OAuth authentication, and lifecycle controls.11Apache 2.0

RushDB MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to gain persistent, structured memory that is semantically searchable and graph-traversable, allowing them to store and query records and relationships without managing embeddings or schemas.16 npmApache 2.0- AlicenseAqualityAmaintenanceProvides persistent, searchable memory for AI agents, enabling them to retain, recall, and reflect on information across conversations.1919 PyPI1MIT
- FlicenseNot gradedqualityBmaintenanceProvides AI agents with persistent, searchable long-term memory across sessions, enabling storage, full-text retrieval, updates, GDPR-compliant deletion, session summaries, and cross-referencing with per-namespace isolation.-
- FlicenseNot gradedqualityDmaintenanceProvides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.14-

Memsolus MCP Serverofficial
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.148 npmMIT
TDQS
Scored across 24 tools
Each tool has a clearly defined job, and the retrieval tools are explicitly differentiated: semantic_search for meaning, recall for exact key/filter lookup, and list_memories for browsing. The only mild ambiguity is among enable_semantic, enable_external_vectors, and reembed_semantic, but their descriptions make the embedding-source distinction clear enough.
All tools share the montycat_ prefix, and most follow a verb_noun pattern like create_keyspace, list_memories, or await_memory_change. A few noun-first names such as semantic_search, policy_view, and policy_history break the pattern slightly, but the naming is still predictable and readable overall.
24 tools sit at the heavy end of the scale and cover many subdomains: memory CRUD, semantic search, keyspace lifecycle, policy, snapshots, and engine installation. Each tool has a purpose, but the surface is larger than a typical memory server needs and may overwhelm agents choosing among many admin operations.
Core memory operations are well covered: create, recall, update, forget, bulk write, list, search, and live change notification. The main gap is snapshot management—start, stop, and clean exist, but there is no restore or snapshot listing tool—and there is no explicit store-level management beyond keyspaces.