Head to head · Vector search · October 2026 research run

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

Milvus and Zilliz Cloud API + MCP scores 64.1 (B) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 1 of 7 scored categories. Weaviate API + MCP leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community. 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 35

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

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

Weaviate API + MCP C

Best for Hybrid keyword and vector retrieval with filters and multi-tenancy, self-hosted or managed, and for agents that work over MCP.

Ahead on

  • Schema & documentation, 84 against 69
  • Agent ergonomics, 95 against 62
  • Security & auth, 80 against 67
  • Payments & pricing, 60 against 53
  • Maintenance & community, 90 against 85

Watch for

No public status page or incident history

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 +60

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.

Weaviate API + MCP 35

No public status page. status.weaviate.io still doesn't resolve, and status.weaviate.cloud (incident.io, titled "Weaviate Enterprise Status") shows a page-not-found body and an empty feed.atom on 1 November (0). No readable history (5). No request limits published for the database. The only numbers are on the AI services (Embeddings 2,000 requests a day and Query Agent 1,000 a month on Free) and a 60-second request timeout on Weaviate Cloud, now stated on the MCP page too (5 of 15). No 429 or backoff guidance found, but the import docs tell you to use deterministic UUIDs so a retried write can't duplicate objects, per the 1 October check (5 of 15). SLA of 99.5% on Flex and up to 99.95% on Premium (10). The database API is GA. The MCP docs page carries "Added in v1.38" with no preview label, though llms.txt still calls the MCP server a preview (10). 0+5+5+5+10+10 = 35.

Agent ergonomics Weaviate API + MCP +33

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).

Weaviate API + MCP 95

4 MCP tools (25). limit, return_properties, return_metadata, target_properties, filters and tenants on hybrid search, plus a cursor API for paging through a collection (20). The MCP page now documents each error an agent meets, with its code and text (401 with a JSON body for a bad key, 400 listing supported protocol versions, 503 when the server is off, isError results for permission failures, invalid arguments and disabled writes, and the 60-second cut-off). No catalogue for the REST API (15). Every tool sets readOnlyHint, destructiveHint and idempotentHint, and the write tool is hidden from tools/list until write access is enabled (20). Only query and collection_name are required. Official clients for Python, TypeScript, Go, Java and C# (15). 25+20+15+20+15 = 95.

Schema & documentation Weaviate API + MCP +15

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).

Weaviate API + MCP 84

Swagger 2.0 file at docs.weaviate.io/openapi.json covers REST only, and search and bulk import run over gRPC. All 4 MCP tools have typed JSON Schema inputs (22). llms.txt (10). MCP descriptions are one line each, such as "Performs hybrid search combining vector similarity and keyword matching (BM25).", with nothing on when to use or avoid a tool. Operators can override them in a config file (10). Typed inputs with required fields, an operator enum in the filter schema, alpha bounded 0 to 1 with a 0.75 default and limit defaulting to 100 (13). Code examples on most docs pages, and the MCP page now has an "Errors and limits" section giving the 401, 400, 503 and isError answers with their text. REST error responses are still documented unevenly (14). Semver releases and dated release notes (15). 22+10+10+13+14+15 = 84.

Security & auth Weaviate API + MCP +13

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.

Weaviate API + MCP 80

Weaviate Cloud keys are created per cluster with an RBAC role (admin, viewer or custom), and can be rotated and deleted. Self-hosted instances add OIDC (30). Viewer roles, write tools off by default on self-hosted MCP and a read-only switch on Weaviate Cloud, though that switch is off by default (18). Search returns stored objects as written and the MCP docs give no prompt-injection guidance (5). With RBAC on, authorisation decisions and role changes are written to an audit log, with source IP, and the MCP server exports six Prometheus metrics. Not a full per-call log (10). SOC 2 Type II and HIPAA on the pricing page, a trust portal at trust.weaviate.io, a Vulnerability Disclosure Program report form, and advisories published on the Weaviate blog with severity, affected versions and fixes (7 November 2025, 1 and 15 October 2026). No bug bounty found, no SECURITY.md and no security.txt. novu takes 17 for the same record with ISO 27001 added, so 17 here at most (17). 30+18+5+10+17 = 80.

Payments & pricing Weaviate API + MCP +7

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.

Weaviate API + MCP 60

