io.github.avaazquezz/mcp-qdrant
Related Servers
Alternatives to io.github.avaazquezz/mcp-qdrant
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with a Qdrant vector database, including embedding generation and vector search operations.MIT
- AlicenseAqualityDmaintenanceExposes 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.3MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with Qdrant vector database for storing, searching, and managing vectors with automatic text embedding.1-

HyperspaceDB MCP Serverofficial
AlicenseBqualityCmaintenanceEnables 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.35MIT- FlicenseNot gradedqualityNot gradedmaintenanceEnables 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.18 npm-
- FlicenseNot gradedqualityDmaintenanceEnables RAG (Retrieval-Augmented Generation) with tools for vector search, document access, and OpenAI integration, plus MySQL storage and file system operations via MCP.-
TDQS
Scored across 13 tools
Each tool targets a clearly distinct resource+action: collection lifecycle (create/list/info/update/delete/exists), point lifecycle (upsert/get/delete/scroll/count), a single query tool, and a health check. The nearest overlaps — points_get (by id) vs points_scroll (paging) vs points_count vs query — are separated cleanly by their argument shapes and descriptions. No two tools appear interchangeable.
Names follow a predictable qdrant_<resource>_<verb> pattern (qdrant_collection_create, qdrant_points_upsert, qdrant_points_scroll, etc.), with the resource group always spelled out. The only deviations are qdrant_query (verb-only, no resource) and qdrant_health_check, which are minor but break the otherwise uniform scheme.
13 tools is well within the ideal 3-15 range and each tool maps to a real, non-redundant operation on a vector database. Nothing feels padded; the collection/point split is economical.
Core collection and point CRUD is covered, but there are notable gaps: qdrant_collection_update explicitly directs users to 'qdrant_collection_vector_create' for adding named vectors, yet that tool is not exposed. There is also no payload-index management tool, even though query/scroll's order_by requires a range index that cannot be created with this surface.