Skip to main content
Glama

Related Servers

Alternatives to StremAI

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides persistent cognitive memory for AI coding agents, enabling them to recall architecture decisions, coding preferences, and project facts across sessions.
      817 PyPI
      66
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Persistent 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.
      16
      235 npm
      5
      AGPL 3.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.
      19 npm
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides 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 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Helps AI coding agents remember what they learn across sessions by storing and retrieving atomic learnings, enabling persistent memory for AI tools.
      9 npm
      1
      MIT

    TDQS

    A3.9/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Nine tools is well-scoped for a memory-management server. Each tool maps to a real user need without redundancy or bloat.

    Completeness4/5

    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.

    Maintenance

    ActivitySlowing
    ResponsivenessUnresponsive