Skip to main content
Glama
Sign In
MemDrive

MemDrive

by Newmannn91
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to MemDrive

No user-submitted related servers found.

    Related Servers

    • Link

      gowtham0992
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to capture, structure, remember, and retrieve source-backed memory as local Markdown files, with reviewable writes and no cloud dependency.
      218
      MIT

    • AIBrain

      NitishKashyapR
      A
      license
      Not graded
      quality
      B
      maintenance
      A personal, offline-first memory for AI assistants that enables them to read, search, and write to a shared folder of Markdown files, so they all remember you without needing a cloud.
      1
      MIT

    • mor

      laat
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to search, read, create, update, and remove personal markdown notes stored locally, providing persistent memory across sessions.
      20 npm
      2
      MIT

    • tua

      Tuacircles
      A
      license
      A
      quality
      B
      maintenance
      Enables saving, searching, retrieving, linking and importing AI work as plain markdown files with automatic provenance in a local folder the user owns. Runs entirely on the user's machine with no account, key or network calls, and never deletes anything.
      11
      AGPL 3.0

    • mcp-ltm

      kvas-it
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides persistent long-term memory for AI assistants with tag-based retrieval, wiki-style linking, and source references, storing memories as markdown files with SQLite index.
      2
      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.2/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool has a distinct role: search, read, write, list, and two deliberate OS-side-effect helpers. The only real overlap is read_file vs open_image, since both can surface an image, but the descriptions explicitly split 'show it in the conversation' from 'open it on the user's screen' and constrain the latter to explicit requests.

    Naming Consistency5/5

    Every name is snake_case verb_noun (search_files, save_file, read_file, list_directory, open_containing_folder, open_image), with the two viewer helpers sharing a clean open_ prefix. No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is a tight, well-scoped surface for a personal memory library, and each one (search, read, save, list, open folder, open image) fills a distinct slot. Nothing feels padded or redundant.

    Completeness3/5

    Read, write (new/overwrite/append), search, and browse are covered, but the surface has no delete, move, or rename operation, so the file lifecycle is open-ended and an agent cannot clean up mistaken or stale notes. These are notable gaps an agent would hit in real use.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources