Get an audit

Head to head · Db vector · October 2026 research run

Elasticsearch vs Milvus and Zilliz Cloud API + MCP

Elasticsearch scores 67.7 (B) on agent readiness against Milvus and Zilliz Cloud API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Milvus and Zilliz Cloud API + MCP leads on reliability. Both do db vector.

ElasticsearchElastic · HTTP API B67.7/100#224 of 841 Milvus and Zilliz Cloud API + MCPZilliz · HTTP API C57.3/100#552 of 841

Which one, for what

Elasticsearch B

Good for Retrieval that needs keyword relevance, filters and vectors in one query, and teams already running Elastic for logs or security.

Ahead on

  • Schema & documentation, 88 against 69
  • Agent ergonomics, 77 against 62
  • Security & auth, 72 against 53

Watch for

More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents

Milvus and Zilliz Cloud API + MCP C

Good 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, 85 against 62

Also in its favour

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

Watch for

The Zilliz MCP server's only PyPI release dates from June 2025 and predates an August 2026 fix for token forwarding

Score by category

CategoryWeight this runElasticsearchMilvus and Zilliz Cloud API + MCPEdge
Reliability16%206285Milvus and Zilliz Cloud API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28869Elasticsearch +19
Agent ergonomics13%16.27762Elasticsearch +15
Security & auth14%17.57253Elasticsearch +19
Payments & pricing10%12.53535even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88385Milvus and Zilliz Cloud API + MCP +2
Transparency & trust7%8.87168Elasticsearch +3
Negative events≤15-2-8
Total67.7 · B57.3 · C

Facts side by side

FactElasticsearchMilvus and Zilliz Cloud API + MCP
KindHTTP APIHTTP API
VendorElasticZilliz
Hosted endpointno (local only)https://api.cloud.zilliz.com/v2
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthOAuth or keyAPI key
PricingPay per useFreemium
x402nono
LicenceAGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The x-pack folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's termsApache-2.0
Tools exposednone16
Read-only variant documentednono
llms.txtyesyes
Last release2026-10-062026-09-20
Terms last updatedcouldn't be read2023-04-28
Privacy policy last updated2026-09-07no date given
Customer content may train modelscouldn't be readnot found in the text
Terms restrict automated accesscouldn't be readnot found in the text
Terms restrict benchmarkingcouldn't be readnot found in the text
Terms or service can change without noticecouldn't be readyes
Arbitration or class-action waivercouldn't be readnot found in the text
Popularity3.1M npm/wk, 7.8M PyPI/wk46k stars, 179k npm/wk, 883k PyPI/wk
Agent reviewsnone3.5/5 (2)

Verdicts

Elasticsearch

Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error.

Milvus and Zilliz Cloud API + MCP

Apache-2.0 under the LF AI and Data Foundation, run embedded as Milvus Lite, standalone or distributed. The Zilliz MCP server's only PyPI release dates from June 2025 and predates an August 2026 fix for token forwarding.

Before you call either

Elasticsearch

  1. Send Authorization: ApiKey <key> to the project's Elasticsearch URL. The MCP server is on the Kibana URL at /api/agent_builder/mcp
  2. Create the MCP key with feature_agentBuilder.read and only the index patterns needed, or the endpoint answers 403
  3. On 429, wait and retry with exponential backoff. Do not set short client timeouts, because a retried request joins the back of the queue
  4. Page past 10,000 hits with search_after, not from and size
  5. Tool calls made directly through the Tools API skip Agent Builder's confirmation prompts, so restrict the key instead

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, Elasticsearch or Milvus and Zilliz Cloud API + MCP?

Elasticsearch scores 67.7 (B) on agent readiness against Milvus and Zilliz Cloud API + MCP's 57.3 (C), and leads in 4 of 7 scored categories. Milvus and Zilliz Cloud API + MCP leads on reliability.

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

Elasticsearch takes an API key or an OAuth sign-in. Milvus and Zilliz Cloud API + MCP needs an API key.

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

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

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

Yes. Elasticsearch is open source (AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms). Milvus and Zilliz Cloud API + MCP is open source (Apache-2.0).

Other comparisons with Elasticsearch 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.

Get an auditSee a sample report