Vectara MCP Server for Claude
Query your Vectara RAG corpora from Claude — ask grounded questions with full answer generation, run semantic search to retrieve ranked document chunks, and detect and correct hallucinations using Vectara's Hallucination Correction API — with the official Vectara MCP server.
Open the source and read safety notes before installing.
Safety notes
- The `ask_vectara` and `search_vectara` tools query your configured corpus — they are read-only operations against your indexed documents.
- `setup_vectara_api_key` and `clear_vectara_api_key` modify the in-session API key state; these do not write to disk.
Privacy notes
- Document chunks retrieved from your Vectara corpus are surfaced in Claude's context — ensure your corpus does not contain sensitive data you don't want in the AI's context window.
- Your `VECTARA_API_KEY` is used to authenticate all queries — keep it in the MCP config env.
Prerequisites
- A Vectara account — sign up at vectara.com.
- A Vectara API key with query permissions on your target corpus.
- A Vectara corpus created and populated with documents.
- Python with `uvx` available.
- An MCP client such as Claude Code or Claude Desktop.
Schema details
- Install type
- cli
- Troubleshooting
- No
- Scope
- Source repo
- Estimated setup
- 10 minutes
- Difficulty
- intermediate
- Website
- https://vectara.com
- Disclosure
- Vectara is a commercial RAG platform. The MCP server is officially maintained by Vectara.
Full copyable content
{
"mcpServers": {
"vectara": {
"command": "uvx",
"args": ["vectara-mcp", "--stdio"],
"env": {
"VECTARA_API_KEY": "<your-api-key>"
}
}
}
}About this resource
Overview
The Vectara MCP Server is the official Model Context Protocol server from Vectara, providing grounded RAG (Retrieval-Augmented Generation) capabilities to Claude. It exposes six tools: RAG query with answer generation, semantic search over document chunks, hallucination detection, factual consistency evaluation, and dynamic API key management. The corpus key is passed as a tool argument at query time (not an env var), making it easy to query different corpora in the same session. Licensed under Apache-2.0.
Key capabilities
- RAG query — ask natural language questions and get grounded answers with source citations.
- Semantic search — retrieve ranked document chunks without LLM answer generation.
- Hallucination correction — detect and fix hallucinations using Vectara's VHC API.
- Factual consistency — evaluate whether a claim is factually consistent with source docs.
- Session API key management — configure or clear the API key within a session.
Tools
| Tool | Purpose |
|---|---|
ask_vectara |
RAG query returning grounded generated answer |
search_vectara |
Semantic search returning ranked document chunks |
correct_hallucinations |
Identify and fix hallucinations via Vectara VHC API |
eval_factual_consistency |
Evaluate factual accuracy against source documents |
setup_vectara_api_key |
Configure API key for current session |
clear_vectara_api_key |
Remove stored API key from server memory |
How it compares
| Server | RAG answers | Semantic search | Hallucination correction | Notes |
|---|---|---|---|---|
| Vectara MCP | Yes | Yes | Yes | Official; corpus key per query |
| Pinecone MCP | No | Yes | No | Vector search only |
| Qdrant MCP | No | Yes | No | Vector search only |
| Chroma MCP | No | Yes | No | Local vector DB |
| Weaviate MCP | Yes | Yes | No | Official |
Vectara's built-in hallucination correction (VHC API) is unique — no other RAG MCP server offers an integrated hallucination detection and correction tool.
Installation
Claude Code
claude mcp add vectara \
-e VECTARA_API_KEY=<your-api-key> \
-- uvx vectara-mcp --stdio
Claude Desktop
{
"mcpServers": {
"vectara": {
"command": "uvx",
"args": ["vectara-mcp", "--stdio"],
"env": {
"VECTARA_API_KEY": "<your-api-key>"
}
}
}
}
The corpus key (VECTARA_CORPUS_KEY) is a tool argument passed at query time — ask Claude
to query a specific corpus by name or key rather than setting it as a static env var.
Requirements
- A Vectara account with at least one populated corpus.
- API key with query permissions.
- Python with
uvx(fromuv). - An MCP client (Claude Code or Claude Desktop).
Security
VECTARA_API_KEYgrants query access to your corpora — use a scoped key with only read/query permissions.- Document content retrieved from corpora enters Claude's context — ensure sensitive documents are not in public or shared corpora.
Source Verification Notes
Verified on 2026-06-18:
- Official repository
vectara/vectara-mcp(Apache-2.0) on PyPI asvectara-mcpdocuments theuvx vectara-mcp --stdioinstall,VECTARA_API_KEYenvironment variable, corpus key as a tool argument (not an env var), all six tools (ask_vectara, search_vectara, correct_hallucinations, eval_factual_consistency, setup_vectara_api_key, clear_vectara_api_key), and the hallucination correction via Vectara's VHC API. - Claude Code MCP documentation at
code.claude.com/docs/en/mcpdescribes the stdio connector pattern used above.
Source citations
Add this badge to your README
How it compares
Vectara MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
| Field | Vectara MCP Server for Claude Query your Vectara RAG corpora from Claude — ask grounded questions with full answer generation, run semantic search to retrieve ranked document chunks, and detect and correct hallucinations using Vectara's Hallucination Correction API — with the official Vectara MCP server. Open dossier | ChunkHound MCP Server Local-first codebase intelligence MCP server that indexes repositories with tree-sitter, stores searchable chunks in DuckDB, and gives Claude semantic search, regex search, daemon status, and deep code research tools. Open dossier | Code Index MCP Server Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases. Open dossier | Android Skills MCP Server for Claude Access AI-optimized Android development guides from Claude — search and retrieve SKILL.md content covering Jetpack Compose, Navigation 3, CameraX, AGP 9, App Functions, Edge-to-Edge, Android Profilers, XR, Google Play, and the Android CLI — with the Android Skills MCP server. Open dossier |
|---|---|---|---|---|
| Trust | ||||
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Category | mcp | mcp | mcp | mcp |
| Source | source-backed | source-backed | source-backed | source-backed |
| Author | Vectara | ChunkHound | johnhuang316 | Jaewoong Eum (skydoves) |
| Added | 2026-06-18 | 2026-06-06 | 2026-06-06 | 2026-06-18 |
| Platforms | Claude CodeCodexCursorClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop | Claude CodeClaude Desktop |
| Source repo | — | — | — | — |
| Safety notes | ✓The `ask_vectara` and `search_vectara` tools query your configured corpus — they are read-only operations against your indexed documents. `setup_vectara_api_key` and `clear_vectara_api_key` modify the in-session API key state; these do not write to disk. | ✓ChunkHound reads source files, Markdown, text, PDFs, and supported config files under the target directory and stores indexed chunks in a local database. Realtime indexing and daemon mode can continue watching project files after the initial MCP connection. Code research and web search tools require embedding, reranking, and LLM configuration and may invoke local CLIs or external model APIs depending on settings. Exclude generated files, vendored dependencies, secrets, large artifacts, and unrelated repositories before indexing broad workspace roots. Review MCP client configuration carefully when using an absolute project path in a global Claude Desktop config. | ✓Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources. Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths. Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases. The server can create and clear index/cache settings and temporary directories used for stored index data. Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository. | ✓The server runs entirely offline — no network requests are made during queries. All skill content is bundled with the npm package. |
| Privacy notes | ✓Document chunks retrieved from your Vectara corpus are surfaced in Claude's context — ensure your corpus does not contain sensitive data you don't want in the AI's context window. Your `VECTARA_API_KEY` is used to authenticate all queries — keep it in the MCP config env. | ✓Indexed chunks, file paths, symbols, comments, Markdown, PDFs, configuration values, database files, daemon state, and search results can reveal proprietary source code and internal architecture. Embedding, reranking, LLM, and web search providers may receive code-derived queries or snippets if configured. Local ChunkHound database files, logs, daemon state, and MCP transcripts may retain code-derived context after the session ends. Avoid sharing ChunkHound databases, config files with API keys, verbose logs, research outputs, and screenshots from private repositories. | ✓Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings. Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree. File watcher status, exclude patterns, and settings can reveal local project layout and development conventions. If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine. Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing. | ✓No API keys, user data, or query content is sent to any external service. All lookups happen locally against the bundled skill snapshot. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Signals
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.