Skip to main content
Glama

Related Servers

Alternatives to shared-memory

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Self-hosted semantic memory for AI agents. Save worklogs, decisions, and notes via MCP, then recall them across sessions by meaning rather than keyword. Backed by Postgres + pgvector with local embeddings (multilingual-e5-base).
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A portable self-hosted memory layer for AI tools, storing context, memories, and handoffs for access from any MCP-compatible client.
      15 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Persistent, searchable memory for AI agents over the Model Context Protocol, enabling memory storage, full-text search with BM25 ranking, and retrieval across sessions.
      6 npm
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Free, persistent memory layer for AI agents, enabling storage and semantic search of memories via MCP or REST.
      -

    TDQS

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle operation on a single resource: add, search, update, forget, stats. There is no meaningful overlap — search retrieves, stats aggregates, and the write operations are cleanly separated.

    Naming Consistency5/5

    All five tools follow a strict memory_<verb> snake_case pattern with clear, conventional verbs (add, search, update, forget, stats). No mixed conventions or vague names.

    Tool Count5/5

    Five tools is a tight, well-scoped surface for a memory store: write, read, mutate, delete, and observe. Every tool earns its place with no redundancy or filler.

    Completeness4/5

    The set covers the full CRUD lifecycle plus stats, and search likely substitutes for a direct get-by-id. Minor gaps remain around bulk operations and explicit id-based retrieval, but core workflows are covered without dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive