cognee-mcp
Related Servers
Alternatives to cognee-mcp
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityDmaintenancePersistent AI memory server with hybrid search and embedded sync. Enables AI agents to store, retrieve, and manage information across sessions with temporal knowledge graph support.MIT- FlicenseNot gradedqualityCmaintenanceProvides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.-
- AlicenseNot gradedqualityDmaintenanceProvides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.MIT
- FlicenseNot gradedqualityFmaintenanceEnables LLMs to store, search, and manage memories with hybrid semantic and keyword search using ChromaDB and Neo4j for persistent memory and knowledge graph capabilities.-
- AlicenseNot gradedqualityAmaintenancePersistent knowledge memory layer for AI agents. Hybrid semantic + full-text search with pgvector, code dependency graph with blast-radius impact analysis, and incremental indexing for 7 languages. In-process ONNX embeddings, no external API required.31 npm35MIT
- AlicenseAqualityBmaintenanceEnables AI agents to store, retrieve, and connect information in a Neo4j graph database as persistent memory, with semantic relationships, natural language search, and temporal tracking across conversations.9106 npm69MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: remember stores, forget deletes, recall searches, call_tool executes, and search_tools finds tools. No overlap or ambiguity exists between them.
Tool names mostly follow a verb pattern, but three are single verbs (remember, forget, recall) while two are verb_noun compounds (call_tool, search_tools). This is a minor inconsistency but still predictable and readable.
Five tools is well within the ideal 3-15 range, and each tool earns its place for a memory management server, covering core operations without excess.
The tool surface covers the full memory lifecycle: ingestion (remember), retrieval (recall), and deletion (forget), plus tool discovery and execution for extensibility. No obvious gaps for the stated purpose.