Skip to main content
Glama
Magnemo-AI

Magnemo

Official
by Magnemo-AI
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Magnemo

No user-submitted related servers found.

    Related Servers

    • cookbook-brain

      dpro10
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that gives AI agents persistent, file-based memory stored as plain markdown files in a local git repository, enabling agents to remember, recall, and build on information across sessions.
      6 npm
      1
      MIT

    • mnemo

      JoaquimLegal
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent, local-first memory for AI agents via Markdown files in a git repo, with search, branching, and auditability.
      5 npm
      2
      MIT

    • loreweave

      lets-order-some-fries
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that gives AI agents durable, temporal memory over local markdown vaults, with tools for searching, asserting facts, querying point-in-time state, and reinforcing useful knowledge.
      380 npm
      MIT

    • Engram

      rwnalds
      A
      license
      A
      quality
      A
      maintenance
      A self-hosted MCP server that gives AI agents shared, long-term memory over a git-backed folder of markdown, enabling persistent knowledge search, read, and write without a database.
      16
      22 npm
      11
      MIT

    • genmem

      helloSobuj
      A
      license
      Not graded
      quality
      C
      maintenance
      A local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.6/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool maps to a distinct lifecycle action: querying approved memory, proposing new memory, loading the boot context, and closing a session. There is no real overlap, since bootpack is a deterministic startup read while retrieve is on-demand canonical lookup.

    Naming Consistency5/5

    All four names are lowercase single-word commands, forming a consistent imperative style. They do not follow a verb_noun scheme, but the naming convention is uniform and predictable across the set.

    Tool Count5/5

    Four tools is tight but appropriate for the server's narrow, well-defined purpose. Each tool has a distinct role and none feels redundant or extraneous.

    Completeness5/5

    The toolset covers the full agent-facing memory lifecycle: wake with bootpack, read with retrieve, propose with stage, and close with handoff. Keyholder review appears intentionally external, and the deterministic bootpack plus append-only handoff ledger leaves no obvious dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources