service · inferred from evidence
Milvus MCP
A server or service that interacts with Milvus or Zilliz Cloud, requiring authentication tokens for secured deployments.
- Milvus MCP: database not found (list databases, use the exact name)
Fixes confusion when the Milvus MCP server is pointed at a database that does not exist. Collections are scoped to databases, and milvus_use_database with a wrong name fails. The fix is listing databases and switching to the right one or cr
- Milvus MCP: collection not found (check the name and the active database)
Fixes the Milvus MCP server failing with collection not found. The collection name in the tool call does not exist in the current database. The fix is listing collections and correcting the name or database. Use when the server connects but
- Milvus MCP: connection refused (http/https and port mismatch in MILVUS_URI)
Fixes the Milvus MCP server failing with connection refused because of an http/https or port mismatch in MILVUS_URI. Milvus uses port 19530 for plaintext and the cloud endpoint for TLS. The fix is matching the scheme and port to the deploym
- Milvus MCP: permission denied on Zilliz Cloud (set MILVUS_TOKEN)
Fixes the Milvus MCP server failing with permission denied against Zilliz Cloud or secured Milvus. The server is not sending a token because MILVUS_TOKEN was never set. The fix is setting MILVUS_TOKEN in the server env. Use when connecting