Skip to main content
Glama
harsh-gulhane

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

    • Gingugu

      gingugu
      A
      license
      A
      quality
      A
      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.
      21
      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

    • 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
    • litopys by litopys-dev

      litopysofficial

      litopys-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent graph-based memory for AI agents, stored as plain markdown — no vector DB. Typed nodes and 11 relation types via 5 MCP tools (search, get, create, link, related), stdio and HTTP/SSE transports.
      3
      MIT

    • Agent Memory Engine

      rgolabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store and recall durable facts, decisions, and lessons over MCP using hybrid semantic and keyword search, typed memories, graph relations, sessions, and time-travel queries. Runs locally with no server process or API key, persisting everything to files that both agents and a CLI can share.
      14 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

    A3.8/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools target clearly distinct operations, and the descriptions actively disambiguate the tricky pairs (save vs append vs update, search vs list). The only soft overlaps are search_memory/list_memories/find_by_entity and find_duplicates vs search, but the parameter semantics (query vs filters vs entity) make the boundaries clear.

    Naming Consistency5/5

    All 16 tools follow a consistent snake_case verb_noun pattern (save_memory, get_thread, list_entities, find_duplicates, cleanup_expired). Verb families (get/list/find/search) are used predictably for their intent.

    Tool Count4/5

    16 tools is on the heavy side, but the memory domain genuinely spans CRUD, search, entities, threads, history, stats, and maintenance, and each tool maps to a real need. Slightly over the typical sweet spot without feeling padded.

    Completeness5/5

    Full lifecycle is covered: create (save), read (get/list/search), update (update/append), delete (delete_memory/cleanup_expired/delete linked entities), plus history, dedup detection, stats, threads, and entity lookup. No obvious dead ends for the stated purpose.

    Maintenance

    ActivityNo data
    ResponsivenessNo issues

    Resources