A
licenseNot graded
qualityC
maintenancePrivacy Agent Memory with best performance and security
34
MIT
knowmind
Related Servers
Alternatives to knowmind
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceLong-term Memory for AI. On Device. Secure. Coding tools, AI Agents. Instant Recall. Precise.-
- AlicenseAqualityDmaintenanceEnables AI agents with persistent semantic memory, including semantic recall, knowledge graphs, and instant domain expertise via pre-built Intelligence Packs.1027 npmMIT
- FlicenseNot gradedqualityBmaintenanceA long-term memory system built for AI Agents. Agent wakes up already knowing who he is, not querying "who am I?" every session. Every turn calling back accurate memory context. Achieving accurate memory hits while also preventing memory from expanding at scale. No compression, no forgetting.36-
- AlicenseAqualityAmaintenancePersistent AI agents memory for Claude, Codex, Cursor... that is always current.1229261 npm104Apache 2.0
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.535 npmMIT
TDQS
A4.3/5.0
Scored across 13 tools
Disambiguation5/5
Each tool has a clearly distinct purpose: recall vs recall_at_time, store_memory vs upload_document, link vs unlink, and entity vs schema are all separated with explicit use-case guidance. There is no real risk of an agent picking the wrong tool for a given action.
Naming Consistency4/5
Most tools follow a knowmind_<verb>_<object> pattern such as store_memory, upload_document, update_fact, and list_relations. Some tools are bare nouns or verbs (stats, health, entity, schema, recall, link, unlink), but the shared prefix and snake_case style keep the overall set predictable.
Tool Count5/5
13 tools is well within the ideal range for a knowledge-graph memory server. Each tool covers a distinct part of the workflow: ingestion, retrieval, fact supersession, graph construction, schema inspection, health checks, and statistics.
Completeness4/5
The core write/read/update graph workflows are well covered, including storing memories, uploading documents, recalling current and historical facts, and managing entities and relations. The main gap is the lack of explicit delete operations for memories, documents, or entities, though supersede, upsert, and unlink provide reasonable workarounds and deletion may be intentionally excluded for auditability.
Maintenance
ActivityActive
ResponsivenessNo issues