Skip to main content
Glama
qianqiuwanzi

hypermarrow-mcp

by qianqiuwanzi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to hypermarrow-mcp

No user-submitted related servers found.

    Related Servers

    • engram

      TushaeBXN
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first AI memory across sessions via MCP tools for storing, searching, and retrieving context from past interactions.
      1
      MIT

    • mcp-memory-system

      zitongz343-ai
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides AI clients with a persistent, readable and writable long-term memory layer over MCP, enabling creation, retrieval, tagging, updating, and deletion of memories across sessions.
      49 npm
      -

    • mnemosyne-mcp

      CodeCoreLab
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides AI agents with persistent local memory management, including semantic recall, knowledge graph traversal, and automatic memory consolidation, enabling structured long-term memory across MCP clients.
      Apache 2.0

    • memory-mcp

      lakehouse-42
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory for AI assistants via MCP, enabling them to store and recall facts, preferences, and tasks across conversations using either local file storage or a cloud backend with semantic search.
      5
      5 npm
      MIT

    • CP Memory

      CJhuochai
      A
      license
      C
      quality
      A
      maintenance
      Local-first, governable long-term memory for AI agents. Provides SQLite-backed storage, cross-session recall, and traceable memory corrections through a standard MCP interface.
      40
      52 PyPI
      1
      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 4 tools

    Disambiguation5/5

    Each tool has a distinct purpose: writing context, recalling it, maintaining memory, and resolving path anchors. No two tools overlap in function.

    Naming Consistency4/5

    record_context and recall_memory follow verb_noun, file_anchor is a compound noun, and consolidate is a bare verb. Mostly consistent but slightly mixed.

    Tool Count5/5

    Four tools tightly cover the server's memory-management scope without redundancy or bloat.

    Completeness4/5

    The core write/read/maintenance lifecycle is covered, including path anchoring. Explicit per-entry update/delete is absent, but consolidate handles duplication and aging.

    Resources