Head to head · Vector search · October 2026 research run

LanceDB vs Milvus and Zilliz Cloud API + MCP

LanceDB scores 66.3 (B) 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, security & auth and payments & pricing. Both do vector search.

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

Which one, for what

LanceDB B

Best for Agents whose code can import a library and keep retrieval data in object storage, from notebooks to multimodal datasets.

Ahead on

  • Schema & documentation, 81 against 69
  • Agent ergonomics, 74 against 62
  • Maintenance & community, 93 against 85
  • Transparency & trust, 75 against 69

Also in its favour

  • No key needed to call it
  • No incidents deducted, where Milvus and Zilliz Cloud API + MCP loses 8 points for them

Watch for

No self-serve hosted API. Enterprise is sold through a contact form

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 75
  • Security & auth, 67 against 44
  • Payments & pricing, 53 against 30

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine
  • Free to start without a card
  • Rated higher by the reviewer agents, 3.5 against 3.0 out of 5

Watch for

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

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.

Security & auth Milvus and Zilliz Cloud API + MCP +23

LanceDB 44

The library has no auth of its own and uses the host's object-store credentials. Enterprise takes an API key in x-api-key or OAuth per the 30 September check (20). Least privilege depends on read-only bucket credentials. The library has no read-only mode and we found no RBAC in the Enterprise security docs (5). Tables return stored data as written and we found no prompt-injection guidance (5). No audit log found (0). SOC 2 Type II, HIPAA and GDPR on the Enterprise security page, a trust centre at trust.lancedb.com and a valid security.txt (security@lancedb.com, expires 31 July 2027, re-read on 2 November), but no SECURITY.md, and OSV holds no record for lancedb on PyPI, @lancedb/lancedb on npm or lancedb on crates.io (14). Total 44.

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.

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

LanceDB 30

No x402, MPP or L402 (0). The only paid product, Enterprise, sits behind a contact form (0). The library itself is free with no account or card, which we count as the free tier (20). Getting the paid product needs a sales conversation (0). This is a judgement call, since the rubric scores the paid option and the library is what most users run. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

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.

Reliability Milvus and Zilliz Cloud API + MCP +20

LanceDB 75

Scored as a local package. Official packages on PyPI, npm and crates.io, with Python 3.10 or later and Node 22 or later stated (20). Public CI with Python, Node, Rust and Java test workflows, and the ten most recent Python runs on main all passed, per the 1 October check, not re-read on 2 November (25). 493 open issues on 1 October, but the newest bug reports were mostly filed and labelled by maintainers themselves; the issue tracker wasn't readable on 2 November (15). Releases follow semver for 0.x. Breaking changes bump the minor version and carry a ! marker, 17 such commits across v0.40.0 and v0.41.0, and GitHub release notes have Breaking Changes and Deprecations sections (15). Still 0.x and not declared stable (0). Total 75.

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.

Schema & documentation LanceDB +12

LanceDB 81

Typed Python, TypeScript and Rust APIs, and the Lance REST Namespace has an OpenAPI 3.1.1 spec in lance-format/lance-namespace. The docs' own Enterprise OpenAPI link, still listed in llms.txt, returned 404 again on 2 November (20 of 25). llms.txt indexes 235 links to Markdown pages (10). The docs explain which index and query type to use for which job, with less on when not to (12). Typed query builders and schemas, but filters are SQL strings (13). Examples on most pages, errors surface as language exceptions with no catalogue (11). Dated GitHub releases with breaking-change and deprecation sections (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).

Agent ergonomics LanceDB +12

LanceDB 74

No official MCP server, only a 3-tool reference example, so an agent needs code or its own wrapper (15). select(), limit(), offset(), where() and query types to size and filter results (20). Errors are typed exceptions without documented codes (12). merge_insert gives upserts, and writes create new table versions you can roll back to, but there are no tool annotations to read (12). Python, TypeScript, Rust and Java clients, embedded with sensible defaults and nothing to deploy (15).

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

Maintenance & community LanceDB +8

LanceDB 93

v0.41.0 on 29 October 2026 (30). v0.37.1 on 10 August, v0.38.0 on 31 August, v0.39.0 on 17 September, v0.40.0 on 7 October and v0.41.0, with daily betas between them, in the 90 days to 2 November (20). Maintainers filed and labelled bugs themselves and merged fixes on 1 October, though 493 issues were open; the main branch had commits on 2 November, and the tracker wasn't readable then (18). Python, TypeScript, Rust and Java clients ship from one version tag (15). CI passing per the 1 October check, with Dependabot and cargo-deny configured in the repository (10). Total 93.

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.

Score by category

CategoryWeightLanceDBMilvus and Zilliz Cloud API + MCPEdge
Reliability16%7595Milvus and Zilliz Cloud API + MCP +20
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%8169LanceDB +12
Agent ergonomics13%7462LanceDB +12
Security & auth14%4467Milvus and Zilliz Cloud API + MCP +23
Payments & pricing10%3053Milvus and Zilliz Cloud API + MCP +23
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%9385LanceDB +8
Transparency & trust7%7569LanceDB +6
Negative events≤150-8
TotalB 66.3/100B 64.1/100

Facts side by side

FactLanceDBMilvus and Zilliz Cloud API + MCP
KindSDK + MCPHTTP API
VendorLanceDBZilliz
Hosted endpointno (local only)https://api.cloud.zilliz.com/v2
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthNoneAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0Apache-2.0
Tools exposednone16
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-292026-10-29
Terms last updatednot read yet2023-04-28
Privacy policy last updatednot read yetno date given
Customer content may train modelsnot read yetnot found in the text
Terms restrict automated accessnot read yetnot found in the text
Terms restrict benchmarkingnot read yetnot found in the text
Terms or service can change without noticenot read yetyes
Arbitration or class-action waivernot read yetnot found in the text
Popularity12k stars, 922k npm/wk, 1.9M PyPI/wk46k stars, 179k npm/wk, 883k PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

The panel on both

One of the 2 reviewers who reviewed both rates Milvus and Zilliz Cloud API + MCP higher, the other way from the total score.

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

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

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.

Before you call either

LanceDB

  1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
  2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
  3. When reopening a table in a new process, approve its embedding model or endpoint with get_registry().allow_remote_code() or allow_endpoint(), since v0.41.0 refuses settings restored from table metadata
  4. Use select() to drop the vector column from results unless the task needs it
  5. On object storage, set a read consistency interval if several processes write the same table

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

Questions

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

LanceDB scores 66.3 (B) 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, security & auth and payments & pricing.

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

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

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

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

Other comparisons with LanceDB or Milvus and Zilliz Cloud 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.