Skip to main content
Glama
NovaAI-innovation

qdrant-kuzu-mcp

by NovaAI-innovation
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to qdrant-kuzu-mcp

No user-submitted related servers found.

    Related Servers

    • MahoRAGa

      Aadi775
      A
      license
      B
      quality
      D
      maintenance
      Persistent, graph-powered memory for AI agents that provides long-term semantic recall using a local Kuzu graph database.
      55
      4
      MIT

    • Qdrant MCP Server

      mcandiav
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables storing and retrieving information using semantic search with Qdrant vector database. Acts as a memory layer for LLMs to persistently store and semantically search through information and metadata.
      Apache 2.0
    • supermem by LaxRaj

      supermemofficial

      LaxRaj
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables storing and querying a personal knowledge graph as a shared memory, allowing agents and tools to remember facts, entities, relations, and recall relevant context via natural language hybrid search.
      1
      MIT

    • agent-memory-mcp

      Yarmoluk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables persistent, graph-based memory for AI agents, allowing them to store, traverse, and recall relationships between facts, decisions, and context across sessions for efficient reasoning and reduced token usage.
      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.
      -
    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.5/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are exact opposites — one stores, one retrieves — so there is no possibility of confusing their purposes. Each tool's role is clear from its name and description.

    Naming Consistency5/5

    Both tools follow the same verb-oriented convention with a consistent 'qdrant-' prefix: qdrant-find and qdrant-store. The pattern is uniform and predictable.

    Tool Count3/5

    At two tools, the server is on the thin side — it covers the bare minimum but feels underdeveloped for a memory system that could reasonably include more operations. The count is borderline rather than egregiously incomplete.

    Completeness3/5

    The basic store-and-retrieve lifecycle is present, but there are notable gaps: no way to delete, update, list all memories, or search by metadata. Agents can work around this, but the surface is minimal and lacks full memory management.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources