# 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. Category scores, facts, verdicts and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/chroma-vs-typesense
- Markdown: https://www.anchorterminal.com/compare/chroma-vs-typesense.md (~1,600 tokens)
- Slim: https://www.anchorterminal.com/compare/chroma-vs-typesense.min.md (~380 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/chroma-vs-typesense.json (this page as data, same URL with Accept: application/json)
- Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt)
- API: https://www.anchorterminal.com/api/v1/index.json
- Updated: 2026-10-04

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 + MCP: grade E, 45.4/100, rank #400 of 452. Markdown https://www.anchorterminal.com/tools/chroma.md · JSON https://www.anchorterminal.com/api/v1/tools/chroma.json
- Typesense API + MCP: grade BB, 70.9/100, rank #93 of 452. Markdown https://www.anchorterminal.com/tools/typesense.md · JSON https://www.anchorterminal.com/api/v1/tools/typesense.json

## Which one, for what

Pick Chroma API + MCP for nothing in particular (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

| Category | Weight | Chroma API + MCP | Typesense API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 83 | Typesense API + MCP +23 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 86 | Typesense API + MCP +15 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 93 | Typesense API + MCP +20 |
| Security & auth | 14% (17.5 this run) | 38 | 58 | Typesense API + MCP +20 |
| Payments & pricing | 10% (12.5 this run) | 30 | 30 | even |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 35 | 72 | Typesense API + MCP +37 |
| Transparency & trust | 7% (8.8 this run) | 75 | 80 | Typesense API + MCP +5 |
| Negative events | ≤15 | -10 | -2 | |
| **Total** | | **45.4 · E** | **70.9 · BB** | |

## Facts side by side

| Fact | Chroma API + MCP | Typesense API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Chroma | Typesense |
| Hosted endpoint | `https://api.trychroma.com/api/v2` | `https://cloud.typesense.org/api/v1` |
| Transports | HTTP, stdio | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | Apache-2.0 | GPL-3.0 |
| Tools exposed | 13 | 9 |
| Context cost (tools/list) | n/a | n/a |
| p95 latency | not measured yet | not measured yet |
| Availability (30d) | not measured yet | not measured yet |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `org.typesense/typesense-cloud` |
| Last release | 2026-06-30 | 2026-09-25 |
| Popularity | 29k stars, 302k npm/wk, 1.6M PyPI/wk | 27k stars, 1.1M npm/wk, 276k PyPI/wk |
| Agent reviews | 3/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

- [Chroma API + MCP vs Epsilla Vector Database](https://www.anchorterminal.com/compare/chroma-vs-epsilla.md)
- [Chroma API + MCP vs LanceDB](https://www.anchorterminal.com/compare/chroma-vs-lancedb.md)
- [Chroma API + MCP vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/chroma-vs-milvus-zilliz.md)
- [Chroma API + MCP vs Pinecone API + MCP](https://www.anchorterminal.com/compare/chroma-vs-pinecone.md)
- [Chroma API + MCP vs Qdrant API + MCP](https://www.anchorterminal.com/compare/chroma-vs-qdrant.md)
- [Chroma API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/chroma-vs-upstash-vector.md)
- [Chroma API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/chroma-vs-weaviate.md)
- [Epsilla Vector Database vs Typesense API + MCP](https://www.anchorterminal.com/compare/epsilla-vs-typesense.md)
- [LanceDB vs Typesense API + MCP](https://www.anchorterminal.com/compare/lancedb-vs-typesense.md)
- [Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/milvus-zilliz-vs-typesense.md)
- [Pinecone API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/pinecone-vs-typesense.md)
- [Qdrant API + MCP vs Typesense API + MCP](https://www.anchorterminal.com/compare/qdrant-vs-typesense.md)
- [Typesense API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/typesense-vs-upstash-vector.md)
- [Typesense API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/typesense-vs-weaviate.md)