Skip to main content
Glama
Sign In
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.
      9 npm
      1
      MIT

    • mnemo

      JoaquimLegal
      A
      license
      Not graded
      quality
      D
      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

    • Engram

      rwnalds
      A
      license
      A
      quality
      C
      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
      35 npm
      18
      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.
      5 npm
      MIT
    Deploy Server
    Context All Your Agents Can ShareAgents share what they learn, hand off work, and hold it when you switch models. Start with 5 GB free.fulcradynamics.comAd

    TDQS

    A4/5.0

    Scored across 7 tools

    Disambiguation4/5

    Each tool has a clearly stated role in the memory lifecycle (stage/keep/drop/pending/retrieve) plus session tools (handoff/bootpack). Minor overlap exists: handoff also stages a note (overlapping with stage), and pending and bootpack both surface staged/review content, but the descriptions delineate their boundaries well enough.

    Naming Consistency3/5

    Names are all lowercase single tokens with no case-style inconsistencies, but they mix verbs (stage, keep, drop, retrieve) and nouns (handoff, pending, bootpack) with no predictable verb_noun pattern. Readable but not a consistent convention.

    Tool Count5/5

    Seven tools map cleanly onto the vault's capture-review-approve-retrieve-session lifecycle; each tool earns its place and none appears redundant filler.

    Completeness4/5

    Core lifecycle is covered: propose, approve, reject, list pending, retrieve canon, boot context, and session handoff. Gaps exist around editing/amending a staged note and managing canon directly (no update/delete of Memory), but agents can work around these via stage/drop.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources