Skip to main content
Glama
gregpriday

Memory MCP

by gregpriday
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Memory MCP

No user-submitted related servers found.

    Related Servers

    • Neuron - "Synapse"

      recla93
      A
      license
      B
      quality
      A
      maintenance
      An MCP server that provides persistent semantic memory for LLMs by building a concept graph with vector search. It enables storing, linking, and retrieving concepts across conversations using Turso vector search and 256-dimensional embeddings.
      22
      6
      PolyForm Noncommercial 1.0.0

    • mcp-recall

      Jensimogit
      A
      license
      Not graded
      quality
      C
      maintenance
      A self-hosted MCP memory server that gives AI assistants persistent, semantic memory by storing facts as vector embeddings locally, supporting semantic search and swappable embedding models.
      352 npm
      MIT

    • engram

      jblacketter
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that provides a personal semantic memory layer for AI tools. It enables storing, searching, and managing memories using hybrid vector and keyword search, allowing AI assistants to recall information by meaning.
      MIT

    • Local Brain MCP

      ejsinfuego
      F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server for AI assistants to store and retrieve personal memories on disk, with optional semantic search using embeddings.
      -
    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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: remember/recall handle memory storage and retrieval, forget handles deletion/modification, and process/process_answers handle refinement. However, process and process_answers are closely related and could be confused as a single operation, creating minor ambiguity in the workflow.

    Naming Consistency5/5

    All tool names follow a consistent verb-based pattern in lowercase (forget, process, process_answers, recall, remember). The naming is uniform and predictable, with process_answers logically extending the process tool without breaking the convention.

    Tool Count5/5

    With 5 tools, this server is well-scoped for memory management. Each tool serves a clear function in the CRUD lifecycle (create, read, update, delete), and the count is neither too sparse nor bloated, fitting the domain appropriately.

    Completeness4/5

    The tool set covers core memory operations: remember (create), recall (read), forget (delete/update), and process/process_answers (refine/update). A minor gap exists in direct update without refinement, but agents can work around this using forget or process, making it largely complete for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources