Skip to main content
Glama
avaazquezz

io.github.avaazquezz/mcp-qdrant

by avaazquezz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to io.github.avaazquezz/mcp-qdrant

No user-submitted related servers found.

    Related Servers

    • rag-mcp-server

      q6066697
      A
      license
      A
      quality
      C
      maintenance
      Exposes hybrid retrieval (dense embeddings + BM25 + RRF) and document operations (search, fetch, rerank) as MCP tools, using Qdrant and OpenAI embeddings for local or server mode.
      3
      MIT
    • HyperspaceDB MCP Server by YARlabs

      HyperspaceDB MCP Serverofficial

      YARlabs
      A
      license
      B
      quality
      C
      maintenance
      Enables LLMs to manage vector collections, run hybrid semantic and Wasserstein searches, traverse knowledge graphs, and perform geometric and cognitive diagnostics through MCP tools. It also provides administration for caches, quantization, reconsolidation, and collection lifecycle operations.
      35
      38 npm
      MIT

    • Pinecone MCP Server

      Solaceking
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Enables AI assistants to perform semantic search, manage vectors, and interact with Pinecone vector databases through standardized MCP tools. Supports querying, upserting, deleting vectors and monitoring database statistics for knowledge base operations.
      4 npm
      -

    • MCP RAG Assistant

      1jelly7
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables RAG (Retrieval-Augmented Generation) with tools for vector search, document access, and OpenAI integration, plus MySQL storage and file system operations via MCP.
      -
    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 13 tools

    Disambiguation4/5

    Most tools have clearly distinct scopes: collection lifecycle, point CRUD, querying, and health checks are separated cleanly. A few boundaries are slightly fuzzy, especially qdrant_query with order_by/sample versus qdrant_points_scroll with order_by, and qdrant_points_get by id versus querying by point id, but the descriptions make the intended use reasonably clear.

    Naming Consistency5/5

    All tools follow a predictable qdrant_* snake_case convention with resource-oriented names such as qdrant_collection_create and qdrant_points_upsert. The few non-resource names like qdrant_query and qdrant_health_check still fit the same overall pattern.

    Tool Count5/5

    The set has 13 tools, which is well-scoped for a Qdrant MCP server. Each tool covers a distinct collection, point, query, or health operation without obvious redundancy.

    Completeness4/5

    The surface covers the core Qdrant lifecycle: collection list/create/update/delete/exists/info, point get/delete/upsert/scroll/count, query, and health. Minor gaps remain around payload index management, aliases/snapshots, and partial payload updates, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources