Skip to main content
Glama
BrunoBanana

memory-as-history

by BrunoBanana

Related Servers

Alternatives to memory-as-history

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides a drop-in MCP memory server over stdio using a local SQLite store, enabling agents to store, search, and audit memory with provenance, scoped access, and contradiction tracking without requiring API keys, LLMs, or embedding providers.
      142 npm
      15
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP server providing persistent, layered memory (episodic, semantic, procedural, resource) for AI agents, with search, versioning, and session management via a single SQLite file.
      54 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local-first MCP memory server providing persistent, searchable memory for AI agents, powered by SQLite.
      1 npm
      1
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      A local MCP memory server for AI agents to manage memory with evidence-backed, versioned mutations, using SQLite with FTS5 for storage and search.
      6
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Persistent memory MCP server for AI agents, featuring a visual interface to browse, search, edit, and delete memory. It provides tools for capturing episodes, recalling, consolidating, crystallizing traits, and forgetting, with local SQLite storage and optional authenticated web UI.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      A SQLite-backed MCP memory server providing persistent memory storage with full-text search and knowledge graph capabilities for AI assistants.
      12
      9 npm
      MIT

    TDQS

    A3.9/5.0

    Scored across 15 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose: storage (remember), consolidation (promote), anchoring (pin/unpin), forgetting (forget/restore), retrieval (recall/search), narrative (narrate/current_narrative), evidence (corroborate/provenance), audit (audit_log), and queue (due_for_consolidation). No two tools overlap in function; even recall and search are differentiated by semantic mode.

    Naming Consistency5/5

    All tool names follow a consistent lowercase snake_case pattern, using descriptive verbs or verb-noun pairs (e.g., flag_sensitive, current_narrative, due_for_consolidation). The style is uniform and predictable, with no camelCase or mixed conventions.

    Tool Count5/5

    15 tools is well-scoped for a memory management system covering lifecycle, evidence, narrative, and audit. Each tool serves a distinct function, and the count feels justified given the domain's complexity without being excessive.

    Completeness2/5

    The toolset has significant gaps: several tools referenced in descriptions are missing from the server (review(), mark_conflict(), list_anchors(), review_narrative()). There is also no update/edit operation for existing memories, and the lack of these referenced tools could cause agent failures when following the documented workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues