Skip to main content
Glama
Sign In
memory

memory

by harsh-gulhane
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to memory

No user-submitted related servers found.

    Related Servers

    • open-memory

      atmakurakhil
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes a local SQLite-backed long-term memory to AI agents as MCP tools, letting them add conversations and documents, record dated facts with provenance, search and assemble context, and edit, inspect, or forget what was stored. It runs with your own embedding and LLM keys, so memories stay readable, exportable, and portable as plain markdown.
      MIT

    • Aletheia

      mohamed-ashraf-elsaed
      A
      license
      A
      quality
      B
      maintenance
      Provides AI coding tools with one local SQLite memory and rules store they can read over MCP, REST or the CLI, so facts, sessions and goals persist across sessions and shared rules are written into each tool's own instruction file. Runs entirely on your machine with no account, telemetry or network calls by default.
      4
      14
      444 npm
      10
      Apache 2.0

    • OmniMind

      IrfanCodesBTW
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides a local stdio MCP server that lets multiple AI clients share a Markdown-vault memory — searching, reading, and recording attributed notes — while coordinating task claims, checkpoints, handoffs, and completions through SQLite with revision-safe, idempotent operations. It runs entirely on the user's machine with no external database or API key required.
      16 npm
      MIT

    • Gingugu

      gingugu
      A
      license
      A
      quality
      B
      maintenance
      Persistent long-term memory for AI coding assistants. Local SQLite, no cloud - 16 MCP tools to store, search, relate, and consolidate typed memories with a confidence lifecycle, hybrid BM25 + semantic search, namespaces, a knowledge graph, and a built-in OS keychain credential vault.
      23
      7
      MIT

    • hindsight-shared-memory

      ShmuelOps
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables all local Claude Code sessions, subagents, and other MCP clients to read and write one shared long-term memory over HTTP on localhost, so facts retained by one agent can be recalled by another. It extracts atomic facts, entities, and observations into an embedded local Postgres with ONNX embeddings and reranking, requiring no API key.
      MIT

    • enscribe

      Zalitygit
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables any MCP-capable AI client to search and write a local-first personal memory store backed by one SQLite file, fusing FTS5 keyword and locally computed vector search over records and git-tracked markdown knowledge pages. An optional authenticated HTTP mode shares the same memory across agents and devices without any cloud dependency.
      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

    A3.8/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools have clearly distinct roles (search vs. list vs. entity lookup vs. duplicate detection vs. stats), and descriptions explicitly cross-reference each other (e.g. append_memory vs. update_memory). The main overlap is between list_memories with a thread_id filter and get_thread, which retrieve similar data, plus get_memory vs. get_memory_history which differ only by whether history is included.

    Naming Consistency5/5

    Every name follows a predictable snake_case verb_noun pattern (list_memories, get_memory, save_memory, update_memory, delete_memory, find_by_entity). The lone slight variation is cleanup_expired (verb + adjective, no noun), but it is still clear and idiomatic.

    Tool Count4/5

    16 tools is at the upper edge for a well-scoped set, but each earns its place: core CRUD, search, entity lookup, threads, history, duplicates, stats, and expiry cleanup. A few aggregation tools (get_stats, list_threads, get_daily_summary) could arguably be folded into list/search filters, keeping it just shy of ideal.

    Completeness5/5

    Full lifecycle coverage: create (save_memory), read (get_memory, list_memories, search_memory), update (update_memory, append_memory), delete (delete_memory), plus history, entity linking/search, thread grouping, stats, duplicate detection, and expiry cleanup. No obvious dead ends for a memory-store domain.

    Maintenance

    ActivityMaintained
    ResponsivenessLimited data

    Resources