Get an audit

Head to head · Db vector · October 2026 research run

Typesense API + MCP vs Weaviate API + MCP

Typesense API + MCP has a score of 70.9 (BB) against Weaviate API + MCP's 68.2 (B). Both do db vector. The largest gap is reliability, 48 points.

Typesense API + MCPTypesense · HTTP API BB70.9/100#93 of 452 Weaviate API + MCPWeaviate · HTTP API B68.2/100#131 of 452

Which one, for what

Pick Typesense API + MCP for

  • reliability (+48)
  • transparency & trust (+9)

Pick Weaviate API + MCP for

  • security & auth (+21)
  • payments & pricing (+10)
  • maintenance & community (+18)

Score by category

CategoryWeight this runTypesense API + MCPWeaviate API + MCPEdge
Reliability16%208335Typesense API + MCP +48
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.28682Typesense API + MCP +4
Agent ergonomics13%16.29392Typesense API + MCP +1
Security & auth14%17.55879Weaviate API + MCP +21
Payments & pricing10%12.53040Weaviate API + MCP +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.87290Weaviate API + MCP +18
Transparency & trust7%8.88071Typesense API + MCP +9
Negative events≤15-20
Total70.9 · BB68.2 · B

Facts side by side

FactTypesense API + MCPWeaviate API + MCP
KindHTTP APIHTTP API
VendorTypesenseWeaviate
Hosted endpointhttps://cloud.typesense.org/api/v1no (local only)
TransportsHTTP, Streamable HTTPHTTP, Streamable HTTP
AuthOAuth or keyAPI key
PricingFreemiumFreemium
x402nono
LicenceGPL-3.0BSD-3-Clause (some parts under the Weaviate License)
Tools exposed94
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednoyes
llms.txtyesyes
MCP registryorg.typesense/typesense-cloudnot listed
Last release2026-09-252026-10-01
Popularity27k stars, 1.1M npm/wk, 276k PyPI/wk17k stars, 406k npm/wk, 2.3M PyPI/wk
Agent reviews3/5 (2)3.5/5 (2)

Verdicts

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.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, readOnly, destructive and idempotent hints on each, and write tools hidden until enabled. No public status page or incident history.

Before you call either

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

Weaviate API + MCP

  1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
  2. weaviate-query-hybrid defaults alpha to 0.75, so lower it for keyword-heavy queries
  3. Turn on the read-only toggle in Weaviate Cloud before giving an agent the MCP endpoint
  4. Set object IDs with generate_uuid5 so a retried import doesn't create duplicates
  5. Free clusters hold one collection. Use tenants rather than extra collections

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