Skip to main content
Glama
Hilbras

Remembra

by Hilbras
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Remembra

No user-submitted related servers found.

    Related Servers

    • 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

    • Memorium

      updalla-apshir
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to have persistent long-term memory by automatically storing and retrieving important information via MCP tools.
      MIT

    • memento-mcp-server

      jee1
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides AI agents with persistent, human-like memory infrastructure via MCP, enabling them to store, search, summarize, and forget episodic, semantic, procedural, and working memories across sessions.
      752 npm
      MIT

    • Mycelia

      kittors
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a persistent, cross-tool memory layer for AI coding agents via MCP, enabling storage and retrieval of decisions, preferences, and context across different tools and models.
      1 npm
      1
      MIT

    • mcp-memory

      oneKn8
      A
      license
      A
      quality
      D
      maintenance
      Provides persistent memory with semantic search for MCP-based AI agents, enabling them to store and recall information across sessions using vector embeddings.
      4
      1
      MIT

    • qcdoc-mem

      wychenzhou
      A
      license
      A
      quality
      C
      maintenance
      Provides AI agents with persistent long-term memory over MCP, extracting durable facts from conversations, storing them as plain files, and injecting ranked memories into later sessions via recall and search tools.
      10
      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.7/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct: store, get, update, forget, archive, revive, search, list, relate, history, and maintain each map to a separate operation. The main ambiguity is memory_batch, which wraps store/update/delete/export and could be confused with the individual write/update/delete tools, though its batch purpose is stated.

    Naming Consistency4/5

    The memory_ prefix is consistent and most suffixes are action verbs: store, search, list, forget, get, relate, update, archive, revive, maintain. memory_batch and memory_history break the verb pattern, but the overall convention remains predictable and readable.

    Tool Count5/5

    Thirteen tools is well within the ideal range and each tool covers a distinct aspect of memory management: CRUD, search, versioning, relationships, archival, batch operations, ingestion, and maintenance. No tool feels redundant or unnecessary.

    Completeness5/5

    The surface fully covers memory lifecycle: store, retrieve, list, search, update, delete, archive, revive, version history, relation management, batch processing, and automated digesting from transcripts. There are no obvious dead ends or missing core operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources