Skip to main content
Glama
CommandOSSLabs

Walrus Memory MCP

by CommandOSSLabs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Walrus Memory MCP

No user-submitted related servers found.

    Related Servers

    • polymnemo

      PCBZ
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a shared long-term memory across any LLM via MCP, enabling semantic recall, session save/reload, and multimedia memory management with local embeddings and private storage.
      MIT
    • Kova Mind MCP Server by KovaMind

      Kova Mind MCP Serverofficial

      KovaMind
      A
      license
      A
      quality
      C
      maintenance
      Enables AI memory persistence and secure credential management via vault tools for MCP-compatible clients like Claude Desktop, Cursor, and VS Code.
      12
      4 npm
      MIT

    • Mem0 MCP Server

      Silimate
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      Integrates the Mem0 Memory API with MCP-compatible clients to provide AI agents with persistent, long-term memory capabilities. It enables users to add, search, update, and delete memories to maintain context and personalization across different interactions.
      Apache 2.0

    • gnosem

      gnosem
      A
      license
      Not graded
      quality
      B
      maintenance
      Cross-vendor AI memory over MCP. Provides a persistent memory store with tools to write, search, list, forget, and supersede memories from any MCP-capable AI client.
      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.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: login for authentication, remember for explicit saving, analyze for batch extraction, recall for searching, and restore for index maintenance. Although analyze and remember both create memories, their trigger conditions are clearly separated (passage processing vs. direct user request), preventing misselection.

    Naming Consistency5/5

    All tools follow a uniform memwal_<verb> pattern using lowercase snake_case. The verb stems (analyze, restore, login, remember, recall) are consistent and predictable, making the naming highly coherent.

    Tool Count5/5

    With only five tools, the surface is compact and focused on the essential operations of a personal memory system: authentication, writing, reading, batch processing, and maintenance. No tool feels redundant or extraneous.

    Completeness3/5

    The set covers authentication, creation, recall, and bulk ingestion, but lacks update and delete operations. For a memory system, the inability to forget or correct stored facts is a notable gap that could limit agent effectiveness.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources