Memory Box MCP Server
Related Servers
Alternatives to Memory Box MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.41MIT
- AlicenseNot gradedqualityBmaintenanceProvides persistent semantic memory for AI agents via MCP, enabling them to remember, recall, list, update, and forget memories with vector-based similarity search.ISC
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to store and semantically retrieve durable memories across sessions via MCP or REST, with tools for remembering, recalling, asking, updating, and forgetting memories.12 npmMIT
- AlicenseCqualityBmaintenancePersistent semantic memory for MCP-compatible agents, enabling them to remember and recall text, audio, and documents across sessions.1069 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to store, retrieve, and manage persistent memories locally via an MCP server with hybrid vector and keyword search, plus tools for memory CRUD, search, backup, and import.MIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that provides a personal semantic memory layer for AI tools. It enables storing, searching, and managing memories using hybrid vector and keyword search, allowing AI assistants to recall information by meaning.MIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose with no significant overlap. Tools target specific actions on distinct resources like memories, buckets, or system status, making it easy for an agent to select the right one. For example, get_all_memories vs. get_bucket_memories vs. search_memories are well-differentiated by scope and method.
All tool names follow a consistent verb_noun pattern using snake_case, such as create_bucket, delete_memory, and get_usage_stats. This uniformity makes the set predictable and easy to parse, with no deviations in style or convention across the 12 tools.
With 12 tools, the server is well-scoped for a memory management system, covering core operations without bloat. Each tool earns its place by addressing key needs like CRUD for memories and buckets, organization, search, and system monitoring, fitting typical expectations for such a domain.
The tool surface provides complete CRUD and lifecycle coverage for memories and buckets, including create, read, update, delete, search, and organization features. No obvious gaps exist; agents can perform all essential workflows from saving and retrieving memories to managing buckets and checking status.