Skip to main content
Glama
Sign In
StremAI

StremAI

by thomasjumper
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to StremAI

No user-submitted related servers found.

    Related Servers

    • iranti

      nfemmanuel
      A
      license
      A
      quality
      D
      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

    • amem

      amanasmuei
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent memory for AI coding tools, allowing them to remember corrections, decisions, and preferences across sessions and different tools.
      14 npm
      2
      MIT

    • LocalMCP

      al-mighty
      A
      license
      A
      quality
      C
      maintenance
      Enables coding agents to share a persistent local memory store across sessions and clients, saving, searching, updating, and retrieving facts, decisions, incidents, preferences, references, and snippets with semantic and lexical search.
      10
      MIT

    • memgw

      holetexvn
      A
      license
      Not graded
      quality
      C
      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.
      4 npm
      3
      MIT
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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

    ActivityNo data
    ResponsivenessOutdated data

    Resources