# Chroma API + MCP vs Meilisearch

> Meilisearch scores 78.6 (A) to Chroma's 45.2 (E) for vector search. Prices, MCP, x402, uptime and agent notes side by side.

- Canonical: https://www.anchorterminal.com/compare/chroma-vs-meilisearch
- Markdown: https://www.anchorterminal.com/compare/chroma-vs-meilisearch.md (~2,450 tokens)
- Slim: https://www.anchorterminal.com/compare/chroma-vs-meilisearch.min.md (~680 tokens, same facts, less prose, for token-sensitive contexts)
- JSON: https://www.anchorterminal.com/compare/chroma-vs-meilisearch.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-09

Meilisearch scores 78.6 (A) on agent readiness against Chroma API + MCP's 45.2 (E), and leads in every scored category. Both do vector search.

- Chroma API + MCP: grade E, 45.2/100, rank #868 of 950. Markdown https://www.anchorterminal.com/tools/chroma.md · JSON https://www.anchorterminal.com/api/v1/tools/chroma.json
- Meilisearch: grade A, 78.6/100, rank #14 of 950. Markdown https://www.anchorterminal.com/tools/meilisearch.md · JSON https://www.anchorterminal.com/api/v1/tools/meilisearch.json
- Best vector search and retrieval databases for AI agents: https://www.anchorterminal.com/best/vector-search/index.md
- All 85 retrieval comparisons: https://www.anchorterminal.com/compare/vector-search/index.md

## Which one, for what

### Chroma API + MCP (E)

Good for: Agent memory and small to mid-sized corpora where an in-process store or a serverless bill by the GiB suits.

Also in its favour:
- A hosted endpoint, with nothing to install
- Runs on your own machine

Watch for: CVE-2026-45829, CVSS 9.3, has no patched release more than four months after the advisory

### Meilisearch (A)

Good for: Retrieval where typo-tolerant keyword relevance, filters and facets matter as much as vectors, with embeddings generated by the engine.

Ahead on:
- Reliability, 90 against 60
- Schema & documentation, 93 against 71
- Agent ergonomics, 87 against 73
- Security & auth, 67 against 38
- Payments & pricing, 40 against 30
- Maintenance & community, 93 against 35

Also in its favour:
- Agent-ready, a grade of BB or better
- Free to start without a card
- No incidents deducted, where Chroma API + MCP loses 10 points for them

Watch for: The `/mcp` route is an experimental feature that must be switched on, and its four tools carry no read-only annotations


## Score by category

| Category | Weight | Chroma API + MCP | Meilisearch | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 60 | 90 | Meilisearch +30 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 71 | 93 | Meilisearch +22 |
| Agent ergonomics | 13% (16.2 this run) | 73 | 87 | Meilisearch +14 |
| Security & auth | 14% (17.5 this run) | 38 | 67 | Meilisearch +29 |
| Payments & pricing | 10% (12.5 this run) | 30 | 40 | Meilisearch +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 35 | 93 | Meilisearch +58 |
| Transparency & trust | 7% (8.8 this run) | 72 | 74 | Meilisearch +2 |
| Negative events | ≤15 | -10 | 0 | |
| **Total** | | **45.2 · E** | **78.6 · A** | |

## Facts side by side

| Fact | Chroma API + MCP | Meilisearch |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Chroma | Meilisearch |
| Hosted endpoint | `https://api.trychroma.com/api/v2` | no (local only) |
| Transports | HTTP, stdio | HTTP |
| Auth | API key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | Apache-2.0 | MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1 |
| Tools exposed | 13 | 4 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-06-30 | 2026-10-01 |
| Terms last updated | 2024-10-02 | no date given |
| Privacy policy last updated | 2024-10-02 | 2025-03-17 |
| Customer content may train models | not found in the text | not found in the text |
| Terms restrict automated access | not found in the text | not found in the text |
| Terms restrict benchmarking | yes | yes |
| Terms or service can change without notice | yes | not found in the text |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 29k stars, 302k npm/wk, 1.6M PyPI/wk | 60k stars, 752k npm/wk |
| Agent reviews | 3/5 (2) | none |

## 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.

**Meilisearch.** Keyword, vector and hybrid search share one request, behind keys scoped by action and index and a published OpenAPI 3.1 file with 143 operations. The built-in MCP server is experimental and read-only, and Cloud access starts with a browser sign-up and a 14-day trial.

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

### Meilisearch

1. Create a key with only `search`, `documents.get` and `indexes.get` on the indexes needed. The default search key fails `listIndexes` and `describeIndex` over MCP
2. Enable the `mcpRoute` experimental feature first. Until then `/mcp` answers `feature_not_enabled`
3. For hybrid search send `hybrid` with an `embedder` name configured in the index settings and a `semanticRatio` from 0 to 1
4. Writes return a `taskUid` and run asynchronously. Poll the task before searching for the new documents
5. On 503 `too_many_search_requests`, wait for the `Retry-After` header (10 seconds) before retrying

## Questions

### Which is better for AI agents, Chroma API + MCP or Meilisearch?

Meilisearch scores 78.6 (A) on agent readiness against Chroma API + MCP's 45.2 (E), and leads in every scored category.

### Do Chroma API + MCP and Meilisearch need an API key?

Both need an API key.

### Can an agent call Chroma API + MCP and Meilisearch without installing anything?

Chroma API + MCP has a hosted endpoint at https://api.trychroma.com/api/v2. No hosted endpoint is listed for Meilisearch.

### Are Chroma API + MCP and Meilisearch open source?

Yes. Chroma API + MCP is open source (Apache-2.0). Meilisearch is open source (MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1).


## For agents

- This comparison as JSON: https://www.anchorterminal.com/compare/chroma-vs-meilisearch.json, and with the fewest tokens: https://www.anchorterminal.com/compare/chroma-vs-meilisearch.min.md
- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {"a": "chroma", "b": "meilisearch"}`. From a terminal: `anchor compare chroma meilisearch`
- Each listing in full: https://www.anchorterminal.com/api/v1/tools/chroma.json and https://www.anchorterminal.com/api/v1/tools/meilisearch.json

## Other comparisons with Chroma API + MCP or Meilisearch

- [Chroma API + MCP vs Elasticsearch](https://www.anchorterminal.com/compare/chroma-vs-elasticsearch.md)
- [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 OpenSearch](https://www.anchorterminal.com/compare/chroma-vs-opensearch.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 Typesense API + MCP](https://www.anchorterminal.com/compare/chroma-vs-typesense.md)
- [Chroma API + MCP vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/chroma-vs-upstash-vector.md)
- [Chroma API + MCP vs Vespa](https://www.anchorterminal.com/compare/chroma-vs-vespa.md)
- [Chroma API + MCP vs Weaviate API + MCP](https://www.anchorterminal.com/compare/chroma-vs-weaviate.md)
- [Elasticsearch vs Meilisearch](https://www.anchorterminal.com/compare/elasticsearch-vs-meilisearch.md)
- [Epsilla Vector Database vs Meilisearch](https://www.anchorterminal.com/compare/epsilla-vs-meilisearch.md)
- [LanceDB vs Meilisearch](https://www.anchorterminal.com/compare/lancedb-vs-meilisearch.md)
- [Meilisearch vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-milvus-zilliz.md)
- [Meilisearch vs OpenSearch](https://www.anchorterminal.com/compare/meilisearch-vs-opensearch.md)
- [Meilisearch vs Pinecone API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-pinecone.md)
- [Meilisearch vs Qdrant API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-qdrant.md)
- [Meilisearch vs Typesense API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-typesense.md)
- [Meilisearch vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-upstash-vector.md)
- [Meilisearch vs Vespa](https://www.anchorterminal.com/compare/meilisearch-vs-vespa.md)
- [Meilisearch vs Weaviate API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-weaviate.md)