Milvus
Zilliz/Milvus official MCP. Lets agents store and query vectors against the Milvus engine for production-scale RAG.
Delv Safety Grade: B
Score 72/100 · assessed 2026-04-28
Milvus MCP server is officially maintained by Zilliz, the commercial entity behind the open-source Milvus vector database. This gives it strong organisational backing and production-grade engineering standards. The server provides scoped database operations for vector storage and retrieval, which is reasonably safe for a database connector. However, the supply chain score suffers because there's no npm or PyPI package; users must clone the repository and run via uv, which bypasses standard package verification. The server requires network access to a Milvus instance and can read/write vectors plus metadata, but permissions are appropriately scoped to database operations only. Transparency is good with open source code and Zilliz's established documentation practices. No known security incidents. The main concern is the manual installation process and the need to handle authentication tokens securely.
Lethal Trifecta (prompt-injection exposure)
ONE OF THREESame.
Green flags
- Official vendor (Zilliz) with production database pedigree
- Scoped to database operations only, no filesystem or shell access
- Open source with active Milvus community backing
- Clear documentation of required credentials and connection parameters
- Production-tested codebase from established vector DB vendor
Red flags
- No package registry distribution, requires manual git clone and uv run
- Requires MILVUS_TOKEN in environment, credential exposure risk
- Network access to external database required, potential data exfiltration vector
- No version pinning or signed releases in install instructions
Permissions requested
Install
uv run src/mcp_server_milvus/server.py --milvus-uri http://localhost:19530
MILVUS_URIMILVUS_TOKENReview
Install this if you're building RAG that needs to scale beyond a few thousand documents or you already run Milvus in production. Skip it if you're prototyping with small datasets or don't want to manage a vector database. The official backing and hybrid search make it the best MCP option for serious vector workloads.
Good at
- Official Zilliz integration means it tracks Milvus features and won't go stale.
- Hybrid search with metadata filters beats pure vector similarity for most real-world RAG tasks.
- Supports both local Milvus Lite and production clusters without code changes.
- Handles billions of vectors in production, so you won't outgrow it.
- Exposes collection management, indexing, and search through clean tool calls.
Watch out
- No embedding generation built in, so you need a separate pipeline to turn text into vectors.
- Requires understanding Milvus concepts like index types and search parameters, which adds learning overhead.
- Sparse documentation in the repo itself, you'll lean on Milvus docs for advanced features.
- Install command runs source directly, not a packaged binary, so production deployments need wrapping.
- Overkill for small datasets, simpler vector stores are faster to set up for prototypes.
Use cases
- Production-grade vector store for an agent
- Semantic search across documents
- Hybrid search with metadata filters
- Custom embedding pipelines
Getting started
Works with
Similar MCPs
- MemoryPersistent memory graph for Claude. Survives across conversations - useful for personal assistants that need to remember facts about you and your projects.
- Knowledge Graph (Anthropic)Anthropic-built knowledge-graph MCP. Stores entities + relationships, persists across sessions, queryable via natural language.
- Mem0Mem0's hosted MCP for long-term memory with semantic recall. Local repo archived; current path is the cloud-hosted server at mcp.mem0.ai/mcp.
- QdrantQdrant's official MCP. Use the vector DB as a semantic memory layer for your agent: store, search, retrieve.