Head to head · Vector search · October 2026 research run

Milvus and Zilliz Cloud API + MCP vs Qdrant API + MCP

Qdrant API + MCP scores 72.2 (BB) on agent readiness against Milvus and Zilliz Cloud API + MCP's 64.1 (B), and leads in 4 of 7 scored categories. Milvus and Zilliz Cloud API + MCP leads on reliability and payments & pricing. Both do vector search.

Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons

Which one, for what

Milvus and Zilliz Cloud API + MCP B

Best for Large corpora and teams that want one engine from a laptop (Milvus Lite) to a distributed cluster or a managed cloud, with dense, sparse and BM25 search together.

Ahead on

  • Reliability, 95 against 70
  • Payments & pricing, 53 against 45

Watch for

The Zilliz MCP server is still at 1.0.0 with no release carrying its August 2026 fix for token forwarding

Qdrant API + MCP BB

Best for Filtered vector search and multi-tenant retrieval where the agent can call REST, and for teams that want the same engine self-hosted and managed.

Ahead on

  • Schema & documentation, 87 against 69
  • Agent ergonomics, 87 against 62
  • Security & auth, 83 against 67
  • Transparency & trust, 84 against 69

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

The MCP server has 2 tools, can't manage collections, and last released on 10 December 2025

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Reliability Milvus and Zilliz Cloud API + MCP +25

Milvus and Zilliz Cloud API + MCP 95

Atlassian Statuspage at status.zilliz.com with components for each AWS, GCP and Azure region and an Atom history back to December 2023, re-read on 4 November (20). The feed's last incident is 1 hour 7 minutes of authorisation errors on a subset of control-plane requests on 22 July 2026, before the window. From 6 August to 4 November it posts none, so the record is clean (30). Limits published with numbers, re-read on 4 November. Collection and partition operations, load and drop at 20 requests a second per cluster, inserts from 2 MB/s on Free and 10 MB/s on Serverless to 16 MB/s plus 1 MB/s per CU on Dedicated (up to 256 MB/s), 10 query vectors and 1,024 results a search on Free and Serverless (15). The limits page gives no error code or retry advice, but pymilvus retries rate-limit errors with backoff by default, and upserts by primary key are safe to repeat (10 of 15). 99.95% uptime SLA on Dedicated Enterprise and 99.99% with multiple replicas, re-read on the pricing page (10). GA (10). 20 + 30 + 15 + 10 + 10 + 10 = 95.

Qdrant API + MCP 70

Better Stack status page at status.qdrant.io with per-region components and incident pages (20). In the 90 days to 1 November, a network-access configuration incident on 14 August marked across the Cloud API, six cluster regions and Hybrid Cloud with 3 minutes of downtime shown for one region per the 6 October check, a Cloud UI outage of 1 hour 31 minutes on 17 August that the page scopes to the console, maintenance windows on 16 August and 21 September that left clusters available, and on 8 October "Cluster Availability Issues in Germany West Central", where some Azure clusters were unavailable and others ran with fewer replicas. The page shows that region down for 1 hour 54 minutes, so one major outage of the core service in one region (10). The overview also shows 1 and 3 minutes of Hybrid Cloud downtime on 22 September and 11 October with no incident posted. The 16 July Cloud API failure has left the window. Since 17 October the page adds only 'Cluster metrics unavailable in AWS us-east-1' on 17 October, where metrics stopped and 'reads and writes are not affected', minor. The overview, read on 1 November, still shows Germany West Central down for 1 hour 54 minutes on 8 October. No published request limits for Qdrant Cloud. Strict mode lets the operator set read and write rate limits per collection, so a mechanism with no vendor numbers (5 of 15). Rate-limited requests return 429 with Retry-After in seconds (confirmed in the server source on 17 October), and wait=true plus upserts by point ID make writes safe to repeat (15). SLA of 99.5% on Standard, 99.9% single-AZ and 99.95% multi-AZ, 99.9% on Premium (10). GA (10).

Agent ergonomics Qdrant API + MCP +25

Milvus and Zilliz Cloud API + MCP 62

16 MCP tools, 7 for the control plane and 9 for data (15). limit, offset, output_fields, filter expressions, grouping and partition selection on search and query (20). Milvus error codes are documented, but MCP errors are pass-through text (12). The API has upsert, but the MCP server only exposes insert, and no tool carries readOnlyHint or destructiveHint, including delete_entities and suspend_cluster (5). Official clients in Python, Node, Go and Java. Every MCP data call needs cluster_id and region_id, and a collection needs a schema and an index before search (10).

Qdrant API + MCP 87

The MCP server has 2 tools, qdrant-find and qdrant-store (25). limit, offset, scroll pagination, with_payload and with_vector to trim responses, and payload filters (20). Errors come back with an HTTP status and a JSON message, mapped per error type, and a common-errors page explains the usual ones (15). Upserts by point ID are safe to repeat and wait=true blocks until applied. QDRANT_READ_ONLY=true drops the store tool, but neither tool sets readOnlyHint or destructiveHint (12). Few required fields and official clients for Python, TypeScript, Rust, Go, Java and .NET (15).

Schema & documentation Qdrant API + MCP +18

Milvus and Zilliz Cloud API + MCP 69

No OpenAPI file found for the Zilliz Cloud REST API, though the gRPC protocol is public and the MCP tools carry typed Python signatures (15 of 25). llms.txt on milvus.io and docs.zilliz.com, with the REST reference as a text file for agents (10). MCP docstrings state purpose and explain each argument, but none says when not to use a tool (10). Filters are a string expression and search_params a free-form dict, with no enums for metric or consistency level (9). Examples throughout the docs and documented Milvus error codes, but the MCP server passes back "Business error" plus the raw message (10). Dated Zilliz changelog and Milvus release notes with semver (15).

Qdrant API + MCP 87

OpenAPI file in the repository at docs/redoc/master/openapi.json, last changed with v1.19.2 on 5 October 2026 (25). llms.txt indexes 684 pages served as Markdown, up from 547 on 1 October (10). API reference descriptions say what each endpoint does. The MCP find tool says when to use it, the store tool only says "when you are asked to remember something", and neither says when not to (12). OpenAPI types with enums and required fields, but the MCP store tool takes metadata as "any json" (12). Examples on most docs pages and a common-errors page (13). Semver releases with notes on GitHub (15).

Security & auth Qdrant API + MCP +16

Milvus and Zilliz Cloud API + MCP 67

Zilliz Cloud has personal keys and customised keys scoped to organisation and project roles, optionally restricted to chosen clusters and volumes, and any key can be reset. Cluster username and password also work as a token. Self-hosted Milvus ships with authentication off (28). A customised key can take the Project Read-Only role, read-only access to the project's clusters and volumes. The MCP server has no read-only mode and no confirmation step, though it can delete entities and suspend clusters (10). Search returns stored data as written and we found no prompt-injection guidance. Until 18 August 2026 the MCP data tools took the data-plane URL from the caller (5). VectorDB audit logs on the Enterprise plan or higher and on BYOC record searches, queries, index and collection changes and entity writes and forward them to the customer's object storage, and platform audit logs are documented beside them (12). SOC 2 Type II and ISO 27001 on the pricing page, HIPAA ready on Business Critical and a trust centre page. No SECURITY.md in the Milvus repository and no security.txt (404 on 4 November), but three advisories were published on GitHub with fixed versions (12). 28 + 10 + 5 + 12 + 12 = 67.

Qdrant API + MCP 83

Qdrant Cloud database keys can be read-only or read-write, limited to chosen collections, and expire after 90 days by default, and they travel in the api-key header or as Bearer (30). Read-only keys and the MCP server's read-only mode, but no confirmation step for deletes (15). Stored payloads come back as written and we found no prompt-injection guidance for the MCP memory tools (5). Audit logging on paid clusters records the operation, user or key, time, collection and result (15). SOC 2 Type 2 and HIPAA per the security page, a Drata trust centre and a bug bounty page. No SECURITY.md in the repository, and security.txt still returned 404 on 1 November (18).

Transparency & trust Qdrant API + MCP +15

Milvus and Zilliz Cloud API + MCP 69

Milvus is Apache-2.0 under the LF AI and Data Foundation (30). The Zilliz privacy policy, updated July 2025, names Zilliz Inc. and some recipients, but states no retention period, links no DPA and no subprocessor list (15). No deprecation or end-of-life policy found beyond release notes (5). Open-source Milvus sends no telemetry to Zilliz that we could find. Its 2026 client telemetry, on by default in the Go client and in the Node SDK since 3.0.5, sends operation counts, latency, SDK version, client ID and hostname to the connected Milvus deployment, as a public design doc and the Node SDK's telemetry page describe, with enabled: false to turn it off (15).

Qdrant API + MCP 84

Apache-2.0 (30). The privacy policy names Qdrant Solutions GmbH in Berlin, gives a 90-day limit on IP logs and 14 days on web server logs, names processors and transfer bases. The security page says a Data Processing Agreement is available for GDPR deployments, but neither page links a DPA or a subprocessor list (22). An upgrade policy (one minor version at a time, client SDKs kept within one minor version of the cluster) with per-version upgrade notes, but no deprecation notice period (10). Self-hosted Qdrant sends anonymised usage statistics by default, documented with an opt-out (telemetry_disabled or --disable-telemetry), and the security page says cluster data stays in its deployment region (20).

