agentmem
Related Servers
Alternatives to agentmem
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceDurable, local-first memory for AI coding agents over MCP — zero-dependency (pure Python + SQLite/FTS5), curated and semantically de-duped. Works with Claude Code, Codex and any MCP host, and you own the data as plain rows.654 PyPI21AGPL 3.0
- AlicenseNot gradedqualityDmaintenancePersistent memory for AI coding agents with local-first, zero-cost, privacy-first SQLite/FTS5 storage and biological-inspired decay.14 npm3MIT
- AlicenseNot gradedqualityBmaintenanceLocal-first memory for your AI agent. One SQLite file you own — offline, no API key. Plugs straight into Claude Code.Apache 2.0
- AlicenseAqualityCmaintenancePersistent 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.16235 npm5AGPL 3.0
- AlicenseAqualityBmaintenanceLocal-first, source-traceable memory for AI agents — no LLM at ingest, $0 per message, zero data egress. Gives Claude Code, Cursor, and any MCP client one shared persistent memory with semantic recall, belief revision, selective forgetting, and a provenance guard that blocks acting on stale or unconfirmed memories.2350 PyPI14MIT
- AlicenseAqualityAmaintenanceLocal-first memory for AI coding agents using SQLite, enabling persistent recall of decisions, lessons, and project context without cloud or API keys.10140 PyPI280Apache 2.0
TDQS
Scored across 13 tools
Each tool has a clearly distinct purpose with no overlap: add, delete, deprecate, list, load_session, conflicts, health, promote, recall, save_session, search, supersede, and update all target specific memory management operations. Descriptions clarify unique use cases, such as delete_memory for errors vs. deprecate_memory for outdated facts, preventing misselection.
Tool names follow a consistent verb_noun pattern throughout (e.g., add_memory, delete_memory, recall_memory), with all 13 tools using snake_case and clear action verbs. The only minor deviation is load_session/save_session, which still fits the pattern by targeting 'session' as the noun, maintaining readability and predictability.
With 13 tools, the count is well-scoped for a memory management system, covering essential operations like CRUD, search, recall, health checks, and session handling. Each tool earns its place without redundancy, aligning with the server's purpose to manage memories comprehensively.
The tool surface provides complete CRUD/lifecycle coverage for memory management: add, update, delete, deprecate, supersede, list, search, and recall cover core operations, while promote, conflicts, health, and session tools handle advanced workflows. No obvious gaps exist, ensuring agents can perform all necessary tasks without dead ends.