amem
Related Servers
Alternatives to amem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10157 PyPI286Apache 2.0
- AlicenseNot gradedqualityCmaintenanceGives AI coding agents persistent memory by storing observations, decisions, and learnings in a local SQLite database with vector search, full-text search, and a rules engine.4MIT
- FlicenseNot gradedqualityAmaintenanceProvides a local-first persistent memory layer that lets AI coding agents store, recall, and semantically search project-specific and cross-project knowledge across sessions, so context, decisions, and guidelines survive between conversations. Runs entirely on the user's machine with SQLite and no API keys, and optionally supports autonomous task-queue execution built on the same memory.-
- FlicenseNot gradedqualityAmaintenanceProvides a local-first, cross-session memory layer that lets AI coding agents store and semantically search per-project decisions, preferences, error patterns, and research alongside global guidelines. Also supports an optional task queue for autonomous execution, all backed by on-disk SQLite with no API keys or external calls.-
- FlicenseNot gradedqualityAmaintenanceEnables AI coding agents to store, search, and recall persistent project-specific and cross-project context — decisions, preferences, error patterns, and guidelines — from a local-first SQLite memory store with semantic search, so knowledge survives across sessions. An optional companion task server lets agents queue and autonomously execute work using that same memory.-
- FlicenseNot gradedqualityAmaintenanceGives AI coding agents a local-first persistent memory they can read and write directly during sessions, storing decisions, preferences, error patterns, and guidelines in per-project and global SQLite stores. Enables semantic and keyword retrieval of relevant context across sessions so agents start work already knowing a codebase's conventions and history.-
TDQS
Scored across 16 tools
Most tools target distinct actions or resources: memory retrieval, remembering, superseding, skills, tasks, and usage reporting are clearly separated. A few boundaries are softer, especially amem_context vs amem_graph vs amem_status and amem_stats vs amem_usage_report, but the descriptions largely clarify intended use.
All tools share the amem_ prefix and snake_case, which helps. However, naming conventions are mixed: some use resource_action (amem_skill_view, amem_task_add), some are bare verbs (amem_remember, amem_supersede), and others are nouns or noun phrases (amem_context, amem_repos, amem_usage_report).
At 16 tools, the set is slightly heavy but still within a reasonable range for a memory server with skills, tasks, inventory, and usage reporting. Each tool appears to have a real role, though some consolidation could make the surface lighter.
Core lifecycle operations are present: memory read/write/retire, skill list/view/save, task list/add/update/complete, and usage/stats reporting. Minor gaps exist around explicit deletion or unmonitoring, and skills/tasks lack full delete/update coverage, but most workflows are supported.