StremAI
Related Servers
Alternatives to StremAI
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceProvides long-term memory for AI coding agents, enabling facts like stack, conventions, and decisions to be recorded once and recalled across sessions.8344 npmMIT
- AlicenseNot gradedqualityAmaintenanceProvides persistent cognitive memory for AI coding agents, enabling them to recall architecture decisions, coding preferences, and project facts across sessions.817 PyPI66MIT
- 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
- AlicenseNot gradedqualityCmaintenanceProvides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.19 npm2MIT
- AlicenseNot gradedqualityAmaintenanceProvides shared long-term memory for AI coding agents via MCP, allowing tools like Claude Code and Codex to store and retrieve distilled facts, notes, and conversation history to persist context across sessions.26 npm3MIT
- AlicenseNot gradedqualityCmaintenanceHelps AI coding agents remember what they learn across sessions by storing and retrieving atomic learnings, enabling persistent memory for AI tools.9 npm1MIT
TDQS
Scored across 9 tools
Each tool targets a distinctly different action: storing, recalling, forgetting, verifying, inspecting health, compacting, signing up, capabilities introspection, and auth status. There is no meaningful overlap or ambiguity between them.
Most tools follow a clear agentbay_memory_<action> pattern, while signup, capabilities, and whoami diverge slightly by dropping the memory_ segment. The naming is still predictable and readable, but not perfectly uniform.
Nine tools is well-scoped for a memory-management server. Each tool maps to a real user need without redundancy or bloat.
The core memory lifecycle is covered: store, recall, forget, verify, health, and compact. A minor gap is the lack of an explicit update/edit operation for existing memory content, though verify partially addresses freshness.