vector-mcp
Related Servers
Alternatives to vector-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables integrating RAG into AI agents via MCP server, supporting multiple vector database technologies.11MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates RAG into AI agents via MCP Server, supporting multiple vector database technologies for collection management and search operations.11MIT
- AlicenseNot gradedqualityDmaintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.65MIT
- -licenseNot gradedqualityNot gradedmaintenanceA sophisticated MCP server providing advanced memory capabilities with RAG, hallucination detection, and enterprise-grade AI infrastructure for intelligent agent ecosystems.-
- AlicenseNot gradedqualityBmaintenanceMCP server providing tools for entity extraction, query refinement, and relevance checking to build Agentic RAG applications.MIT
- FlicenseNot gradedqualityDmaintenanceAn enterprise-ready MCP server that exposes a RAG tool for retrieving relevant context and metadata from a Qdrant vector database using natural language queries.2-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: collection management (CRUD operations on collections) and search (semantic, lexical, hybrid). There is no overlap, making it easy for an agent to select the correct tool.
All tool names follow a consistent 'vector_' prefix pattern with descriptive suffixes ('collection_management', 'search'). Internal action names are uniformly snake_case, maintaining predictability.
With only 2 tools, the server feels somewhat thin for a vector database MCP. While each tool bundles multiple actions, a few more tools (e.g., separate tools for document operations) would improve organization.
The server lacks essential operations such as updating or deleting documents, retrieving collection details, or managing metadata. These gaps would likely cause agent failures in typical workflows.