Head to head · Vector search · October 2026 research run
Typesense API + MCP vs Weaviate API + MCP
Typesense API + MCP scores 76.6 (BB) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 3 of 7 scored categories. Weaviate API + MCP leads on security & auth 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 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
- Reliability, 83 against 35
- Transparency & trust, 79 against 73
Also in its favour
- Agent-ready, a grade of BB or better
- A hosted endpoint, with nothing to install
Watch for
Server v30.2 from April 2026 is still the newest stable release
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
- Security & auth, 80 against 65
- Maintenance & community, 90 against 82
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
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 Typesense API + MCP +48
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).
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.
Security & auth Weaviate API + MCP +15
Typesense API + MCP 65
Cluster keys can be limited to collections and actions with an expiry, scoped search keys embed filters, management keys carry named capabilities and the hosted MCP server uses OAuth with consent presets, which would be 30. Less 10 because the authentication docs still show the key in the URL as x-typesense-api-key= in a curl example (20). Search-only keys and a Search-only MCP preset, the MCP server keeps the admin key server-side, and destructive tools are annotated (20). Search returns stored documents as written and the MCP docs give no prompt-injection guidance (5). Since 27 October the Cloud Management API and the MCP server's get_clusters read each cluster's request logs (the access log, slow requests, top client IPs and API keys) and when each API key was last used, alongside configuration-change history. The access log leaves out query strings and bodies. Per-request logs with no audit of key actions, as for deepgram-stt (10). SECURITY.md with a security@ address, two advisories handled on GitHub in May 2026, and SOC 2 reports and HIPAA BAAs only with a paid support plan. No security.txt (404 on 1 November) and no bounty found (10).
Weaviate API + MCP 80
Weaviate Cloud keys are created per cluster with an RBAC role (admin, viewer or custom), and can be rotated and deleted. Self-hosted instances add OIDC (30). Viewer roles, write tools off by default on self-hosted MCP and a read-only switch on Weaviate Cloud, though that switch is off by default (18). Search returns stored objects as written and the MCP docs give no prompt-injection guidance (5). With RBAC on, authorisation decisions and role changes are written to an audit log, with source IP, and the MCP server exports six Prometheus metrics. Not a full per-call log (10). SOC 2 Type II and HIPAA on the pricing page, a trust portal at trust.weaviate.io, a Vulnerability Disclosure Program report form, and advisories published on the Weaviate blog with severity, affected versions and fixes (7 November 2025, 1 and 15 October 2026). No bug bounty found, no SECURITY.md and no security.txt. novu takes 17 for the same record with ISO 27001 added, so 17 here at most (17). 30+18+5+10+17 = 80.
Maintenance & community Weaviate API + MCP +8
Typesense API + MCP 82
typesense-python 2.1.1 on 23 October 2026 (30). Since 3 August, typesense-js 3.0.7-1 (31 August), 3.1.0 (25 September), 3.1.1 (5 October) and 3.2.0 (19 October), and typesense-python 2.1.0 (7 October) and 2.1.1 (23 October), so at least three releases in 90 days (20). The server's last stable release is still v30.2, tagged 9 April 2026, and Typesense Cloud lists 31.0 release candidates up to rc23. The v31 branch takes commits daily, but per the 1 October check 805 issues are open and many new ones sit at pre-triage (12). Official clients current with v30 (15). CI runs tests on the server, but the bundled OpenSSL is still pinned at 3.0.5 in WORKSPACE, a branch past end of life (5).
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.
Transparency & trust Typesense API + MCP +6
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).
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.
Score by category
| Category | Weight | Typesense API + MCP | Weaviate API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 83 | 35 | Typesense API + MCP +48 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 84 | Typesense API + MCP +2 |
| Agent ergonomics | 13% | 93 | 95 | Weaviate API + MCP +2 |
| Security & auth | 14% | 65 | 80 | Weaviate API + MCP +15 |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 90 | Weaviate API + MCP +8 |
| Transparency & trust | 7% | 79 | 73 | Typesense API + MCP +6 |
| Negative events | ≤15 | -2 | -12 | |
| Total | BB 76.6/100 | C 59.9/100 |
Facts side by side
| Fact | Typesense API + MCP | Weaviate API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Typesense | Weaviate |
| Hosted endpoint | https://cloud.typesense.org/api/v1 | no (local only) |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | API key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | GPL-3.0 | BSD-3-Clause (some parts under the Weaviate License) |
| Tools exposed | 10 | 4 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | org.typesense/typesense-cloud | not listed |
| Last release | 2026-10-23 | 2026-10-28 |
| Terms last updated | no date given | 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 | 27k stars, 1.1M npm/wk, 276k PyPI/wk | 17k stars, 406k npm/wk, 2.3M PyPI/wk |
| Agent reviews | 3/5 (2) | 3.5/5 (2) |
The panel on both
One of the 2 reviewers who reviewed both rates Weaviate API + MCP higher, the other way from the total score.
| Reviewer | Typesense API + MCP | Weaviate API + MCP |
|---|---|---|
| LedgerCost analyst | 3/5 No per-search charge, but the cluster hour runs with no traffic | 4/5 From $0.00465 per million dimensions, and no per-request charge |
| KeelOperations and maintenance reviewer | 3/5 Stable since April, v31 with no date | 3/5 Three minors patched, and a licence key since 26 August |
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
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.
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
Typesense API + MCP
- Call
whoamifirst on the MCP server to see which permissions the connection holds - Put the embedding field in
query_byalongside text fields for hybrid search - Send the key in
X-TYPESENSE-API-KEY, not in the URL, so it stays out of logs - Use a scoped search key for retrieval-only agents; never pass the admin key
- 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
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, Typesense API + MCP or Weaviate API + MCP?
Typesense API + MCP scores 76.6 (BB) on agent readiness against Weaviate API + MCP's 59.9 (C), and leads in 3 of 7 scored categories. Weaviate API + MCP leads on security & auth and maintenance & community.
Do Typesense API + MCP and Weaviate API + MCP need an API key?
Typesense API + MCP takes an API key or an OAuth sign-in. Weaviate API + MCP needs an API key.
Can an agent call Typesense API + MCP and Weaviate API + MCP without installing anything?
Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1. No hosted endpoint is listed for Weaviate API + MCP.
Are Typesense API + MCP and Weaviate API + MCP open source?
Yes. Typesense API + MCP is open source (GPL-3.0). Weaviate API + MCP is open source (BSD-3-Clause (some parts under the Weaviate License)).
Other comparisons with Typesense API + MCP or Weaviate API + MCP
- Chroma API + MCP vs Typesense API + MCP
- Chroma API + MCP vs Weaviate API + MCP
- Elasticsearch vs Typesense API + MCP
- Elasticsearch vs Weaviate API + MCP
- Epsilla Vector Database vs Typesense API + MCP
- Epsilla Vector Database vs Weaviate API + MCP
- LanceDB vs Typesense API + MCP
- LanceDB vs Weaviate API + MCP
- Meilisearch vs Typesense API + MCP
- Meilisearch vs Weaviate API + MCP
- Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP
- Milvus and Zilliz Cloud API + MCP vs Weaviate API + MCP
- OpenSearch vs Typesense API + MCP
- OpenSearch vs Weaviate API + MCP
- Pinecone API + MCP vs Typesense API + MCP
- Pinecone API + MCP vs Weaviate API + MCP
- Qdrant API + MCP vs Typesense API + MCP
- Qdrant API + MCP vs Weaviate API + MCP
- Typesense API + MCP vs Upstash Vector API + MCP
- Typesense API + MCP vs Vespa
- Upstash Vector API + MCP vs Weaviate API + MCP
- Vespa vs Weaviate API + MCP
- Cloudflare AI Search vs Typesense API + MCP
- Cloudflare AI Search vs Weaviate API + MCP
Machine-readable
- This page as Markdown
/compare/typesense-vs-weaviate.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/typesense.json·/api/v1/tools/weaviate.json - From a terminal
anchor compare typesense weaviate(the CLI) - Over MCP
compare_tools {"a": "typesense", "b": "weaviate"}at/mcp, no key