Skip to main content
Glama

Related Servers

Alternatives to MemCore

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Provides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.
      52
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Provides persistent cross-session memory and full-text search for AI coding assistants, storing project context, decisions, and preferences while enabling searchable access to conversation history via local SQLite.
      8
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      A lightweight, local memory server for AI coding assistants that stores durable knowledge (decisions, facts, gotchas) in a tree structure, enabling persistent context across sessions with efficient retrieval via summaries and FTS5 search.
      9
      4
      -

    TDQS

    A4.6/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct axis: content search, exact-key fetch, browsing by scope/type, time-ordered recents, audit events, version history, semantic status, healthcheck, and lifecycle mutations. The descriptions explicitly cross-reference nearby tools and state when to use one instead of another, so an agent can reliably select the right tool.

    Naming Consistency4/5

    All names use the consistent `memory_` prefix and snake_case, making the family easy to scan. However, suffixes mix verbs (`search`, `get`, `write`, `archive`) with nouns/adjectives (`stats`, `recent`, `events`, `scopes`, `history`, `healthcheck`), so the verb_noun pattern is not fully uniform.

    Tool Count5/5

    Thirteen tools is well within the appropriate range for a memory store with search, scopes, audit history, versioning, archive/restore, and health checks. Each tool earns its place by covering a distinct operation rather than duplicating functionality.

    Completeness5/5

    The lifecycle is fully covered: create/update via `memory_write`, read via search/get/list/recent, soft-delete via archive, restore, audit events, prior-version history, scope discovery, stats, semantic embedding status, and end-to-end healthcheck. The absence of hard delete is intentional and explained, not a dead end.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data