VECTOR DATA MANAGEMENT / Zilliz
Zilliz MCP Server
Manages Zilliz Cloud projects and clusters and works with data in Milvus collections (create, insert, delete, vector and hybrid search) from an MCP client.
“MCP server for Zilliz Cloud and Milvus”
01 / THE REASONING
Why this made the selection.
- Published in Zilliz's own repository; the README at this commit separates control-plane tools (list_projects, list_clusters, create_free_cluster, describe_cluster, suspend_cluster, resume_cluster, query_cluster_metrics) from data-plane tools on Milvus collections.
- pyproject.toml names zilliz-mcp-server 1.0.0 with license Apache-2.0, matching the LICENSE file, and declares the zilliz-mcp-server console script the README's uvx block runs.
02 / THE REVIEW RECORD
What we actually inspected.
Source review has boundaries.
A clear record is more useful than a “safe” badge.
Material inspected
- README.md at c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6
- LICENSE, pyproject.toml, src/zilliz_mcp_server/settings.py and server.py at the same commit
Our findings
- server.py takes --transport (default stdio); settings.py defaults ZILLIZ_CLOUD_URI to https://api.cloud.zilliz.com and the free-cluster region to gcp-us-west1, and loads .env only without overriding existing variables.
- The README's stdio block carries a note about replacing /path/to/your/zilliz-mcp-server that the block itself does not use.
Not established by this review
- uvx launch
- Any Zilliz Cloud or Milvus call
- create_free_cluster
The review applies to the material and revision named here. A newer upstream release can change its behavior.
03 / PUT IT TO WORK
Connect a server deliberately.
- The README gives a client block rather than a one-line command: command uvx with args zilliz-mcp-server and ZILLIZ_CLOUD_TOKEN in env. It was not run.
- For HTTP mode, set ZILLIZ_CLOUD_TOKEN (the variable settings.py reads) before running the README's uv run command. Do not commit the token.
Before you start
- uv and Python 3.10 or later
- A Zilliz Cloud account and API key
Documented configuration example
Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.
{
"mcpServers": {
"zilliz-mcp-server": {
"command": "uvx",
"args": [
"zilliz-mcp-server"
],
"env": {
"ZILLIZ_CLOUD_TOKEN": "your-token-here"
}
}
}
} 04 / FOLLOW THE EVIDENCE
The source trail.
Our notes are separate from the original resource.
Check upstream before adopting a new version.
- Zilliz MCP README ↗Checked
https://github.com/zilliztech/zilliz-mcp-server/blob/c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6/README.md
Supports: Tools, stdio and Streamable HTTP setup
- Zilliz MCP settings.py ↗Checked
https://github.com/zilliztech/zilliz-mcp-server/blob/c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6/src/zilliz_mcp_server/settings.py
Supports: ZILLIZ_CLOUD_TOKEN requirement, Defaults
- Zilliz MCP server.py ↗Checked
https://github.com/zilliztech/zilliz-mcp-server/blob/c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6/src/zilliz_mcp_server/server.py
Supports: Transport flag
- Zilliz MCP pyproject.toml ↗Checked
https://github.com/zilliztech/zilliz-mcp-server/blob/c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6/pyproject.toml
Supports: Description, Package 1.0.0, License Apache-2.0
- Zilliz MCP LICENSE ↗Checked
https://github.com/zilliztech/zilliz-mcp-server/blob/c2a84e1779d87aa2ba7098b6609f8a3cb529c4e6/LICENSE
Supports: Apache License 2.0