No x402, MPP or L402 (0). Per-unit prices published without login, from $0.00465 per million vector dimensions and $0.12 per GiB stored on Flex, with Premium rates listed too (20). Free cluster with no card required, 100,000 objects and 1 collection (20). A person signs up in the browser and creates a key per cluster (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Maintenance & community Weaviate API + MCP +5

Milvus and Zilliz Cloud API + MCP 85

Milvus v3.0.5 tagged on 29 October and v2.6.26 on 23 October 2026 (30). In the 90 days from 6 August, v2.6.23 to v2.6.26 and v3.0.1 to v3.0.5, plus pymilvus 3.0.2 and the Node SDK 3.0.5 and 3.0.6 (20). 1,100 open issues with kind and difficulty labels on new ones, few assignees visible, per the 1 October check (15). pymilvus 3.0.2 and the Node SDK 3.0.6 (both 18 September) follow the 3.0 server (15). 21 CI workflows including code checks, licence checks and weekly releases (10). Less 5 because the Zilliz MCP server is still at version 1.0.0 with no tag, and its only PyPI release, 1.0.0 from 30 June 2025 per the 1 October check, predates the August security fix. 30 + 20 + 15 + 15 + 10 - 5 = 85.

Weaviate API + MCP 90

v1.40.3 tagged on 28 October 2026, with v1.39.14 and v1.38.23 on 27 October (30). Dozens of patch releases across three supported minors since 3 August, with v1.40.0 on 6 October after three release candidates from 15 September (20). Issue replies per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: 456 open issues, the newest bug reports answered within weeks (15). Official clients in five languages, Python 4.24.1 on 26 October and TypeScript 3.15.2 on 27 October (15). CI on pull requests with a linter and a security lint workflow, per the 1 October check (10). 30+20+15+15+10 = 90.

Score by category

CategoryWeightMilvus and Zilliz Cloud API + MCPWeaviate API + MCPEdge
Reliability16%9535Milvus and Zilliz Cloud API + MCP +60
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6984Weaviate API + MCP +15
Agent ergonomics13%6295Weaviate API + MCP +33
Security & auth14%6780Weaviate API + MCP +13
Payments & pricing10%5360Weaviate API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8590Weaviate API + MCP +5
Transparency & trust7%6973Weaviate API + MCP +4
Negative events≤15-8-12
TotalB 64.1/100C 59.9/100

Facts side by side

FactMilvus and Zilliz Cloud API + MCPWeaviate API + MCP
KindHTTP APIHTTP API
VendorZillizWeaviate
Hosted endpointhttps://api.cloud.zilliz.com/v2no (local only)
TransportsHTTP, stdio, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0BSD-3-Clause (some parts under the Weaviate License)
Tools exposed164
Read-only variant documentedyesyes
llms.txtyesyes
Last release2026-10-292026-10-28
Terms last updated2023-04-282026-05-01
Privacy policy last updatedno date given2024-02-01
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 textyes
Terms or service can change without noticeyesyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity46k stars, 179k npm/wk, 883k PyPI/wk17k stars, 406k npm/wk, 2.3M PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (2)

The panel on both

The 2 reviewers who reviewed both rate them the same.

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.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, full annotations and documented error answers, and write tools hidden until enabled on self-hosted instances. Weaviate posts security advisories on its blog, three in the last year, but one released authentication fix in October carried none. No public status page or incident history.

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

Weaviate API + MCP

  1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
  2. Set return_properties on weaviate-query-hybrid, since every property comes back in full otherwise and limit defaults to 100
  3. Turn on Enable MCP Read-Only in Weaviate Cloud, or use a viewer key, before giving an agent the MCP endpoint
  4. Check collection names before an upsert, because auto-schema creates a new collection from a typo
  5. Move GraphQL queries to the clients or the REST Search API before 1 December 2026 on Weaviate Cloud

Questions

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

Milvus and Zilliz Cloud API + MCP scores 64.1 (B) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 1 of 7 scored categories. Weaviate API + MCP leads on schema & documentation, agent ergonomics, security & auth, payments & pricing and maintenance & community.

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

Both need an API key.

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

Milvus and Zilliz Cloud API + MCP has a hosted endpoint at https://api.cloud.zilliz.com/v2. No hosted endpoint is listed for Weaviate API + MCP.

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

Yes. Milvus and Zilliz Cloud API + MCP is open source (Apache-2.0). Weaviate API + MCP is open source (BSD-3-Clause (some parts under the Weaviate License)).

Other comparisons with Milvus and Zilliz Cloud API + MCP or Weaviate 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.