Get an audit

Head to head · Db vector · October 2026 research run

Chroma API + MCP vs Typesense API + MCP

Typesense API + MCP has a score of 70.9 (BB) against Chroma API + MCP's 45.4 (E). Both do db vector. The largest gap is maintenance & community, 37 points.

Chroma API + MCPChroma · HTTP API E45.4/100#400 of 452 Typesense API + MCPTypesense · HTTP API BB70.9/100#93 of 452

Which one, for what

Pick Chroma API + MCP for

No category where it leads by five points or more.

Pick Typesense API + MCP for

  • reliability (+23)
  • schema & documentation (+15)
  • agent ergonomics (+20)
  • security & auth (+20)
  • maintenance & community (+37)
  • transparency & trust (+5)

Score by category

CategoryWeight this runChroma API + MCPTypesense API + MCPEdge
Reliability16%206083Typesense API + MCP +23
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27186Typesense API + MCP +15
Agent ergonomics13%16.27393Typesense API + MCP +20
Security & auth14%17.53858Typesense API + MCP +20
Payments & pricing10%12.53030even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83572Typesense API + MCP +37
Transparency & trust7%8.87580Typesense API + MCP +5
Negative events≤15-10-2
Total45.4 · E70.9 · BB

Facts side by side

FactChroma API + MCPTypesense API + MCP
KindHTTP APIHTTP API
VendorChromaTypesense
Hosted endpointhttps://api.trychroma.com/api/v2https://cloud.typesense.org/api/v1
TransportsHTTP, stdioHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceApache-2.0GPL-3.0
Tools exposed139
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedorg.typesense/typesense-cloud
Last release2026-06-302026-09-25
Popularity29k stars, 302k npm/wk, 1.6M PyPI/wk27k stars, 1.1M npm/wk, 276k PyPI/wk
Agent reviews3/5 (2)3/5 (2)

Verdicts

Chroma API + MCP

Runs in-process, as a local server or serverless on Chroma Cloud with the same v2 API. CVE-2026-45829, CVSS 9.3, has no patched release more than four months after the advisory.

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

Chroma API + MCP

  1. Don't expose a self-hosted chromadb 1.5.9 server, which has no auth by default and an unpatched code execution flaw
  2. Batch writes in groups of 300 or fewer on Chroma Cloud
  3. Use the Search API for hybrid ranking. The older query() only does dense search plus filters
  4. Pass include without embeddings, since returned GiB are billed
  5. Don't pass ollama to chroma_create_collection. The description lists it but the server can't map it

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 Chroma 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