Skip to main content
Glama
varadganjoo

MemKernel

by varadganjoo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to MemKernel

No user-submitted related servers found.

    Related Servers

    • nuzo-memory

      fabionfsc
      A
      license
      Not graded
      quality
      F
      maintenance
      Local-first, auditable memory for AI agents. Provides durable context for MCP hosts with SQLite storage, CLI, and MCP tools for memory management.
      2
      Apache 2.0

    • oneledger

      Slocean
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a self-hosted shared memory ledger that lets coding agents store, search, list, and forget memories over MCP, with local SQLite or remote HTTP access, secret filtering, and optional synchronization between nodes.
      MIT

    • CP Memory

      CJhuochai
      A
      license
      C
      quality
      A
      maintenance
      Local-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.
      40
      1
      MIT

    • memory-as-history

      BrunoBanana
      A
      license
      A
      quality
      A
      maintenance
      Provides a SQLite-backed MCP server that records agent memory as history, enabling explicit consolidation, source checks, revisions, narrative versions, and accountable forgetting.
      15
      MIT

    • tartarus-mcp

      saluca-labs
      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
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target distinct resources and actions (lease acquire/release/heartbeat, branch fork/checkout/rollback, memory query/history/diff). The only real risk is memkernel_append_decision vs memkernel_fenced_append_decision, but the descriptions clearly distinguish the lease-guarded variant, keeping confusion low.

    Naming Consistency4/5

    All names share a consistent memkernel_ prefix with snake_case and are mostly verb_noun (append_decision, acquire_lease, trigger_gc, log_execution). A few are bare nouns/verbs (checkout, rollback, note, history), a minor deviation but still readable and predictable.

    Tool Count4/5

    16 tools is slightly on the heavy side but each maps to a distinct capability spanning leases, branches, decisions, execution logging, notes, and GC. Nothing looks redundant enough to be padding, so the count fits the scope.

    Completeness4/5

    The surface covers the full memory-kernel lifecycle: tasks, decisions, leases, branch management, history, diff, GC, execution logging, and notes. Minor gaps like no explicit decision deletion or separate fact-listing tool exist, but query_state and GC largely compensate.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources