MemoryShield+ Agent Plugin
Related Servers
Alternatives to MemoryShield+ Agent Plugin
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to persist, retrieve, and share source-linked memory across sessions via MCP tools, backed by PostgreSQL with project/session management, decision tracking, keyword search, and cross-host context handoff.Apache 2.0
- AlicenseAqualityDmaintenanceProvides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.41MIT
- AlicenseAqualityCmaintenanceEnables AI agents to persist memory across sessions through MCP, supporting semantic retrieval, source-backed context, knowledge graph relationships, supersession lineage, and topic digests.431MIT
- AlicenseNot gradedqualityBmaintenanceProvides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.3MIT
- AlicenseCqualityCmaintenancePersistent semantic memory for MCP-compatible agents, enabling them to remember and recall text, audio, and documents across sessions.1055 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to maintain persistent memory across sessions by capturing conversations, extracting durable knowledge, and injecting relevant context, supporting various MCP-compatible platforms.12MIT
TDQS
Scored across 3 tools
Write (remember), read (recall), and health/diagnostic (status) are cleanly separated with no overlap in intent or data flow. An agent can decide unambiguously which tool to call for a given need, and the descriptions reinforce the read-vs-write boundary.
All three tools use a single snake_case pattern with a consistent `memoryshield_` namespace prefix followed by a short, intention-revealing token. There is no mixing of casing or verb styles across the set.
Three tools are well-scoped for a memory plugin and each earns its place; nothing is redundant. It is on the lean side, since a delete/forget operation would plausibly be a fourth peer tool rather than an omission.
The store/retrieve/diagnose core is covered, but the memory lifecycle is incomplete: there is no way to delete, update, or supersede stored messages, and no listing or inventory operation beyond semantic recall. For a persistent user-memory surface, missing deletion is a notable gap that agents cannot work around.