agent-memory-mcp
Related Servers
Alternatives to agent-memory-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceA local MCP memory server for AI agents to manage memory with evidence-backed, versioned mutations, using SQLite with FTS5 for storage and search.6Apache 2.0
- AlicenseNot gradedqualityCmaintenanceAn MCP server that provides persistent long-term memory for AI agents via local SQLite storage with low token overhead, enabling memory storage, retrieval, and management across sessions.1MIT
- AlicenseNot gradedqualityAmaintenanceA local memory server for AI agents that stores and retrieves information via MCP, keeping all data in SQLite on your machine.225 PyPI1Apache 2.0
- AlicenseNot gradedqualityDmaintenanceMCP server providing persistent memory management for AI agents using SQLite and FTS5, enabling storage, full-text search, and recall of memories with namespace isolation.1MIT
- AlicenseAqualityBmaintenanceMCP server for persistent, cross-session, local-first memory for AI agents, storing memories as Markdown files with SQLite indexing for hybrid search.24Apache 2.0
- AlicenseAqualityCmaintenanceA local-first MCP server for durable agent memory using SQLite and FTS5, enabling knowledge graph storage, search, and recall for AI agents.201MIT
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: memory_feedback for rating usefulness, memory_recall for retrieving memories, memory_stats for analytics, and memory_store for creating new memories. There is no overlap or ambiguity in their functions.
All tool names follow a consistent 'memory_' prefix with a descriptive suffix (feedback, recall, stats, store), using snake_case uniformly. This pattern is predictable and enhances readability.
With 4 tools, the server is well-scoped for managing agent memory, covering core operations like storing, recalling, providing feedback, and viewing statistics. Each tool earns its place without being excessive or insufficient.
The tool set provides complete CRUD-like coverage for the memory domain: store (create), recall (read), feedback (update/rate), and stats (monitor). There are no obvious gaps, supporting a full lifecycle from storage to decay management.