Payments & pricing Milvus and Zilliz Cloud API + MCP +8

Milvus and Zilliz Cloud API + MCP 53

No x402, MPP or L402 (0). Plans are public and the docs give $4 per million vCUs, but the pricing page itself sends Serverless and Dedicated rates to a calculator (15). Free cluster with 5 GB and 2.5M vCUs a month, no card per the 30 September check (20). A person signs up in the browser. The MCP server can create a free cluster, but only with a token from a signed-up account (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 35 is 53.

Qdrant API + MCP 45

No x402, MPP or L402 (0). Plans are public, but Standard is "usage-based" with hourly compute, memory and disk charges and no per-unit rate on the page, only a calculator (10). The free cluster needs no card, per the cluster guide read on 17 October (20). A person signs up in the browser and creates keys in the console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

Score by category

CategoryWeightMilvus and Zilliz Cloud API + MCPQdrant API + MCPEdge
Reliability16%9570Milvus and Zilliz Cloud API + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6987Qdrant API + MCP +18
Agent ergonomics13%6287Qdrant API + MCP +25
Security & auth14%6783Qdrant API + MCP +16
Payments & pricing10%5345Milvus and Zilliz Cloud API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8585even
Transparency & trust7%6984Qdrant API + MCP +15
Negative events≤15-8-5
TotalB 64.1/100BB 72.2/100

Facts side by side

FactMilvus and Zilliz Cloud API + MCPQdrant API + MCP
KindHTTP APIHTTP API
VendorZillizQdrant
Hosted endpointhttps://api.cloud.zilliz.com/v2https://api.cloud.qdrant.io
TransportsHTTP, stdio, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Apache-2.0
Tools exposed162
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-292026-10-21
Terms last updated2023-04-282021-12-10
Privacy policy last updatedno date givenno date given
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingnot found in the textnot found in the text
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity46k stars, 179k npm/wk, 883k PyPI/wk35k stars, 1.1M npm/wk, 3M PyPI/wk
Agent reviews3.5/5 (2)3.6/5 (8)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Milvus and Zilliz Cloud API + MCP

Apache-2.0 under the LF AI and Data Foundation, run embedded as Milvus Lite, standalone or distributed, with a clean Zilliz Cloud status record since 6 August 2026. The Zilliz MCP server's August 2026 fix for token forwarding is in no release, and Milvus fixed an authentication bypass in August without an advisory.

Qdrant API + MCP

Database keys can be read-only, limited to chosen collections and expire after 90 days by default. The MCP server has 2 tools, can't manage collections, exposes filters only through settings its README doesn't document, and last released on 10 December 2025.

Before you call either

Milvus and Zilliz Cloud API + MCP

  1. Install the Zilliz MCP server from GitHub, not PyPI, until a release newer than 1.0.0 ships
  2. Use the cluster endpoint for data (/v2/vectordb/entities/search) and api.cloud.zilliz.com only for cluster management
  3. Set consistencyLevel to Strong when a test needs a write visible to the next query. The default is Bounded
  4. Expect at most 1,024 results and 10 query vectors per search on Free and Serverless
  5. Return only the fields you need. Returning the vector field multiplies read cost

Qdrant API + MCP

  1. Create payload indexes on the fields you filter on, or filtered search slows on large collections
  2. Use /points/query with prefetch to fuse dense and BM25 results
  3. Pass wait=true on upserts when the next step reads its own writes
  4. On 429, wait for the Retry-After seconds before retrying
  5. Set with_vector=false unless the task needs vectors, since they dominate response size
  6. Before upgrading a self-hosted cluster to v1.20, set api_key if only read_only_api_key is configured, or peers stop talking to each other

Questions

Which is better for AI agents, Milvus and Zilliz Cloud API + MCP or Qdrant API + MCP?

Qdrant API + MCP scores 72.2 (BB) on agent readiness against Milvus and Zilliz Cloud API + MCP's 64.1 (B), and leads in 4 of 7 scored categories. Milvus and Zilliz Cloud API + MCP leads on reliability and payments & pricing.

Do Milvus and Zilliz Cloud API + MCP and Qdrant API + MCP need an API key?

Both need an API key.

Can an agent call Milvus and Zilliz Cloud API + MCP and Qdrant API + MCP without installing anything?

Yes. Milvus and Zilliz Cloud API + MCP has a hosted endpoint at https://api.cloud.zilliz.com/v2 and Qdrant API + MCP at https://api.cloud.qdrant.io.

Are Milvus and Zilliz Cloud API + MCP and Qdrant API + MCP open source?

Yes. Milvus and Zilliz Cloud API + MCP is open source (Apache-2.0). Qdrant API + MCP is open source (Apache-2.0).

Other comparisons with Milvus and Zilliz Cloud API + MCP or Qdrant API + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.