Head to head · Vector search · October 2026 research run
Typesense API + MCP vs Upstash Vector API + MCP
Typesense API + MCP scores 76.6 (BB) on agent readiness against Upstash Vector API + MCP's 66.5 (B), and leads in 5 of 7 scored categories. 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 75
- Schema & documentation, 86 against 49
- Agent ergonomics, 93 against 80
- Maintenance & community, 82 against 56
Also in its favour
- Agent-ready, a grade of BB or better
- Open source
Watch for
Server v30.2 from April 2026 is still the newest stable release
Best for Small to mid-sized agent memory and RAG where per-request pricing and zero setup matter more than search options.
No category where it leads by five points or more, and no fact that sets it apart.
Watch for
The Vector changelog's last entry is August 2025 and the Python client last shipped in February 2025
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 Typesense API + MCP +37
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).
Upstash Vector API + MCP 49
No OpenAPI file found for the Vector REST API. The hosted MCP server's 20 Vector and Search tools are listed by name and access on the docs page, but their input schemas aren't published (5 of 25). llms.txt and Markdown docs (10). Each REST endpoint page says what it does, with no when-not guidance (10). Typed request fields in the reference, but filters are a SQL-like string (10). curl and SDK examples on each page, and no error catalogue found (8). No API versioning, and the Vector changelog's last entry is August 2025 while the FAQ still says hybrid search isn't supported (6). The changelog was re-read on 2 November 2026 and still ends at August 2025. 5 + 10 + 10 + 10 + 8 + 6 = 49.
Maintenance & community Typesense API + MCP +26
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).
Upstash Vector API + MCP 56
The Upstash MCP server package shipped v0.4.0 on 23 October 2026 (30). Besides declaring the stdio package no longer maintained and pointing to the hosted server, v0.4.0 is the first tag to carry the Box workspace tools merged on 31 August and a change to registry publishing, so it is read as a full release, as upstash-qstash read it on 1 November. v0.2.6 (7 August), v0.2.7 (13 August), v0.3.0 (24 August) and v0.4.0 fall in the 90 days from 4 August (20). None touched Vector. The npm package has no Vector tools, vector-js last shipped 1.2.3 on 9 March 2026 (its October commits bundle docs and fix JSDoc, untagged), vector-py 0.8.0 on 27 February 2025, and the Vector changelog's last entry is August 2025 (less 15). Public changelog and Discord support, with no reply data for the SDK repos (5). TypeScript client current, Python client 20 months old (8). CI on vector-js and the MCP server, which publishes to the official registry on release (8). 30 + 20 - 15 + 5 + 8 + 8 = 56.
Agent ergonomics Typesense API + MCP +13
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).
Upstash Vector API + MCP 80
The hosted MCP server now lists 74 tools across Redis, QStash, Workflow, Vector, Search, Box, Blob and a console, of which 20 are for Vector and Search (5). ?features=vector_search scopes the server to those 20, and a read-only key or grant switches off every write tool (10 back, up from 5 when only the read-only mode was credited). topK, metadata filters, includeMetadata, includeVectors and includeData, namespaces, cursor-based range and resumable queries (20). Error responses aren't documented as a list (10). Upserts by ID are safe to repeat, and each MCP tool is labelled read, write or destructive (20). With hosted embedding, upsert-data and query-data take plain text. Official clients for TypeScript, Python and PHP (15). 15 + 20 + 10 + 20 + 15 = 80.
Reliability Typesense API + MCP +8
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).
Upstash Vector API + MCP 75
Statuspage at status.upstash.com with per-product components and a history feed (20). Re-read on 2 November 2026 from history.atom, one Vector incident in the 90 days from 4 August, about 20 minutes of intermittent DNS resolution errors in us-east-1 on 9 September 2026 with existing connections unaffected, so minor only. The 28 August QStash, 3 September console and 29 September connection proxy incidents don't name Vector (20). Daily caps published per plan (10,000 queries and updates on Free, 1M on the $60 fixed plan) but no per-second limit (10 of 15). We found no 429 or backoff guidance for Vector, per the 1 October check. Upserts by ID overwrite, so a retried write is safe (5 of 15). 99.9% uptime SLA on pay as you go and fixed, 99.99% on Pro, re-read on the pricing page (10). GA (10). 20 + 20 + 10 + 5 + 10 + 10 = 75.
Score by category
| Category | Weight | Typesense API + MCP | Upstash Vector API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 83 | 75 | Typesense API + MCP +8 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 86 | 49 | Typesense API + MCP +37 |
| Agent ergonomics | 13% | 93 | 80 | Typesense API + MCP +13 |
| Security & auth | 14% | 65 | 65 | even |
| Payments & pricing | 10% | 60 | 60 | even |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 82 | 56 | Typesense API + MCP +26 |
| Transparency & trust | 7% | 79 | 77 | Typesense API + MCP +2 |
| Negative events | ≤15 | -2 | 0 | |
| Total | BB 76.6/100 | B 66.5/100 |
Facts side by side
| Fact | Typesense API + MCP | Upstash Vector API + MCP |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Typesense | Upstash |
| Hosted endpoint | https://cloud.typesense.org/api/v1 | https://api.upstash.com/v2 |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP |
| Auth | OAuth or key | OAuth or key |
| Pricing | Freemium | Freemium |
| x402 | no | no |
| Licence | GPL-3.0 | MIT |
| Tools exposed | 10 | 74 |
| Read-only variant documented | no | yes |
| llms.txt | yes | yes |
| MCP registry | org.typesense/typesense-cloud | io.github.upstash/mcp-server |
| Last release | 2026-10-23 | 2026-10-23 |
| Terms last updated | no date given | not read yet |
| Privacy policy last updated | no date given | not read yet |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | not found in the text | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Popularity | 27k stars, 1.1M npm/wk, 276k PyPI/wk | 70 stars, 187k npm/wk, 34k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Typesense API + MCP | Upstash Vector API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 3/5 Stable since April, v31 with no date | 2/5 BGE closed to new indexes, no date given |
| LedgerCost analyst | 3/5 No per-search charge, but the cluster hour runs with no traffic | 4/5 $0.004 per 1,000 requests, and a free plan with no card |
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.
Upstash Vector API + MCP
$0.40 per 100,000 requests and a free plan with 10,000 queries and updates a day. The Vector changelog's last entry is August 2025 and the Python client last shipped in February 2025.
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
Upstash Vector API + MCP
- Connect to mcp.upstash.com/mcp for Vector tools.
npx @upstash/mcp-serverhas none - Create the index with an embedding model if the agent works in text; then
query-dataandupsert-datatake strings - Give retrieval-only agents the index's read-only token, not the full one
- Filters use a SQL-like string (
genre = 'fiction' AND year > 2020) in thefilterfield - Ignore the FAQ line saying hybrid isn't supported. Pass
queryModeHYBRID, DENSE or SPARSE on hybrid indexes
Questions
Which is better for AI agents, Typesense API + MCP or Upstash Vector API + MCP?
Typesense API + MCP scores 76.6 (BB) on agent readiness against Upstash Vector API + MCP's 66.5 (B), and leads in 5 of 7 scored categories.
Do Typesense API + MCP and Upstash Vector API + MCP need an API key?
Both take an API key or an OAuth sign-in.
Can an agent call Typesense API + MCP and Upstash Vector API + MCP without installing anything?
Yes. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1 and Upstash Vector API + MCP at https://api.upstash.com/v2.
Are Typesense API + MCP and Upstash Vector API + MCP open source?
Typesense API + MCP is open source (GPL-3.0). No open-source release is listed for Upstash Vector API + MCP.
Other comparisons with Typesense API + MCP or Upstash Vector API + MCP
- Chroma API + MCP vs Typesense API + MCP
- Chroma API + MCP vs Upstash Vector API + MCP
- Elasticsearch vs Typesense API + MCP
- Elasticsearch vs Upstash Vector API + MCP
- Epsilla Vector Database vs Typesense API + MCP
- Epsilla Vector Database vs Upstash Vector API + MCP
- LanceDB vs Typesense API + MCP
- LanceDB vs Upstash Vector API + MCP
- Meilisearch vs Typesense API + MCP
- Meilisearch vs Upstash Vector API + MCP
- Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP
- Milvus and Zilliz Cloud API + MCP vs Upstash Vector API + MCP
- OpenSearch vs Typesense API + MCP
- OpenSearch vs Upstash Vector API + MCP
- Pinecone API + MCP vs Typesense API + MCP
- Pinecone API + MCP vs Upstash Vector API + MCP
- Qdrant API + MCP vs Typesense API + MCP
- Qdrant API + MCP vs Upstash Vector API + MCP
- Typesense API + MCP vs Vespa
- Typesense API + MCP vs Weaviate API + MCP
- Upstash Vector API + MCP vs Vespa
- Upstash Vector API + MCP vs Weaviate API + MCP
- Cloudflare AI Search vs Typesense API + MCP
- Cloudflare AI Search vs Upstash Vector API + MCP
Machine-readable
- This page as Markdown
/compare/typesense-vs-upstash-vector.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/typesense.json·/api/v1/tools/upstash-vector.json - From a terminal
anchor compare typesense upstash-vector(the CLI) - Over MCP
compare_tools {"a": "typesense", "b": "upstash-vector"}at/mcp, no key