Skip to main content
Glama
Sign In
MemKernel

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
      B
      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
      B
      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
      33 PyPI
      1
      MIT

    • memory-as-history

      BrunoBanana
      A
      license
      A
      quality
      B
      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
    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

    B3.3/5.0

    Scored across 23 tools

    Disambiguation4/5

    Most tools target a distinct resource+action pair, and the trickiest near-duplicates are explicitly differentiated (append_decision vs fenced_append_decision, note vs append_decision, log_execution vs note). The only mild overlaps are query_state vs history (consolidated memory vs recent events) and post_notice vs sync_now, which the descriptions mostly disambiguate.

    Naming Consistency4/5

    All tools share a uniform memkernel_ prefix and snake_case, with a verb-first pattern (acquire_lease, query_state, fork_investigation). A handful drop the noun (checkout, rollback, note, history), which is a minor deviation rather than an inconsistency.

    Tool Count3/5

    23 tools sits at the heavy end for a single server, and an agent must juggle four sub-domains (leases, memory events, branches, notices/sync) at once. Very few tools are redundant, but the breadth makes selection cost high.

    Completeness3/5

    The surface covers leases, memory recording, branching, rollback, diffing, and notice sync/export/import well, but obvious lifecycle gaps remain: no branch merge tool (fork+diff exist without a way to land work) and no way to complete, update, or abandon a task or branch. These are notable holes an agent will hit during normal workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources