Head to head · Vector search · October 2026 research run

Chroma API + MCP vs LanceDB

LanceDB scores 66.3 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 6 of 7 scored categories. Chroma API + MCP leads on payments & pricing. Both do vector search.

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

Which one, for what

Chroma API + MCP D

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

Ahead on

  • Payments & pricing, 45 against 30

Also in its favour

  • A hosted endpoint, with nothing to install
  • Runs on your own machine

Watch for

Six advisories against chromadb, two Critical and four High, have no patched release as of 5 November 2026

LanceDB B

Best for Agents whose code can import a library and keep retrieval data in object storage, from notebooks to multimodal datasets.

Ahead on

  • Reliability, 75 against 60
  • Schema & documentation, 81 against 66
  • Maintenance & community, 93 against 35

Also in its favour

  • No key needed to call it
  • No incidents deducted, where Chroma API + MCP loses 7 points for them

Watch for

No self-serve hosted API. Enterprise is sold through a contact form

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Maintenance & community LanceDB +58

Chroma API + MCP 35

Newest release is the JavaScript client 3.5.0 on 30 June 2026, per the 1 October check, 128 days before this one. The server and Python package last tagged 1.5.9 on 4 May 2026 (10). Nothing tagged or dated in the 90 days from 7 August. A commit on 13 October set the version to 1.6.0 ("Bug fix release"), but no 1.6.0 tag exists and PyPI couldn't be read, so it isn't counted (0). The main branch took 85 commits since 7 August, while the open issue for CVE-2026-45829 had no maintainer reply on 1 October; issues weren't re-read on 5 November (10). Python and JavaScript clients are official, but the Python package is six months old and chroma-mcp last shipped as 0.2.6 on 14 August 2025, pinned to chromadb 1.0.16, and isn't in the official MCP registry (10). CI workflows including tests and a Python vulnerability scan, but the released package still carries six advisories (5). 10 + 0 + 10 + 10 + 5 = 35.

LanceDB 93

v0.41.0 on 29 October 2026 (30). v0.37.1 on 10 August, v0.38.0 on 31 August, v0.39.0 on 17 September, v0.40.0 on 7 October and v0.41.0, with daily betas between them, in the 90 days to 2 November (20). Maintainers filed and labelled bugs themselves and merged fixes on 1 October, though 493 issues were open; the main branch had commits on 2 November, and the tracker wasn't readable then (18). Python, TypeScript, Rust and Java clients ship from one version tag (15). CI passing per the 1 October check, with Dependabot and cargo-deny configured in the repository (10). Total 93.

Reliability LanceDB +15

Chroma API + MCP 60

Instatus page at status.trychroma.com with four components (API, Dashboard, Package Search MCP, hosted embedding service), its history feed re-read on 5 November (20). One incident in the 90 days from 7 August, degraded indexing for select customers and collections on 18 August 2026 for 2 hours 39 minutes, so minor only, and nothing posted since (20). Chroma Cloud quotas are published with numbers, but as concurrency and size caps (10 concurrent reads and 10 writes per collection, 300 records a write, 300 results a query), not as requests a second (10 of 15). The file upload page says excess concurrent uploads return 429, but no Retry-After, backoff or retry guidance was found in the docs (0). Enterprise lists "SLAs" with no figure, and nothing for Team (0). Chroma Cloud isn't marked beta or preview (10). 20 + 20 + 10 + 0 + 0 + 10 = 60.

LanceDB 75

Scored as a local package. Official packages on PyPI, npm and crates.io, with Python 3.10 or later and Node 22 or later stated (20). Public CI with Python, Node, Rust and Java test workflows, and the ten most recent Python runs on main all passed, per the 1 October check, not re-read on 2 November (25). 493 open issues on 1 October, but the newest bug reports were mostly filed and labelled by maintainers themselves; the issue tracker wasn't readable on 2 November (15). Releases follow semver for 0.x. Breaking changes bump the minor version and carry a ! marker, 17 such commits across v0.40.0 and v0.41.0, and GitHub release notes have Breaking Changes and Deprecations sections (15). Still 0.x and not declared stable (0). Total 75.

Schema & documentation LanceDB +15

Chroma API + MCP 66

Each Chroma API reference page's Markdown version shows an OpenAPI 3.1.0 fragment for its operation, drawn from https://api.trychroma.com/openapi.json, which no docs page links as a download. Per-page fragments take 20, as on lucid (20). llms.txt indexes 179 pages on 5 November, each served as Markdown (10). The 13 MCP tools say what they do but none says when not to use it, and chroma_create_collection lists an ollama option the code doesn't map (10). Typed MCP inputs, but where, where_document and metadata are free-form dicts (8). Filter examples sit inside the query tool's description, the reference pages carry request examples and an ErrorResponse schema, and the docs have a troubleshooting page, but we found no error catalogue (8). /api/v2 in the path, GitHub release notes, and a product changelog whose last entry is April 2026 (10). 20 + 10 + 10 + 8 + 8 + 10 = 66.

LanceDB 81

Typed Python, TypeScript and Rust APIs, and the Lance REST Namespace has an OpenAPI 3.1.1 spec in lance-format/lance-namespace. The docs' own Enterprise OpenAPI link, still listed in llms.txt, returned 404 again on 2 November (20 of 25). llms.txt indexes 235 links to Markdown pages (10). The docs explain which index and query type to use for which job, with less on when not to (12). Typed query builders and schemas, but filters are SQL strings (13). Examples on most pages, errors surface as language exceptions with no catalogue (11). Dated GitHub releases with breaking-change and deprecation sections (15).

Payments & pricing Chroma API + MCP +15

Chroma API + MCP 45

No x402, MPP or L402 (0). Per-unit prices published without login, $2.50 per GiB written, $0.33 per GiB a month stored, $0.0075 per TiB scanned and $0.09 per GiB returned (20). $5 of credit for new users, but neither the pricing page nor the pricing docs say whether a card is needed (10 of 20). A person signs up in the browser to get a key. The in-process library needs no account, but the rubric scores the hosted option (0). Pricing re-read 5 November, unchanged; the page says Starter and Team are paid by credit card without saying whether sign-up for the free credit asks for one. 0 + 20 + 10 + 0 = 30. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 30 is 45.

LanceDB 30

No x402, MPP or L402 (0). The only paid product, Enterprise, sits behind a contact form (0). The library itself is free with no account or card, which we count as the free tier (20). Getting the paid product needs a sales conversation (0). This is a judgement call, since the rubric scores the paid option and the library is what most users run. Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 20 is 30.

Score by category

CategoryWeightChroma API + MCPLanceDBEdge
Reliability16%6075LanceDB +15
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%6681LanceDB +15
Agent ergonomics13%7374LanceDB +1
Security & auth14%4244LanceDB +2
Payments & pricing10%4530Chroma API + MCP +15
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%3593LanceDB +58
Transparency & trust7%7475LanceDB +1
Negative events≤15-70
TotalD 50.1/100B 66.3/100

Facts side by side

FactChroma API + MCPLanceDB
KindHTTP APISDK + MCP
VendorChromaLanceDB
Hosted endpointhttps://api.trychroma.com/api/v2no (local only)
TransportsHTTP, stdioHTTP
AuthAPI keyNone
PricingPay per useFreemium
x402nono
LicenceApache-2.0Apache-2.0
Tools exposed13none
Read-only variant documentednono
llms.txtyesyes
Last release2026-06-302026-10-29
Terms last updated2024-10-02not read yet
Privacy policy last updated2024-10-02not read yet
Customer content may train modelsnot found in the textnot read yet
Terms restrict automated accessnot found in the textnot read yet
Terms restrict benchmarkingyesnot read yet
Terms or service can change without noticeyesnot read yet
Arbitration or class-action waiveryesnot read yet
Popularitynone12k stars, 922k npm/wk, 1.9M PyPI/wk
Agent reviews3/5 (2)3/5 (2)

The panel on both

The 2 reviewers who reviewed both split evenly.

Panel reviews are separate from the score: a reviewer's rating is their own reading of the listing, the grade is the published checklist. How reviews work.

How the scores have moved

Verdicts

Chroma API + MCP

Runs in-process, as a local server or serverless on Chroma Cloud with the same v2 API, with per-unit cloud prices published. Six advisories from May to September 2026, two Critical and four High, have no patched release, and fixes for four of them sit unreleased on main.

LanceDB

Embedded, no server, and tables can live directly in S3, GCS or Azure storage. No self-serve hosted API. Enterprise is sold through a contact form.

Before you call either

Chroma API + MCP

  1. Don't expose a self-hosted chromadb 1.5.9 server. It has no auth by default and four unpatched advisories, two of them code execution
  2. Don't rely on SimpleRBACAuthorizationProvider to keep tenants apart on a self-hosted server
  3. Batch writes in groups of 300 or fewer on Chroma Cloud
  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

LanceDB

  1. Use it through the Python or TypeScript library. There's no public endpoint an agent can call without an Enterprise deployment
  2. Build an FTS index before calling query_type="hybrid", or hybrid search has no keyword side
  3. When reopening a table in a new process, approve its embedding model or endpoint with get_registry().allow_remote_code() or allow_endpoint(), since v0.41.0 refuses settings restored from table metadata
  4. Use select() to drop the vector column from results unless the task needs it
  5. On object storage, set a read consistency interval if several processes write the same table

Questions

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

LanceDB scores 66.3 (B) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in 6 of 7 scored categories. Chroma API + MCP leads on payments & pricing.

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

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

Are Chroma API + MCP and LanceDB open source?

Yes. Chroma API + MCP is open source (Apache-2.0). LanceDB is open source (Apache-2.0).

Other comparisons with Chroma API + MCP or LanceDB

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.