Head to head · Vector search · October 2026 research run
Qdrant API + MCP vs Weaviate API + MCP
Qdrant API + MCP scores 72.2 (BB) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 4 of 7 scored categories. Weaviate API + MCP leads on agent ergonomics, payments & pricing and maintenance & community. Both do vector search.
Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons
Which one, for what
Best for Filtered vector search and multi-tenant retrieval where the agent can call REST, and for teams that want the same engine self-hosted and managed.
Ahead on
- Reliability, 70 against 35
- Transparency & trust, 84 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
- Runs on your own machine
Watch for
The MCP server has 2 tools, can't manage collections, and last released on 10 December 2025
Best for Hybrid keyword and vector retrieval with filters and multi-tenancy, self-hosted or managed, and for agents that work over MCP.
Ahead on
- Agent ergonomics, 95 against 87
- Payments & pricing, 60 against 45
- Maintenance & community, 90 against 85
Watch for
No public status page or incident history
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.
Reliability Qdrant API + MCP +35
Qdrant API + MCP 70
Better Stack status page at status.qdrant.io with per-region components and incident pages (20). In the 90 days to 1 November, a network-access configuration incident on 14 August marked across the Cloud API, six cluster regions and Hybrid Cloud with 3 minutes of downtime shown for one region per the 6 October check, a Cloud UI outage of 1 hour 31 minutes on 17 August that the page scopes to the console, maintenance windows on 16 August and 21 September that left clusters available, and on 8 October "Cluster Availability Issues in Germany West Central", where some Azure clusters were unavailable and others ran with fewer replicas. The page shows that region down for 1 hour 54 minutes, so one major outage of the core service in one region (10). The overview also shows 1 and 3 minutes of Hybrid Cloud downtime on 22 September and 11 October with no incident posted. The 16 July Cloud API failure has left the window. Since 17 October the page adds only 'Cluster metrics unavailable in AWS us-east-1' on 17 October, where metrics stopped and 'reads and writes are not affected', minor. The overview, read on 1 November, still shows Germany West Central down for 1 hour 54 minutes on 8 October. No published request limits for Qdrant Cloud. Strict mode lets the operator set read and write rate limits per collection, so a mechanism with no vendor numbers (5 of 15). Rate-limited requests return 429 with Retry-After in seconds (confirmed in the server source on 17 October), and wait=true plus upserts by point ID make writes safe to repeat (15). SLA of 99.5% on Standard, 99.9% single-AZ and 99.95% multi-AZ, 99.9% on Premium (10). GA (10).
Weaviate API + MCP 35
No public status page. status.weaviate.io still doesn't resolve, and status.weaviate.cloud (incident.io, titled "Weaviate Enterprise Status") shows a page-not-found body and an empty feed.atom on 1 November (0). No readable history (5). No request limits published for the database. The only numbers are on the AI services (Embeddings 2,000 requests a day and Query Agent 1,000 a month on Free) and a 60-second request timeout on Weaviate Cloud, now stated on the MCP page too (5 of 15). No 429 or backoff guidance found, but the import docs tell you to use deterministic UUIDs so a retried write can't duplicate objects, per the 1 October check (5 of 15). SLA of 99.5% on Flex and up to 99.95% on Premium (10). The database API is GA. The MCP docs page carries "Added in v1.38" with no preview label, though llms.txt still calls the MCP server a preview (10). 0+5+5+5+10+10 = 35.
Payments & pricing Weaviate API + MCP +15
Qdrant API + MCP 45
No x402, MPP or L402 (0). Plans are public, but Standard is "usage-based" with hourly compute, memory and disk charges and no per-unit rate on the page, only a calculator (10). The free cluster needs no card, per the cluster guide read on 17 October (20). A person signs up in the browser and creates keys in the console (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.
Weaviate API + MCP 60
No x402, MPP or L402 (0). Per-unit prices published without login, from $0.00465 per million vector dimensions and $0.12 per GiB stored on Flex, with Premium rates listed too (20). Free cluster with no card required, 100,000 objects and 1 collection (20). A person signs up in the browser and creates a key per cluster (0). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Transparency & trust Qdrant API + MCP +11
Qdrant API + MCP 84
Apache-2.0 (30). The privacy policy names Qdrant Solutions GmbH in Berlin, gives a 90-day limit on IP logs and 14 days on web server logs, names processors and transfer bases. The security page says a Data Processing Agreement is available for GDPR deployments, but neither page links a DPA or a subprocessor list (22). An upgrade policy (one minor version at a time, client SDKs kept within one minor version of the cluster) with per-version upgrade notes, but no deprecation notice period (10). Self-hosted Qdrant sends anonymised usage statistics by default, documented with an opt-out (telemetry_disabled or --disable-telemetry), and the security page says cluster data stays in its deployment region (20).
Weaviate API + MCP 73
BSD-3-Clause for the core. Since 26 August 2026 a wl/ directory holds enterprise code (namespaces, backup deduplication, self-recovery) under a proprietary licence unlocked by key, so the repository is open-core (25). The privacy policy, amended March 2026, names Weaviate B.V. in Amsterdam, lists processors in section 8, states a 5-year retention period and the transfer basis, and agrees with the telemetry page, per the 1 October check. No DPA link found (22). The release notes state a support policy (the latest three minors get fixes), and the GraphQL API was deprecated on 26 October 2026 with a dated timeline (switched off on Weaviate Cloud on 1 December 2026 for clusters unused in 30 days and on 1 May 2027 for the rest). No general notice period is promised (16). Self-hosted telemetry is on by default and documented with DISABLE_TELEMETRY, but the docs say Weaviate may use it to find sales prospects and share it with third parties (12). 25+22+16+12 = 75.
Agent ergonomics Weaviate API + MCP +8
Qdrant API + MCP 87
The MCP server has 2 tools, qdrant-find and qdrant-store (25). limit, offset, scroll pagination, with_payload and with_vector to trim responses, and payload filters (20). Errors come back with an HTTP status and a JSON message, mapped per error type, and a common-errors page explains the usual ones (15). Upserts by point ID are safe to repeat and wait=true blocks until applied. QDRANT_READ_ONLY=true drops the store tool, but neither tool sets readOnlyHint or destructiveHint (12). Few required fields and official clients for Python, TypeScript, Rust, Go, Java and .NET (15).
Weaviate API + MCP 95
4 MCP tools (25). limit, return_properties, return_metadata, target_properties, filters and tenants on hybrid search, plus a cursor API for paging through a collection (20). The MCP page now documents each error an agent meets, with its code and text (401 with a JSON body for a bad key, 400 listing supported protocol versions, 503 when the server is off, isError results for permission failures, invalid arguments and disabled writes, and the 60-second cut-off). No catalogue for the REST API (15). Every tool sets readOnlyHint, destructiveHint and idempotentHint, and the write tool is hidden from tools/list until write access is enabled (20). Only query and collection_name are required. Official clients for Python, TypeScript, Go, Java and C# (15). 25+20+15+20+15 = 95.
Maintenance & community Weaviate API + MCP +5
Qdrant API + MCP 85
Server v1.20.0 tagged on 21 October 2026, within 30 days (30). v1.19.0 (4 August), v1.19.1 (3 September), v1.19.2 (5 October) and v1.20.0 (21 October) in the last 90 days, plus the Python client v1.20.0 on 22 October (20). The dev branch took 66 commits from 17 to 31 October, many of them fixes, but 474 issues were open and a batch of July bug reports sat open per the 1 October check, not re-read on 1 November, and we couldn't see reply counts (15). Official clients in six languages, current with the server (15). 18 CI workflows and a Dependabot configuration in the repository (10). Less 5 because the MCP server's last release is still v0.8.1 on 10 December 2025, with its last commit on 11 August 2026. 30+20+15+15+10-5 = 85.
Weaviate API + MCP 90
v1.40.3 tagged on 28 October 2026, with v1.39.14 and v1.38.23 on 27 October (30). Dozens of patch releases across three supported minors since 3 August, with v1.40.0 on 6 October after three release candidates from 15 September (20). Issue replies per the 1 October check, not re-read on 1 November because GitHub's pages refuse us: 456 open issues, the newest bug reports answered within weeks (15). Official clients in five languages, Python 4.24.1 on 26 October and TypeScript 3.15.2 on 27 October (15). CI on pull requests with a linter and a security lint workflow, per the 1 October check (10). 30+20+15+15+10 = 90.
Score by category
| Category | Weight | Qdrant API + MCP | Weaviate API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 70 | 35 | Qdrant API + MCP +35 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 87 | 84 | Qdrant API + MCP +3 |
| Agent ergonomics | 13% | 87 | 95 | Weaviate API + MCP +8 |
| Security & auth | 14% | 83 | 80 | Qdrant API + MCP +3 |
| Payments & pricing | 10% | 45 | 60 | Weaviate API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 85 | 90 | Weaviate API + MCP +5 |
| Transparency & trust | 7% | 84 | 73 | Qdrant API + MCP +11 |
| Negative events | ≤15 | -5 | -12 | |
| Total | BB 72.2/100 | C 59.9/100 |
Facts side by side
| Fact | Qdrant API + MCP | Weaviate API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Qdrant | Weaviate |
| Hosted endpoint | https://api.cloud.qdrant.io | no (local only) |
| Transports | HTTP, stdio, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | API key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | BSD-3-Clause (some parts under the Weaviate License) |
| Tools exposed | 2 | 4 |
| Read-only variant documented | yes | yes |
| llms.txt | yes | yes |
| Last release | 2026-10-21 | 2026-10-28 |
| Terms last updated | 2021-12-10 | 2026-05-01 |
| Privacy policy last updated | no date given | 2024-02-01 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 35k stars, 1.1M npm/wk, 3M PyPI/wk | 17k stars, 406k npm/wk, 2.3M PyPI/wk |
| Agent reviews | 3.6/5 (8) | 3.5/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Qdrant API + MCP | Weaviate API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 4/5 One minor at a time, and the rule is written | 3/5 Three minors patched, and a licence key since 26 August |
| LedgerCost analyst | 3/5 No rate card for Qdrant Cloud, and an idle cluster still bills | 4/5 From $0.00465 per million dimensions, and no per-request charge |
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
Qdrant API + MCP
Database keys can be read-only, limited to chosen collections and expire after 90 days by default. The MCP server has 2 tools, can't manage collections, exposes filters only through settings its README doesn't document, and last released on 10 December 2025.
Weaviate API + MCP
Built-in MCP server with 4 typed tools, full annotations and documented error answers, and write tools hidden until enabled on self-hosted instances. Weaviate posts security advisories on its blog, three in the last year, but one released authentication fix in October carried none. No public status page or incident history.
Before you call either
Qdrant API + MCP
- Create payload indexes on the fields you filter on, or filtered search slows on large collections
- Use
/points/querywithprefetchto fuse dense and BM25 results - Pass
wait=trueon upserts when the next step reads its own writes - On 429, wait for the
Retry-Afterseconds before retrying - Set
with_vector=falseunless the task needs vectors, since they dominate response size - Before upgrading a self-hosted cluster to v1.20, set
api_keyif onlyread_only_api_keyis configured, or peers stop talking to each other
Weaviate API + MCP
- Call
weaviate-collections-get-configfirst so the model sees property names before it writes a filter - Set
return_propertiesonweaviate-query-hybrid, since every property comes back in full otherwise andlimitdefaults to 100 - Turn on Enable MCP Read-Only in Weaviate Cloud, or use a viewer key, before giving an agent the MCP endpoint
- Check collection names before an upsert, because auto-schema creates a new collection from a typo
- Move GraphQL queries to the clients or the REST Search API before 1 December 2026 on Weaviate Cloud
Questions
Which is better for AI agents, Qdrant API + MCP or Weaviate API + MCP?
Qdrant API + MCP scores 72.2 (BB) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 4 of 7 scored categories. Weaviate API + MCP leads on agent ergonomics, payments & pricing and maintenance & community.
Do Qdrant API + MCP and Weaviate API + MCP need an API key?
Both need an API key.
Can an agent call Qdrant API + MCP and Weaviate API + MCP without installing anything?
Qdrant API + MCP has a hosted endpoint at https://api.cloud.qdrant.io. No hosted endpoint is listed for Weaviate API + MCP.
Are Qdrant API + MCP and Weaviate API + MCP open source?
Yes. Qdrant API + MCP is open source (Apache-2.0). Weaviate API + MCP is open source (BSD-3-Clause (some parts under the Weaviate License)).
Other comparisons with Qdrant API + MCP or Weaviate API + MCP
- Chroma API + MCP vs Qdrant API + MCP
- Chroma API + MCP vs Weaviate API + MCP
- Elasticsearch vs Qdrant API + MCP
- Elasticsearch vs Weaviate API + MCP
- Epsilla Vector Database vs Qdrant API + MCP
- Epsilla Vector Database vs Weaviate API + MCP
- LanceDB vs Qdrant API + MCP
- LanceDB vs Weaviate API + MCP
- Meilisearch vs Qdrant API + MCP
- Meilisearch vs Weaviate API + MCP
- Milvus and Zilliz Cloud API + MCP vs Qdrant API + MCP
- Milvus and Zilliz Cloud API + MCP vs Weaviate API + MCP
- OpenSearch vs Qdrant API + MCP
- OpenSearch vs Weaviate API + MCP
- Pinecone API + MCP vs Qdrant API + MCP
- Pinecone API + MCP vs Weaviate API + MCP
- Qdrant API + MCP vs Typesense API + MCP
- Qdrant API + MCP vs Upstash Vector API + MCP
- Qdrant API + MCP vs Vespa
- Typesense API + MCP vs Weaviate API + MCP
- Upstash Vector API + MCP vs Weaviate API + MCP
- Vespa vs Weaviate API + MCP
- Cloudflare AI Search vs Qdrant API + MCP
- Cloudflare AI Search vs Weaviate API + MCP
Machine-readable
- This page as Markdown
/compare/qdrant-vs-weaviate.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/qdrant.json·/api/v1/tools/weaviate.json - From a terminal
anchor compare qdrant weaviate(the CLI) - Over MCP
compare_tools {"a": "qdrant", "b": "weaviate"}at/mcp, no key