Skip to main content
Glama
stflj2022

mcp-memvid

by stflj2022
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-memvid

No user-submitted related servers found.

    Related Servers

    • ORA

      black-dash77
      A
      license
      A
      quality
      D
      maintenance
      Persistent memory + intelligent context for Claude Code. Save and reuse solutions, decisions, and patterns across projects.
      43
      7
      MIT

    • am-memory

      danielwanwx
      A
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory for Claude Code — a self-evolving knowledge layer that survives across sessions, grows from every conversation, and surfaces relevant context automatically.
      14
      MIT

    • CCCMemory MCP

      xiaolai
      A
      license
      Not graded
      quality
      F
      maintenance
      Provides Claude with long-term memory by indexing conversation history, enabling semantic search, decision tracking, and cross-project search.
      18 npm
      29
      MIT

    • claude-recall

      nhevers
      A
      license
      Not graded
      quality
      F
      maintenance
      A persistent memory server for Claude Code that captures session context and tool outputs to inject relevant history into future sessions. It enables long-term recall through semantic search and automatic context management, allowing for more consistent and context-aware coding interactions.
      10 npm
      253
      ISC
    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

    C2.7/5.0

    Scored across 10 tools

    Disambiguation2/5

    Several tools overlap in purpose: lcm_search and memvid_search both search, lcm_list_summaries and memvid_summary both surface summaries, and lcm_status overlaps with memvid_summary. The LCM/AUTO tags hint at subsystems but do not clearly separate responsibilities.

    Naming Consistency2/5

    The toolset mixes lcm_ and memvid_ prefixes with inconsistent naming styles: some are noun-like (lcm_status, memvid_summary), others are verb phrases (memvid_save_context, memvid_quick_save), and search appears in both namespaces. There is no predictable verb_noun pattern across the full set.

    Tool Count4/5

    Ten tools is a reasonable size for a context/memory management server, and the count is not excessive. However, the effective surface feels slightly larger than necessary because some tools are near-duplicates of each other.

    Completeness3/5

    The set covers saving, restoring, compacting, summarizing, and searching context and memory, but long-term memory has no update/delete/forget capabilities. There is also no clear way to explicitly manage or clear stored memories beyond storing and searching.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources