Vectara MCP server
OfficialRelated Servers
Alternatives to Vectara MCP server
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceMCP server for Vectros, a typed multi-tenant record store with hybrid search and citation-grounded RAG, enabling agents to query, search, and ask questions over their own indexed data.134 npm3Apache 2.0- AlicenseAqualityDmaintenanceMCP server for OpenAI Vector Store API, managing vector stores, files, file batches, and semantic search.216 npmMIT
- FlicenseNot gradedqualityDmaintenanceAn MCP server that exposes document retrieval as tools (semantic search and source listing) for any LLM, using a vector index built from DocPilot's ingestion pipeline.-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that indexes documents and serves relevant context to LLMs via Retrieval Augmented Generation (RAG).25 npm37MIT
- FlicenseNot gradedqualityBmaintenanceMCP server that enables semantic search over PDF documents using RAG with ChromaDB and OpenAI embeddings.-
- FlicenseNot gradedqualityDmaintenanceLocal MCP server that provides semantic search (RAG) over code repositories, enabling AI clients like Claude and Gemini to access project context without manual re-upload.-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: ask_vectara performs RAG queries with generated responses, while search_vectara performs semantic search without generation. Their descriptions explicitly differentiate between these functions, leaving no room for confusion or overlap in intended use.
Both tools follow a perfect verb_noun pattern with 'vectara' as the consistent noun component. The naming is completely uniform across the tool set, using snake_case consistently without any deviations or mixed conventions.
With only 2 tools, this server feels significantly under-scoped for a Vectara integration. A comprehensive MCP server for a search/RAG platform would typically include tools for corpus management, document operations, configuration settings, and additional query types beyond just these two basic search functions.
The tool surface is severely incomplete for a Vectara integration. While it covers basic querying, it lacks essential operations like creating/updating/deleting corpora, managing documents within corpora, configuring search parameters, handling authentication more robustly, or providing administrative functions. This creates significant gaps that will limit agent capabilities.