Skip to main content
Glama
renzynx

@renzynx/memory-mcp

by renzynx
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to @renzynx/memory-mcp

No user-submitted related servers found.

    Related Servers

    • agent-memory

      khaled1174
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing persistent memory management for AI agents using SQLite and FTS5, enabling storage, full-text search, and recall of memories with namespace isolation.
      1
      MIT

    • MCPSaver

      cpntodd
      A
      license
      Not graded
      quality
      B
      maintenance
      Local MCP server for persistent, searchable agent memory using SQLite FTS5, replacing flat MEMORY.md files with efficient full-text search and workspace context caching.
      GPL 3.0

    • fuga-memory

      densuke
      A
      license
      A
      quality
      D
      maintenance
      An MCP server providing long-term memory for LLMs via hybrid search (FTS5 + vector) stored in SQLite, with time-decay scoring and support for multiple AI assistants.
      4
      2
      MIT

    • recall-mcp

      autonsol
      F
      license
      Not graded
      quality
      D
      maintenance
      Persistent memory MCP server for AI coding agents. Stores, searches, and retrieves context across sessions using SQLite and FTS5.
      -
    • hive-memory by hivemem-dev

      hive-memoryofficial

      hivemem-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for personal and shared memory with full-text search (SQLite FTS5) and outcome tracking, compatible with any MCP agent like Claude Code, Cursor, and Codex CLI.
      6 npm
      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.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: storing memories, searching them, and listing categories. There is no functional overlap between the three operations.

    Naming Consistency5/5

    All tool names follow a predictable verb_noun snake_case pattern: save_memory, search_memories, list_categories. The singular/plural noun variation is natural and does not create confusion.

    Tool Count5/5

    Three tools is a minimal but well-scoped set for a focused memory server. Each tool covers a distinct core operation without unnecessary bloat.

    Completeness3/5

    The server supports saving, searching, and listing categories, but lacks update and delete operations for memories. This creates a notable lifecycle gap where incorrect or obsolete memories cannot be corrected or removed.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources