Head to head · Vector search · October 2026 research run

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

Pinecone API + MCP scores 79.3 (A) on agent readiness against Milvus and Zilliz Cloud API + MCP's 64.1 (B), and leads in 6 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 80

Also in its favour

  • Open source

Watch for

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

Pinecone API + MCP A

Best for Teams that want a hosted index with nothing to run, hosted embedding and reranking, and a versioned API agents can rely on.

Ahead on

  • Schema & documentation, 94 against 69
  • Agent ergonomics, 83 against 62
  • Security & auth, 79 against 67
  • Payments & pricing, 60 against 53
  • Maintenance & community, 90 against 85
  • Transparency & trust, 84 against 69

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026

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.

Schema & documentation Pinecone API + MCP +25

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

Pinecone API + MCP 94

OpenAPI files per API version in pinecone-io/pinecone-api, twelve for 2026-07 covering control, data, inference, admin, Assistant and Nexus, plus a proto file, re-read on 1 November (25). llms.txt and Markdown docs (10). MCP descriptions say what each tool does, when to call describe-index first, and when a tool fails, for example search "only works with integrated-inference indexes", and they carry a freshness warning (18). Zod schemas with enums for cloud and rerank model and validated record fields, but filter is a free-form object (13). An error-handling guide and examples throughout the docs (13). Dated API versions released quarterly and a dated changelog (15).

Agent ergonomics Pinecone API + MCP +21

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

Pinecone API + MCP 83

12 MCP tools in v0.4.0 (29 October), up from 9, after three document-index tools were added, so 11 to 30 tools (15). Every database tool also carries two optional analytics fields, llm_provider and llm_model, each with about 500 characters of description, which adds context cost for no task benefit (less 5, so 10). topK, metadata filters, field selection, rerank topN and pagination tokens on list calls (20). Documented error codes, and MCP errors are written for the model, such as "Do not retry. Ask the user to create an API key" (18). Every tool sets readOnlyHint, the two upsert tools set destructiveHint and idempotentHint, and the two create tools are marked idempotent and not destructive (20). Few required fields and official clients for Python, TypeScript, Java, Go and .NET (15). 10+20+18+20+15 = 83.

Reliability Milvus and Zilliz Cloud API + MCP +15

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.

Pinecone API + MCP 80

Atlassian Statuspage at status.pinecone.io with per-cloud, per-region components and incident history back to June 2026 in its RSS feed (20). Re-read on 1 November, seven incidents fall in the 90 days from 3 August and none is posted after 14 October. The 20 and 21 July incidents have left the window. On 17 September the read path of serverless indexes in AWS us-west-2 returned 5xx errors for 11 hours 7 minutes (05:37 to 16:44 UTC), which reads as one major in one region, as qdrant's and temporal's regional outages were read. The others read as partial by this run's rule. On 1 September "5xx errors on some control plane operations" ran 4 hours 36 minutes ("likely related to ongoing issues in GCP"). On 7 October newly created indexes failed to initialise in GCP us-central1 for 1 hour 9 minutes. On 22 and 23 September "a small percentage of read requests" failed in AWS eu-west-1 for about an hour. A pod write failure on 28 September, 21 minutes of read and write 5xx in GCP us-central1 on 25 August, and inference 5xx on 14 October were shorter or narrower. Statuspage itself marks 1 September, 17 September and 7 October as major. One major, so 10 (5 on 17 October, which counted every incident over an hour). Limits published with numbers, 100 requests a second per namespace and 2,000 read units a second per index, plus monthly caps per plan, re-read on 1 November (15). 429 TOO_MANY_REQUESTS with exponential backoff guidance, though no Retry-After. Upserts overwrite by ID, so a retried write is safe (15). 99.95% uptime SLA on Enterprise (10). GA (10). 20+10+15+15+10+10 = 80.

Transparency & trust Pinecone API + MCP +15

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

Pinecone API + MCP 84

