Skip to main content
Glama
aalokjha-gits

Memory MCP

by aalokjha-gits
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Memory MCP

No user-submitted related servers found.

    Related Servers

    • local-memory-mcp

      mason-yb-zhang
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with persistent, local cross-session shared memory by combining vector semantic retrieval with knowledge graph relationships, and supports short/long-term memory management and local backups.
      -

    • ClawMem MCP Server

      BFLabsAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to maintain persistent, local memory with retrieval-augmented search, knowledge graphs, and context surfacing, without any cloud dependencies.
      2,052 npm
      MIT

    • SharedBrain

      awictor
      A
      license
      Not graded
      quality
      B
      maintenance
      Local-first, multi-user shared memory for AI agents with semantic search, offline support, and team synchronization.
      MIT
    • RushDB MCP Server by rush-db

      RushDB MCP Serverofficial

      rush-db
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to gain persistent, structured memory that is semantically searchable and graph-traversable, allowing them to store and query records and relationships without managing embeddings or schemas.
      54 npm
      Apache 2.0

    • clude-memory

      sebbsssss
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to store, recall, update, delete, and analyze persistent memories with semantic search, decay, and anomaly retrieval across hosted, self-hosted, or fully local storage modes.
      53 npm
      22
      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.1/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct operation: add, link, search, list, forget, profile, and help. The search vs list distinction is explicitly described as semantic versus metadata browsing, and memory_profile is clearly separated from general knowledge storage.

    Naming Consistency4/5

    All tools share the memory_ prefix, which is highly predictable. Most suffixes are verb-style actions like add, link, search, list, and forget, though profile and help are nouns rather than actions, creating a minor inconsistency.

    Tool Count5/5

    Seven tools is well-scoped for a memory server: core CRUD, linking, browsing, preference storage, and help each have a clear place. There is no apparent redundancy or excessive surface area.

    Completeness4/5

    The core memory lifecycle is covered: add, read/search/list, delete, link, and profile storage. An explicit update operation and an unlink operation are missing, but these can be worked around with forget+add, so they are minor gaps rather than critical dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources