Head to head · Vector search · October 2026 research run

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

Typesense API + MCP scores 76.6 (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. 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 83

Also in its favour

  • Runs on your own machine
  • 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

Typesense API + MCP BB

Best for Retrieval where keyword relevance, typo tolerance, filters and facets matter as much as vectors, and for teams that want a hosted MCP server with tight permissions.

Ahead on

  • Schema & documentation, 86 against 69
  • Agent ergonomics, 93 against 62
  • Payments & pricing, 60 against 53
  • Transparency & trust, 79 against 69

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Server v30.2 from April 2026 is still the newest stable release

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.

Agent ergonomics Typesense API + MCP +31

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

Typesense API + MCP 93

10 MCP tools per the docs on 1 November, show_cluster added in October, including two generic read and change tools that cover the rest of the server API (25). per_page, page, include_fields, exclude_fields, filter_by and facets (20). A refused MCP call names the permission it lacks, and imports over 1,000 documents or 10 MB come back as a curl command with a 24-hour key scoped to one collection and action (18). manage_cluster, documents and change_cluster_data are marked destructive so clients ask first. We couldn't confirm readOnlyHint on the read tools (15). Official clients for JavaScript, Python, PHP, Ruby and more. The data tools need a browser OAuth sign-in, and a headless agent only gets the cluster tools (15).

Schema & documentation Typesense API + MCP +17

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

Typesense API + MCP 86

OpenAPI 3.0.3 in typesense/typesense-api-spec, 79 operations, version 30.0, last updated 10 September 2026 (25). llms.txt and Markdown docs (10). The MCP docs say whoami should be called first and describe each tool, but we couldn't read the hosted tool definitions themselves (14). The server API is typed in the spec, but two MCP tools, read_cluster_data and change_cluster_data, take any server API path, which leaves the shape to the model (10). An API errors page lists codes 400 to 503, and every docs page has examples in several languages (12). Docs versioned per server release, GitHub releases and a versioned spec (15).

Reliability Milvus and Zilliz Cloud API + MCP +12

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.

Typesense API + MCP 83

Instatus page at cloud-status.typesense.org with the management console and 21 cluster regions as components (20). The notice history reports no notices from June to November 2026, and every component shows 100.0 per cent for each month. The last incident was 11 hours 30 minutes of slow new-cluster provisioning on 31 May, with existing clusters unaffected, now outside the 90 days (30). Limits documented with numbers, 300 data calls and 30 cluster actions a minute per MCP connection, 30 a minute per management key, and the docs state there are no HTTP rate limits on the server API (15). The management API returns 429 with "Rate Limit Exceeded. Please try again later.", with no Retry-After or backoff advice. Imports take an upsert action, so a retried import is safe (8 of 15). No SLA found on the pricing page or in the docs we read (0). GA (10).

Transparency & trust Typesense API + MCP +10

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

Typesense API + MCP 79

GPL-3.0 (30). The Typesense Cloud privacy policy dates from 20 September 2022, names Typesense Inc., lists processors and AWS regions and links a DPA, but gives no retention period and says the full processor list is on request (18). Docs are versioned per release with an upgrade guide, but we found no deprecation notice policy (8). No usage telemetry in the server source that we could find, and hosted data locations are listed (18).

Payments & pricing Typesense 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.

Typesense API + MCP 60

No x402, MPP or L402 (0). Hourly pricing by RAM, vCPU, nodes and region through a calculator, bandwidth per GB, no rate table on the page (10). A free-tier cluster (0.5 GB RAM, 2 vCPU burst, one node) needs no payment method (20). Since 28 October an agent connected to the MCP server can create a free-tier cluster before anyone has an account and gets its hostname and a key that can't delete or manage keys, and a person claims the cluster later. A person still clicks "Try it without an account" on the sign-in page in a browser when the client connects, and the other tools need a signed-in account or a management key a person creates, so half, as context-dev's browser-completed claim was read (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.

Score by category

CategoryWeightMilvus and Zilliz Cloud API + MCPTypesense API + MCPEdge
Reliability16%9583Milvus and Zilliz Cloud API + MCP +12
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6986Typesense API + MCP +17
Agent ergonomics13%6293Typesense API + MCP +31
Security & auth14%6765Milvus and Zilliz Cloud API + MCP +2
Payments & pricing10%5360Typesense API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8582Milvus and Zilliz Cloud API + MCP +3
Transparency & trust7%6979Typesense API + MCP +10
Negative events≤15-8-2
TotalB 64.1/100BB 76.6/100

Facts side by side

FactMilvus and Zilliz Cloud API + MCPTypesense API + MCP
KindHTTP APIHTTP API
VendorZillizTypesense
Hosted endpointhttps://api.cloud.zilliz.com/v2https://cloud.typesense.org/api/v1
TransportsHTTP, stdio, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0GPL-3.0
Tools exposed1610
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedorg.typesense/typesense-cloud
Last release2026-10-292026-10-23
Terms last updated2023-04-28no date given
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/wk27k stars, 1.1M npm/wk, 276k PyPI/wk
Agent reviews3.5/5 (2)3/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

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.

Typesense API + MCP

Keyword, vector and hybrid search with filters, facets, sorting and geo in one request, with a hosted MCP server that can start a free cluster before an account exists. Server v30.2 from April 2026 is still the newest stable release, and no SLA was found.

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

Typesense API + MCP

  1. Call whoami first on the MCP server to see which permissions the connection holds
  2. Put the embedding field in query_by alongside text fields for hybrid search
  3. Send the key in X-TYPESENSE-API-KEY, not in the URL, so it stays out of logs
  4. Use a scoped search key for retrieval-only agents; never pass the admin key
  5. Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally. Without an account, only free-cluster creation, its status and docs search work

Questions

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

Typesense API + MCP scores 76.6 (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.

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

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

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

Yes. Milvus and Zilliz Cloud API + MCP has a hosted endpoint at https://api.cloud.zilliz.com/v2 and Typesense API + MCP at https://cloud.typesense.org/api/v1.

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

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

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