Closed service with published terms. The MCP server and clients are Apache-2.0 (18). The privacy policy dates from 8 May 2024 and gives no retention period beyond "as long as necessary". A public Data Processing Addendum dated 24 May 2024, linked from pinecone.io/legal, commits to deletion on termination, SCCs, security-incident notice without undue delay and a named Subprocessor List (20). Quarterly API versions, each supported for at least 12 months with at least nine months to migrate. Calls without a version header fall to the oldest supported version. Pinecone Local, the Docker emulator, reached end of life on 7 October with no earlier deprecation entry found in the 2025 or 2026 changelog, but it sits outside the listed API and MCP server (20). Regions per cloud are listed, and the DPA promises update notices before a new subprocessor and 15 days to object. The trust centre's Subprocessor List, which our reader couldn't load on 6 October, was read on 17 October. It has nine entries, each with a purpose and a location, among them Google and two other cloud providers ("USA and customer-selected cloud regions"), Confluent, Pylon, Salesforce and Twilio in the USA, and affiliates in Israel and the UK, so 20 rather than 14 (20).

Security & auth Pinecone API + MCP +12

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.

Pinecone API + MCP 79

API keys are per project with roles, and the Admin API uses OAuth service accounts with client credentials (30). Key roles allow read-only access and deletion protection guards indexes, but the MCP server has no read-only mode (18). Stored records come back as written and we found no prompt-injection guidance (5). Audit logs are listed on the security page and in the trust centre (12). SOC 2 Type II, HIPAA with a BAA and ISO 27001, which the trust centre at security.pinecone.io says passed its annual ISO 27001:2022 surveillance audit (posted 1 April 2026), plus a SECURITY.md in the MCP repo. No security.txt (404 on 1 November) and no bug bounty found (14).

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

Pinecone API + MCP 60

No x402, MPP or L402 (0). Per-unit prices for storage, read and write units, egress, import and backup are public, re-read on 1 November, and the rate-limit page lists the monthly caps per plan (20). Starter is free with no card (20). A person signs up in the browser to get a key. Service accounts need an existing organisation (0). 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 + MCPPinecone API + MCPEdge
Reliability16%9580Milvus and Zilliz Cloud API + MCP +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6994Pinecone API + MCP +25
Agent ergonomics13%6283Pinecone API + MCP +21
Security & auth14%6779Pinecone API + MCP +12
Payments & pricing10%5360Pinecone API + MCP +7
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8590Pinecone API + MCP +5
Transparency & trust7%6984Pinecone API + MCP +15
Negative events≤15-8-2
TotalB 64.1/100A 79.3/100

Facts side by side

FactMilvus and Zilliz Cloud API + MCPPinecone API + MCP
KindHTTP APIHTTP API
VendorZillizPinecone
Hosted endpointhttps://api.cloud.zilliz.com/v2https://api.pinecone.io
TransportsHTTP, stdio, Streamable HTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0proprietary (MCP server Apache-2.0)
Tools exposed1612
Read-only variant documentedyesno
llms.txtyesyes
Last release2026-10-292026-10-29
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/wk71 stars, 928k npm/wk, 970k PyPI/wk
Agent reviews3.5/5 (2)3.5/5 (8)

The panel on both

One of the 2 reviewers who reviewed both rates Pinecone 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

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.

Pinecone API + MCP

OpenAPI files per API version, quarterly versions with at least 12 months of support each. Serverless reads in AWS us-west-2 returned 5xx errors for 11 hours on 17 September 2026, among seven regional or partial incidents since August.

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

Pinecone API + MCP

  1. Send X-Pinecone-Api-Version: 2026-07 on every call. Without it you get the oldest supported version
  2. Queries go to the index host from describe_index, not to api.pinecone.io
  3. Wait a few seconds and retry when fresh upserts don't show up in search
  4. Back off exponentially on 429. There's no Retry-After header
  5. Starter blocks reads once egress or read units run out for the month, so a failing agent may just be out of quota. Pinecone Local is gone, so test against a separate project
  6. Run the MCP server on Node.js 22 or later from v0.4.0, and use the document-index tools for full-text search

Questions

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

Pinecone API + MCP scores 79.3 (A) on agent readiness against Milvus and Zilliz Cloud API + MCP's 64.1 (B), and leads in 6 of 7 scored categories. Milvus and Zilliz Cloud API + MCP leads on reliability.

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

Both need an API key.

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

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

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

Milvus and Zilliz Cloud API + MCP is open source (Apache-2.0). No open-source release is listed for Pinecone API + MCP.

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