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

    • 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
      C
      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.
      -

    • mcp-vector

      xrykmb
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to turn documents into vectors, perform approximate nearest neighbor search with HNSW, and filter by metadata via MCP tools for RAG workflows.
      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/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct operation on either collections, points, or the server itself. Collection existence vs. info are adjacent but clearly separated by their boolean-vs-detailed-output behavior.

    Naming Consistency4/5

    Tools mostly follow a consistent qdrant_<resource>_<action> snake_case pattern. qdrant_query and qdrant_health_check deviate slightly by omitting the resource segment, but the overall pattern remains predictable.

    Tool Count5/5

    13 tools is well-scoped for a Qdrant MCP server: collection lifecycle, point operations, search, and health check all have a place. No tool feels redundant or out of scope.

    Completeness4/5

    The core surface is solid: collections can be created, listed, inspected, updated, and deleted, and points can be upserted, fetched, deleted, scrolled, counted, and queried. The main gap is that collection_update references a qdrant_collection_vector_create tool that is not actually exposed, making it impossible to add a new named vector to an existing collection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources