Head to head · Vector search · October 2026 research run

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

Milvus and Zilliz Cloud API + MCP scores 64.1 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 5 of 7 scored categories. Chroma API + MCP leads on agent ergonomics and transparency & trust. Both do vector search.

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

Which one, for what

Chroma API + MCP D

Best for Agent memory and small to mid-sized corpora where an in-process store or a serverless bill by the GiB suits.

Ahead on

  • Agent ergonomics, 73 against 62
  • Transparency & trust, 74 against 69

Watch for

Six advisories against chromadb, two Critical and four High, have no patched release as of 5 November 2026

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 60
  • Security & auth, 67 against 42
  • Payments & pricing, 53 against 45
  • Maintenance & community, 85 against 35

Also in its favour

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

Maintenance & community Milvus and Zilliz Cloud API + MCP +50

Chroma API + MCP 35

Newest release is the JavaScript client 3.5.0 on 30 June 2026, per the 1 October check, 128 days before this one. The server and Python package last tagged 1.5.9 on 4 May 2026 (10). Nothing tagged or dated in the 90 days from 7 August. A commit on 13 October set the version to 1.6.0 ("Bug fix release"), but no 1.6.0 tag exists and PyPI couldn't be read, so it isn't counted (0). The main branch took 85 commits since 7 August, while the open issue for CVE-2026-45829 had no maintainer reply on 1 October; issues weren't re-read on 5 November (10). Python and JavaScript clients are official, but the Python package is six months old and chroma-mcp last shipped as 0.2.6 on 14 August 2025, pinned to chromadb 1.0.16, and isn't in the official MCP registry (10). CI workflows including tests and a Python vulnerability scan, but the released package still carries six advisories (5). 10 + 0 + 10 + 10 + 5 = 35.

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.

Reliability Milvus and Zilliz Cloud API + MCP +35

Chroma API + MCP 60

Instatus page at status.trychroma.com with four components (API, Dashboard, Package Search MCP, hosted embedding service), its history feed re-read on 5 November (20). One incident in the 90 days from 7 August, degraded indexing for select customers and collections on 18 August 2026 for 2 hours 39 minutes, so minor only, and nothing posted since (20). Chroma Cloud quotas are published with numbers, but as concurrency and size caps (10 concurrent reads and 10 writes per collection, 300 records a write, 300 results a query), not as requests a second (10 of 15). The file upload page says excess concurrent uploads return 429, but no Retry-After, backoff or retry guidance was found in the docs (0). Enterprise lists "SLAs" with no figure, and nothing for Team (0). Chroma Cloud isn't marked beta or preview (10). 20 + 20 + 10 + 0 + 0 + 10 = 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.

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

Chroma API + MCP 42

Chroma Cloud keys go in x-chroma-token and are tied to a tenant and database per the 30 September check, with no other scopes found. A local or self-hosted server runs with no auth unless configured (20). No read-only key, and the MCP server has no read-only mode, though a key limited to one database narrows the reach (5). Stored documents come back as written, including pages pulled in by Sync from the web, and we found no prompt-injection guidance (5). No audit log found (0). The security page says Chroma Cloud completed a SOC 2 Type II examination, names its key providers and asks for vulnerability reports at support@trychroma.com, with no acknowledgement time. No security.txt or bug bounty found, the MCP repository's SECURITY.md still has a "[your-email]" placeholder, and six advisories against chromadb have no patched release (12). 20 + 5 + 5 + 0 + 12 = 42.

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.

Agent ergonomics Chroma API + MCP +11

Chroma API + MCP 73

13 MCP tools, in the 11 to 30 band (15). The API and the query tool take include to drop embeddings or documents from the response (3 back). limit and offset on list and get, n_results, metadata and document filters, and pagination and field selection in the Search API (20). MCP errors come back as "Failed to ... " plus the raw exception text, and we found no documented error codes (10). upsert makes writes safe to repeat, but the MCP tools carry no readOnlyHint or destructiveHint, including chroma_delete_collection (10). Only the collection name and query text are required. Official Python and JavaScript clients (15). 15 + 3 + 20 + 10 + 10 + 15 = 73.

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

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

