Skip to main content
Glama
Tapiocapioca

memvid-mcp

by Tapiocapioca
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to memvid-mcp

No user-submitted related servers found.

    Related Servers

    • saor-mcp

      ubajxn
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing persistent memory for AI agents, enabling them to read, write, and query memories across sessions.
      9
      17 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

    • Mnemon

      coopers98
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted memory server that gives AI agents a shared, persistent second brain, enabling verbatim storage, hybrid semantic/keyword retrieval, and a synthesized wiki layer through MCP tools.
      MIT

    • mem0-agent-memory

      arunkumars-mf
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that provides persistent memory capabilities for AI agents using Mem0, enabling storage, search, and management of contextual information across conversations with support for multiple backends and LLM providers.
      18
      21 PyPI
      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

    B3.3/5.0

    Scored across 40 tools

    Disambiguation3/5

    Most tools have distinct purposes, but there is some overlap that could cause confusion. For example, memvid_find and memvid_vec_search both handle search operations with different methods, and memvid_verify and memvid_verify_single_file are similar in function but differ in scope. The descriptions help clarify, but agents might misselect between closely related tools.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern with a 'memvid_' prefix, such as memvid_fetch, memvid_ask, and memvid_audit. This uniformity makes the tool set predictable and easy to navigate, with no deviations in naming conventions.

    Tool Count2/5

    With 40 tools, the count is excessive for a memory management server, making it feel heavy and potentially overwhelming. A more focused set of 10-20 tools would be more appropriate for this domain, as many operations could be consolidated or simplified.

    Completeness5/5

    The tool set provides comprehensive coverage for memory file operations, including creation, reading, updating, deletion, search, enrichment, export, and management tasks like encryption and diagnostics. There are no obvious gaps, and it supports full CRUD/lifecycle workflows for the domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources