Skip to main content
Glama
tomRumi

hermes-memory-rag

by tomRumi
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to hermes-memory-rag

No user-submitted related servers found.

    Related Servers

    • ai-cortex

      ai-creed
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides durable project context for coding agents, including project maps, session history, and explicit memories, all stored locally.
      11 npm
      7
      MIT

    • memory

      go-ports
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides coding agents with persistent local memory by exposing tools to save, search, and retrieve decisions, bugs, and context as Markdown with hybrid keyword and semantic search.
      4
      MIT

    • daryl-memories

      DarylAndrian
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables multiple Hermes agents to persist and retrieve shared knowledge via a local graph-based memory system, supporting hybrid search, entity context exploration, and memory management.
      -

    • Continuity

      cubiix3
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables agents to maintain persistent project context locally, with source-backed memory and structured handoffs for seamless handover between interchangeable agents.
      Apache 2.0
    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.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: recall retrieves, learn writes, retire soft-deletes, stats summarizes, and ingest_code/ingest_wiki index different source types. There is no meaningful overlap or ambiguous boundary between them.

    Naming Consistency3/5

    Most names are lowercase and readable, but conventions are mixed: recall/learn/retire are bare verbs while ingest_code/ingest_wiki use verb_noun, and stats is a noun rather than an imperative verb. The pattern is not uniform, though it is still easy to parse.

    Tool Count5/5

    Six tools is a well-scoped size for a memory/RAG server; each tool earns its place by covering a distinct lifecycle step. The count is neither bloated nor too thin.

    Completeness5/5

    The tool surface covers the full cycle: ingesting wiki and code, storing learnings, recalling context, soft-withdrawing obsolete notes, and inspecting project state. Update is handled through learn/supersedes and re-ingestion, so there are no obvious dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources