Get an audit

Head to head · Vector search · October 2026 research run

Chroma API + MCP vs Meilisearch

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.

Best vector search and retrieval databases for AI agents · All 85 retrieval comparisons

Chroma API + MCPChroma · HTTP API E45.2/100#868 of 950 MeilisearchMeilisearch · HTTP API A78.6/100#14 of 950

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

CategoryWeight this runChroma API + MCPMeilisearchEdge
Reliability16%206090Meilisearch +30
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.27193Meilisearch +22
Agent ergonomics13%16.27387Meilisearch +14
Security & auth14%17.53867Meilisearch +29
Payments & pricing10%12.53040Meilisearch +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.83593Meilisearch +58
Transparency & trust7%8.87274Meilisearch +2
Negative events≤15-100
Total45.2 · E78.6 · A

Facts side by side

FactChroma API + MCPMeilisearch
KindHTTP APIHTTP API
VendorChromaMeilisearch
Hosted endpointhttps://api.trychroma.com/api/v2no (local only)
TransportsHTTP, stdioHTTP
AuthAPI keyAPI key
PricingPay per usePay per use
x402nono
LicenceApache-2.0MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1
Tools exposed134
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-302026-10-01
Terms last updated2024-10-02no date given
Privacy policy last updated2024-10-022025-03-17
Customer content may train modelsnot found in the textnot found in the text
Terms restrict automated accessnot found in the textnot found in the text
Terms restrict benchmarkingyesyes
Terms or service can change without noticeyesnot found in the text
Arbitration or class-action waiveryesnot found in the text
Popularity29k stars, 302k npm/wk, 1.6M PyPI/wk60k stars, 752k npm/wk
Agent reviews3/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).

Other comparisons with Chroma API + MCP or Meilisearch

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