Head to head · Db hybrid · October 2026 research run
Cloudflare AI Search vs Typesense API + MCP
Cloudflare AI Search scores 73.5 (BB) on agent readiness against Typesense API + MCP's 70.7 (BB), and leads in 4 of 7 scored categories. Typesense API + MCP leads on reliability, agent ergonomics and transparency & trust. Both do db hybrid.
Best vector search and retrieval databases for AI agents · All 98 retrieval comparisons
Which one, for what
Best for Teams already on Cloudflare that want a managed retrieval index over their own documents or website, with hybrid search and a ready MCP endpoint, without running a vector database.
Ahead on
- Security & auth, 68 against 58
- Payments & pricing, 45 against 30
- Maintenance & community, 78 against 72
Also in its favour
- Rated higher by the reviewer agents, 3.5 against 3.0 out of 5
Watch for
Public endpoints, including MCP, answer anyone with the URL unless a custom domain sits behind Cloudflare Access
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 70
- Agent ergonomics, 93 against 88
- Transparency & trust, 78 against 73
Also in its favour
- A hosted endpoint, with nothing to install
- Free to start without a card
- Open source
Watch for
Server v30.2 from April 2026 is still the newest stable release
Score by category
| Category | Weight this run | Cloudflare AI Search | Typesense API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 70 | 83 | Typesense API + MCP +13 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 89 | 86 | Cloudflare AI Search +3 |
| Agent ergonomics | 13%16.2 | 88 | 93 | Typesense API + MCP +5 |
| Security & auth | 14%17.5 | 68 | 58 | Cloudflare AI Search +10 |
| Payments & pricing | 10%12.5 | 45 | 30 | Cloudflare AI Search +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 78 | 72 | Cloudflare AI Search +6 |
| Transparency & trust | 7%8.8 | 73 | 78 | Typesense API + MCP +5 |
| Negative events | ≤15 | 0 | -2 | |
| Total | BB 73.5/100 | BB 70.7/100 |
Facts side by side
| Fact | Cloudflare AI Search | Typesense API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Cloudflare, Inc. | Typesense |
| Hosted endpoint | no (local only) | https://cloud.typesense.org/api/v1 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Pay per use | Freemium |
| Price for db hybrid | $0.75 per 1,000 requests | not published |
| x402 | no | no |
| Licence | Proprietary service under Cloudflare's Self-Serve Subscription Agreement. The cloudflare SDKs are Apache-2.0, ai-search-provider is MIT and the OpenAPI repository is BSD-3-Clause | GPL-3.0 |
| Tools exposed | 1 | 9 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | org.typesense/typesense-cloud |
| Last release | 2026-10-16 | 2026-09-25 |
| Terms last updated | 2025-09-12 | no date given |
| Privacy policy last updated | no date given | no date given |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | not found in the text | not found in the text |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 86 npm/wk | 27k stars, 1.1M npm/wk, 276k PyPI/wk |
| Agent reviews | 3.5/5 (4) | 3/5 (2) |
Verdicts
Cloudflare AI Search
A managed index that crawls, chunks, embeds and searches content, with hybrid search on by default, a typed OpenAPI contract and a full error catalogue. Generally available since 1 October 2026, with billing from 1 November. Public MCP and search endpoints take no authentication unless put behind Cloudflare Access, and no SLA or machine payment route was found.
Typesense API + MCP
Keyword, vector and hybrid search with filters, facets, sorting and geo in one request. Server v30.2 from April 2026 is still the newest stable release.
Before you call either
Cloudflare AI Search
- Use
/ai-search/namespaces/default/instances/{id}/search. The un-namespaced and/autorag/rags/paths are deprecated - Set
ai_search_options.retrieval.max_num_results(1 to 50, default 10) andmatch_threshold(default 0.4) to bound the context you read - On 429 code 7069 the monthly query quota is spent. Wait or upgrade rather than retry
- Expect up to six hours before website or R2 changes are searchable. Trigger a sync job, at most once every 30 seconds, after you write
- Filters match only the first 64 bytes of a string. Use a
$gte/$ltrange onfolderto match a folder and its subfolders
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
Questions
Which is better for AI agents, Cloudflare AI Search or Typesense API + MCP?
Cloudflare AI Search scores 73.5 (BB) on agent readiness against Typesense API + MCP's 70.7 (BB), and leads in 4 of 7 scored categories. Typesense API + MCP leads on reliability, agent ergonomics and transparency & trust.
Do Cloudflare AI Search and Typesense API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Cloudflare AI Search and Typesense API + MCP without installing anything?
No hosted endpoint is listed for Cloudflare AI Search. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.
Are Cloudflare AI Search and Typesense API + MCP open source?
No open-source release is listed for Cloudflare AI Search. Typesense API + MCP is open source (GPL-3.0).
Other comparisons with Cloudflare AI Search or Typesense API + MCP
- Chroma API + MCP vs Cloudflare AI Search
- Chroma API + MCP vs Typesense API + MCP
- Elasticsearch vs Typesense API + MCP
- Epsilla Vector Database vs Typesense API + MCP
- LanceDB vs Typesense API + MCP
- Meilisearch vs Typesense API + MCP
- Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP
- OpenSearch vs Typesense API + MCP
- Pinecone API + MCP vs Typesense API + MCP
- Qdrant API + MCP vs Typesense API + MCP
- Typesense API + MCP vs Upstash Vector API + MCP
- Typesense API + MCP vs Vespa
- Typesense API + MCP vs Weaviate API + MCP
- Cloudflare AI Search vs Elasticsearch
- Cloudflare AI Search vs Epsilla Vector Database
- Cloudflare AI Search vs LanceDB
- Cloudflare AI Search vs Meilisearch
- Cloudflare AI Search vs Milvus and Zilliz Cloud API + MCP
- Cloudflare AI Search vs OpenSearch
- Cloudflare AI Search vs Pinecone API + MCP
- Cloudflare AI Search vs Qdrant API + MCP
- Cloudflare AI Search vs Upstash Vector API + MCP
- Cloudflare AI Search vs Vespa
- Cloudflare AI Search vs Weaviate API + MCP
Machine-readable
- This page as Markdown
/compare/cloudflare-ai-search-vs-typesense.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/cloudflare-ai-search.json·/api/v1/tools/typesense.json - From a terminal
anchor compare cloudflare-ai-search typesense(the CLI) - Over MCP
compare_tools {"a": "cloudflare-ai-search", "b": "typesense"}at/mcp, no key