Chroma API + MCP 45

No x402, MPP or L402 (0). Per-unit prices published without login, $2.50 per GiB written, $0.33 per GiB a month stored, $0.0075 per TiB scanned and $0.09 per GiB returned (20). $5 of credit for new users, but neither the pricing page nor the pricing docs say whether a card is needed (10 of 20). A person signs up in the browser to get a key. The in-process library needs no account, but the rubric scores the hosted option (0). Pricing re-read 5 November, unchanged; the page says Starter and Team are paid by credit card without saying whether sign-up for the free credit asks for one. 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

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.

Transparency & trust Chroma API + MCP +5

Chroma API + MCP 74

Apache-2.0 (30). The privacy policy names Chroma Inc., links a subprocessor list at trychroma.com/subprocessors and a DPA, but it was last updated 2 October 2024, says the service is hosted in the United States although the changelog announced an EU region in April 2026, and states no retention period beyond "no longer necessary" (18). No deprecation policy or dated notices found, only a migration guide (5). Subprocessors listed. In the current source the PostHog product-telemetry client is a no-op, and OpenTelemetry stays with the operator (15). Privacy policy (2 October 2024), terms (2 October 2024) and changelog re-read 5 November, unchanged; the security page names AWS, Vercel, Honeycomb and PostHog as key providers. 30 + 18 + 5 + 15 = 68.

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

Score by category

CategoryWeightChroma API + MCPMilvus and Zilliz Cloud API + MCPEdge
Reliability16%6095Milvus and Zilliz Cloud API + MCP +35
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6669Milvus and Zilliz Cloud API + MCP +3
Agent ergonomics13%7362Chroma API + MCP +11
Security & auth14%4267Milvus and Zilliz Cloud API + MCP +25
Payments & pricing10%4553Milvus and Zilliz Cloud API + MCP +8
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3585Milvus and Zilliz Cloud API + MCP +50
Transparency & trust7%7469Chroma API + MCP +5
Negative events≤15-7-8
TotalD 50.1/100B 64.1/100

Facts side by side

FactChroma API + MCPMilvus and Zilliz Cloud API + MCP
KindHTTP APIHTTP API
VendorChromaZilliz
Hosted endpointhttps://api.trychroma.com/api/v2https://api.cloud.zilliz.com/v2
TransportsHTTP, stdioHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceApache-2.0Apache-2.0
Tools exposed1316
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-06-302026-10-29
Terms last updated2024-10-022023-04-28
Privacy policy last updated2024-10-02no 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 benchmarkingyesnot found in the text
Terms or service can change without noticeyesyes
Arbitration or class-action waiveryesnot found in the text
Popularitynone46k 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.

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

Chroma API + MCP

Runs in-process, as a local server or serverless on Chroma Cloud with the same v2 API, with per-unit cloud prices published. Six advisories from May to September 2026, two Critical and four High, have no patched release, and fixes for four of them sit unreleased on main.

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

Chroma API + MCP

  1. Don't expose a self-hosted chromadb 1.5.9 server. It has no auth by default and four unpatched advisories, two of them code execution
  2. Don't rely on SimpleRBACAuthorizationProvider to keep tenants apart on a self-hosted server
  3. Batch writes in groups of 300 or fewer on Chroma Cloud
  4. Pass include without embeddings, since returned GiB are billed
  5. Don't pass ollama to chroma_create_collection. The description lists it but the server can't map it

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

Milvus and Zilliz Cloud API + MCP scores 64.1 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 5 of 7 scored categories. Chroma API + MCP leads on agent ergonomics and transparency & trust.

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

Both need an API key.

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

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

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

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

Other comparisons with Chroma API + MCP 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.