A
licenseA
qualityA
maintenanceMemory manager for AI apps and Agents using various graph and vector stores and allowing ingestion from 30+ data sources
5
30,993
Apache 2.0
knowl
by dat999zx
Related Servers
Alternatives to knowl
- AlicenseBqualityAmaintenanceBasic Memory is a knowledge management system that allows you to build a persistent semantic graph from conversations with AI assistants. All knowledge is stored in standard Markdown files on your computer, giving you full control and ownership of your data. Integrates directly with Obsidan.md176,060 PyPI4,041AGPL 3.0
mem0-mcpofficial
AlicenseAqualityCmaintenanceSelf-hosted Mem0 MCP server integrating Qdrant, Neo4j, and Ollama for semantic memory search, graph entity relationships, and memory management via OpenMemory API.64MIT
Related Servers
- AlicenseAqualityAmaintenanceHosted memory for AI agents that learns from outcomes, with shared rooms. One key across Claude, Cursor & ChatGPT.611753 npm25MIT
- AlicenseNot gradedqualityDmaintenanceProvides long-term memory for AI coding agents, enabling them to remember, search, and organize information across sessions and platforms like Claude Code, ChatGPT, and Cursor.13 npm8MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI tools like Claude and Cursor to share persistent memory across sessions.5-
Xanther memory Engineofficial
AlicenseNot gradedqualityBmaintenancePersistent memory for AI coding assistants.3MIT- AlicenseNot gradedqualityAmaintenancePersistent memory for AI coding agents that knows when it has gone stale.3MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local long-term memory layer for AI coding tools like Cursor and Claude Code, enabling cross-session, cross-tool sharing of project facts, user preferences, decisions, and workflows.5 npm2MIT
TDQS
A3.8/5.0
Scored across 29 tools
Disambiguation4/5
Most tools have clearly distinct purposes, with detailed descriptions that separate query, store, state, context, and lifecycle operations. A few pairs (knowl_store vs knowl_ingest_atoms, knowl_handoff vs knowl_park) are conceptually close but differentiated by consumption semantics and use case.
Naming Consistency3/5
All tools share the knowl_ prefix and snake_case, but the pattern is mixed: some are bare verbs (knowl_query, knowl_store), some bare nouns (knowl_state, knowl_fleet), some noun_verb (knowl_skill_read, knowl_task_start), and one verb_noun (knowl_ingest_atoms). It is readable but not a coherent convention.
Tool Count2/5
At 29 tools, the surface exceeds the 25+ threshold that signals bloat. While the server covers many subdomains (skills, tasks, GC, fleet, drift), this many entry points places a heavy burden on agent selection and tool discovery.
Completeness5/5
The tool surface covers the memory lifecycle thoroughly: store, query, update, retire/supersede, evidence, conflicts, timeline, ingest, synthesize, sessions, tasks, GC, skills, handoff/park/resume, and fleet awareness. No significant operation appears missing for knowledge management.
Maintenance
ActivityActive
ResponsivenessResponsive