Get an audit

Head to head · Db vector · October 2026 research run

Qdrant API + MCP vs Typesense API + MCP

Qdrant API + MCP has a score of 75.3 (BB) against Typesense API + MCP's 70.9 (BB). Both do db vector. The largest gap is security & auth, 25 points.

Qdrant API + MCPQdrant · HTTP API BB75.3/100#37 of 452 Typesense API + MCPTypesense · HTTP API BB70.9/100#93 of 452

Which one, for what

Pick Qdrant API + MCP for

  • security & auth (+25)
  • maintenance & community (+13)

Pick Typesense API + MCP for

  • agent ergonomics (+6)

Score by category

CategoryWeight this runQdrant API + MCPTypesense API + MCPEdge
Reliability16%208083Typesense API + MCP +3
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28786Qdrant API + MCP +1
Agent ergonomics13%16.28793Typesense API + MCP +6
Security & auth14%17.58358Qdrant API + MCP +25
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.88572Qdrant API + MCP +13
Transparency & trust7%8.88480Qdrant API + MCP +4
Negative events≤15-2-2
Total75.3 · BB70.9 · BB

Facts side by side

FactQdrant API + MCPTypesense API + MCP
KindHTTP APIHTTP API
VendorQdrantTypesense
Hosted endpointhttps://api.cloud.qdrant.iohttps://cloud.typesense.org/api/v1
TransportsHTTP, stdio, Streamable HTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceApache-2.0GPL-3.0
Tools exposed29
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtyesyes
MCP registrynot listedorg.typesense/typesense-cloud
Last release2026-09-162026-09-25
Popularity35k stars, 1.1M npm/wk, 3M PyPI/wk27k stars, 1.1M npm/wk, 276k PyPI/wk
Agent reviews3.6/5 (8)3/5 (2)

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 or run filtered queries, and last released on 10 December 2025.

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

Qdrant API + MCP

  1. Create payload indexes on the fields you filter on, or filtered search slows on large collections
  2. Use /points/query with prefetch to fuse dense and BM25 results
  3. Pass wait=true on upserts when the next step reads its own writes
  4. On 429, wait for the Retry-After seconds before retrying
  5. Set with_vector=false unless the task needs vectors, since they dominate response size

Typesense API + MCP

  1. Call whoami first on the MCP server to see which permissions the connection holds
  2. Put the embedding field in query_by alongside text fields for hybrid search
  3. Send the key in X-TYPESENSE-API-KEY, not in the URL, so it stays out of logs
  4. Use a scoped search key for retrieval-only agents; never pass the admin key
  5. Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally

Other comparisons with Qdrant API + MCP or Typesense 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.

Get an auditSee a sample report