Skip to main content
Glama
wb200

Memory-MCP

by wb200
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Memory-MCP

No user-submitted related servers found.

    Related Servers

    • AI Agent History RAG MCP

      velenzaboc
      A
      license
      A
      quality
      B
      maintenance
      Provides persistent, searchable memory across AI coding agent and chat history (Claude Code, Codex, Gemini CLI, ChatGPT, and more) via retrieval-augmented generation, enabling semantic and hybrid search to retain context across sessions.
      5
      MIT

    • arcane

      Edition-X
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent, searchable memory and knowledge capture for AI-assisted development, enabling agents to retain decisions, bugs, and patterns across sessions and projects.
      MIT

    • hive-memory

      moonx010
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI coding agents with persistent, graph-connected memory across projects, enabling cross-project context retrieval via synaptic connections and hybrid search.
      7 npm
      8
      MIT

    • rekal

      janbjorge
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides long-term memory for LLMs via local SQLite storage with hybrid search (BM25, vectors, recency decay), enabling AI coding agents to persist and recall memories across sessions without cloud or API keys.
      53
      MIT

    • MCP Memory Server

      beach55607-max
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides long-term memory for AI coding agents, enabling them to remember, search, and organize information across sessions and platforms like Claude Code, ChatGPT, and Cursor.
      12 npm
      8
      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 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: delete, health, recall (all projects), recall (current project), save, session start, stats, update. The two recall tools are differentiated by scope, and no overlapping functionality exists.

    Naming Consistency5/5

    All tools follow a consistent 'memory_<verb>' pattern in snake_case, with verbs like delete, recall, save, update. The compound 'session_start' still fits the pattern clearly.

    Tool Count5/5

    8 tools is appropriate for a memory system, covering CRUD operations, search, health, stats, and session context. Each tool earns its place without being excessive.

    Completeness4/5

    Core CRUD is covered (save, recall, update, delete). Minor gaps: no direct retrieval of a single memory by ID (only recall with search) and no bulk operations. Agents can work around these gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources