agent-knowledge
Related Servers
Alternatives to agent-knowledge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceLong-term memory for AI agents over MCP — episodic + semantic memory, a temporal knowledge graph, and a dialectic user model, exposed as 32 tools (recall, remember, context, graph, dreaming, peers). Zero dependencies, runs fully offline; leads the LoCoMo benchmark at ~35x fewer LLM calls.2Apache 2.0
- AlicenseAqualityAmaintenancePersistent shared memory for AI coding agents. Stores facts as entity/key/value triples with hybrid semantic search, task checkpoints, and conflict resolution — shared across Claude Code, Codex CLI, and GitHub Copilot.162355AGPL 3.0
- AlicenseAqualityAmaintenanceAssociative key-graph memory for LLM agents — recall facts by association (recall → read_key → read_memory) instead of vector similarity alone, with persistent cross-session memory and cross-lingual keys.111,6723MIT

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.1412MIT- AlicenseNot gradedqualityAmaintenanceLocal memory for AI agents in one SQLite file on your own machine. Facts carry a validity window and a confidence score, so an outdated one is superseded and downweighted rather than deleted, and retrieval fuses BM25, vector similarity and a knowledge graph.3MIT
- AlicenseAqualityBmaintenanceEnables AI agents to record, recall, correct, and forget evidence-backed factual claims with temporal history, while explaining whether remembered information is current, historical, or contested.5Apache 2.0
TDQS
Scored across 8 tools
Each tool has a clearly distinct purpose: querying, ingesting text, ingesting UMSF documents, stats, dreaming, hook operations, and hook stats. The two ingest tools are differentiated by input type and use case, and the hook tools are a cohesive subset with clear roles.
All tools share the 'ak_' prefix and use snake_case, but patterns vary slightly: some are action-only (query, ingest, stats, dream), while others include a context prefix (ingest_umsf, hook_fire, hook_list, hook_stats). This is readable and predictable, with minor inconsistency in noun/verb ordering.
With 8 tools, the set is well-scoped for a knowledge vault server. Each tool covers a distinct aspect—query, ingestion, usage stats, memory consolidation, and hook management—without unnecessary bloat or missing core functionality.
The core knowledge vault operations (ingest, query, stats, dream) are covered, plus real-time hook management. Minor gaps include lack of explicit source deletion or listing, but these are not essential for the stated purpose and can be worked around.