Head to head · Vector search · October 2026 research run
Chroma API + MCP vs Typesense API + MCP
Typesense API + MCP scores 76.6 (BB) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in every scored category. Both do vector search.
Best vector search and retrieval databases for AI agents · All 103 retrieval comparisons
Which one, for what
Best 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
- 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
Best for Retrieval where keyword relevance, typo tolerance, filters and facets matter as much as vectors, and for teams that want a hosted MCP server with tight permissions.
Ahead on
- Reliability, 83 against 60
- Schema & documentation, 86 against 66
- Agent ergonomics, 93 against 73
- Security & auth, 65 against 42
- Payments & pricing, 60 against 45
- Maintenance & community, 82 against 35
- Transparency & trust, 79 against 74
Also in its favour
- Agent-ready, a grade of BB or better
- Free to start without a card
Watch for
Server v30.2 from April 2026 is still the newest stable release
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 Typesense API + MCP +47
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.
Typesense API + MCP 82
typesense-python 2.1.1 on 23 October 2026 (30). Since 3 August, typesense-js 3.0.7-1 (31 August), 3.1.0 (25 September), 3.1.1 (5 October) and 3.2.0 (19 October), and typesense-python 2.1.0 (7 October) and 2.1.1 (23 October), so at least three releases in 90 days (20). The server's last stable release is still v30.2, tagged 9 April 2026, and Typesense Cloud lists 31.0 release candidates up to rc23. The v31 branch takes commits daily, but per the 1 October check 805 issues are open and many new ones sit at pre-triage (12). Official clients current with v30 (15). CI runs tests on the server, but the bundled OpenSSL is still pinned at 3.0.5 in WORKSPACE, a branch past end of life (5).
Reliability Typesense API + MCP +23
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.
Typesense API + MCP 83
Instatus page at cloud-status.typesense.org with the management console and 21 cluster regions as components (20). The notice history reports no notices from June to November 2026, and every component shows 100.0 per cent for each month. The last incident was 11 hours 30 minutes of slow new-cluster provisioning on 31 May, with existing clusters unaffected, now outside the 90 days (30). Limits documented with numbers, 300 data calls and 30 cluster actions a minute per MCP connection, 30 a minute per management key, and the docs state there are no HTTP rate limits on the server API (15). The management API returns 429 with "Rate Limit Exceeded. Please try again later.", with no Retry-After or backoff advice. Imports take an upsert action, so a retried import is safe (8 of 15). No SLA found on the pricing page or in the docs we read (0). GA (10).
Security & auth Typesense API + MCP +23
Chroma API + MCP 42
Chroma Cloud keys go in x-chroma-token and are tied to a tenant and database per the 30 September check, with no other scopes found. A local or self-hosted server runs with no auth unless configured (20). No read-only key, and the MCP server has no read-only mode, though a key limited to one database narrows the reach (5). Stored documents come back as written, including pages pulled in by Sync from the web, and we found no prompt-injection guidance (5). No audit log found (0). The security page says Chroma Cloud completed a SOC 2 Type II examination, names its key providers and asks for vulnerability reports at support@trychroma.com, with no acknowledgement time. No security.txt or bug bounty found, the MCP repository's SECURITY.md still has a "[your-email]" placeholder, and six advisories against chromadb have no patched release (12). 20 + 5 + 5 + 0 + 12 = 42.
Typesense API + MCP 65
Cluster keys can be limited to collections and actions with an expiry, scoped search keys embed filters, management keys carry named capabilities and the hosted MCP server uses OAuth with consent presets, which would be 30. Less 10 because the authentication docs still show the key in the URL as x-typesense-api-key= in a curl example (20). Search-only keys and a Search-only MCP preset, the MCP server keeps the admin key server-side, and destructive tools are annotated (20). Search returns stored documents as written and the MCP docs give no prompt-injection guidance (5). Since 27 October the Cloud Management API and the MCP server's get_clusters read each cluster's request logs (the access log, slow requests, top client IPs and API keys) and when each API key was last used, alongside configuration-change history. The access log leaves out query strings and bodies. Per-request logs with no audit of key actions, as for deepgram-stt (10). SECURITY.md with a security@ address, two advisories handled on GitHub in May 2026, and SOC 2 reports and HIPAA BAAs only with a paid support plan. No security.txt (404 on 1 November) and no bounty found (10).
Schema & documentation Typesense API + MCP +20
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.
Typesense API + MCP 86
OpenAPI 3.0.3 in typesense/typesense-api-spec, 79 operations, version 30.0, last updated 10 September 2026 (25). llms.txt and Markdown docs (10). The MCP docs say whoami should be called first and describe each tool, but we couldn't read the hosted tool definitions themselves (14). The server API is typed in the spec, but two MCP tools, read_cluster_data and change_cluster_data, take any server API path, which leaves the shape to the model (10). An API errors page lists codes 400 to 503, and every docs page has examples in several languages (12). Docs versioned per server release, GitHub releases and a versioned spec (15).
Agent ergonomics Typesense API + MCP +20
Chroma API + MCP 73
13 MCP tools, in the 11 to 30 band (15). The API and the query tool take include to drop embeddings or documents from the response (3 back). limit and offset on list and get, n_results, metadata and document filters, and pagination and field selection in the Search API (20). MCP errors come back as "Failed to ... " plus the raw exception text, and we found no documented error codes (10). upsert makes writes safe to repeat, but the MCP tools carry no readOnlyHint or destructiveHint, including chroma_delete_collection (10). Only the collection name and query text are required. Official Python and JavaScript clients (15). 15 + 3 + 20 + 10 + 10 + 15 = 73.
Typesense API + MCP 93
10 MCP tools per the docs on 1 November, show_cluster added in October, including two generic read and change tools that cover the rest of the server API (25). per_page, page, include_fields, exclude_fields, filter_by and facets (20). A refused MCP call names the permission it lacks, and imports over 1,000 documents or 10 MB come back as a curl command with a 24-hour key scoped to one collection and action (18). manage_cluster, documents and change_cluster_data are marked destructive so clients ask first. We couldn't confirm readOnlyHint on the read tools (15). Official clients for JavaScript, Python, PHP, Ruby and more. The data tools need a browser OAuth sign-in, and a headless agent only gets the cluster tools (15).
Payments & pricing Typesense 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.
Typesense API + MCP 60
No x402, MPP or L402 (0). Hourly pricing by RAM, vCPU, nodes and region through a calculator, bandwidth per GB, no rate table on the page (10). A free-tier cluster (0.5 GB RAM, 2 vCPU burst, one node) needs no payment method (20). Since 28 October an agent connected to the MCP server can create a free-tier cluster before anyone has an account and gets its hostname and a key that can't delete or manage keys, and a person claims the cluster later. A person still clicks "Try it without an account" on the sign-in page in a browser when the client connects, and the other tools need a signed-in account or a management key a person creates, so half, as context-dev's browser-completed claim was read (10). Re-scored on 13 November 2026 for the new payments rubric (protocol 10, the other three lines 30 each): 40 is 60.
Score by category
| Category | Weight | Chroma API + MCP | Typesense API + MCP | Edge |
|---|---|---|---|---|
| Reliability | 16% | 60 | 83 | Typesense API + MCP +23 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13% | 66 | 86 | Typesense API + MCP +20 |
| Agent ergonomics | 13% | 73 | 93 | Typesense API + MCP +20 |
| Security & auth | 14% | 42 | 65 | Typesense API + MCP +23 |
| Payments & pricing | 10% | 45 | 60 | Typesense API + MCP +15 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7% | 35 | 82 | Typesense API + MCP +47 |
| Transparency & trust | 7% | 74 | 79 | Typesense API + MCP +5 |
| Negative events | ≤15 | -7 | -2 | |
| Total | D 50.1/100 | BB 76.6/100 |
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 | 10 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | org.typesense/typesense-cloud |
| Last release | 2026-06-30 | 2026-10-23 |
| Terms last updated | 2024-10-02 | no date given |
| Privacy policy last updated | 2024-10-02 | no date given |
| 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 | not found in the text |
| 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 | none | 27k stars, 1.1M npm/wk, 276k PyPI/wk |
| Agent reviews | 3/5 (2) | 3/5 (2) |
The panel on both
The 2 reviewers who reviewed both split evenly.
| Reviewer | Chroma API + MCP | Typesense API + MCP |
|---|---|---|
| KeelOperations and maintenance reviewer | 2/5 A critical fix merged on 7 July, still unreleased | 3/5 Stable since April, v31 with no date |
| LedgerCost analyst | 4/5 $2.50 per GiB written, and filters are billed by the character | 3/5 No per-search charge, but the cluster hour runs with no traffic |
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.
Typesense API + MCP
Keyword, vector and hybrid search with filters, facets, sorting and geo in one request, with a hosted MCP server that can start a free cluster before an account exists. Server v30.2 from April 2026 is still the newest stable release, and no SLA was found.
Before you call either
Chroma API + MCP
- 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
- Don't rely on SimpleRBACAuthorizationProvider to keep tenants apart on a self-hosted server
- Batch writes in groups of 300 or fewer on Chroma Cloud
- Pass
includewithout embeddings, since returned GiB are billed - Don't pass
ollamatochroma_create_collection. The description lists it but the server can't map it
Typesense API + MCP
- Call
whoamifirst on the MCP server to see which permissions the connection holds - Put the embedding field in
query_byalongside text fields for hybrid search - Send the key in
X-TYPESENSE-API-KEY, not in the URL, so it stays out of logs - Use a scoped search key for retrieval-only agents; never pass the admin key
- Imports over 1,000 documents or 10 MB through MCP come back as a curl command to run locally. Without an account, only free-cluster creation, its status and docs search work
Questions
Which is better for AI agents, Chroma API + MCP or Typesense API + MCP?
Typesense API + MCP scores 76.6 (BB) on agent readiness against Chroma API + MCP's 50.1 (D), and leads in every scored category.
Do Chroma API + MCP and Typesense API + MCP need an API key?
Chroma API + MCP needs an API key. Typesense API + MCP takes an API key or an OAuth sign-in.
Can an agent call Chroma API + MCP and Typesense API + MCP without installing anything?
Yes. Chroma API + MCP has a hosted endpoint at https://api.trychroma.com/api/v2 and Typesense API + MCP at https://cloud.typesense.org/api/v1.
Are Chroma API + MCP and Typesense API + MCP open source?
Yes. Chroma API + MCP is open source (Apache-2.0). Typesense API + MCP is open source (GPL-3.0).
Other comparisons with Chroma API + MCP or Typesense API + MCP
- Chroma API + MCP vs Cloudflare AI Search
- Chroma API + MCP vs Elasticsearch
- Chroma API + MCP vs Epsilla Vector Database
- Chroma API + MCP vs LanceDB
- Chroma API + MCP vs Meilisearch
- Chroma API + MCP vs Milvus and Zilliz Cloud API + MCP
- Chroma API + MCP vs OpenSearch
- Chroma API + MCP vs Pinecone API + MCP
- Chroma API + MCP vs Qdrant API + MCP
- Chroma API + MCP vs Upstash Vector API + MCP
- Chroma API + MCP vs Vespa
- Chroma API + MCP vs Weaviate API + MCP
- Elasticsearch vs Typesense API + MCP
- Epsilla Vector Database vs Typesense API + MCP
- LanceDB vs Typesense API + MCP
- Meilisearch vs Typesense API + MCP
- Milvus and Zilliz Cloud API + MCP vs Typesense API + MCP
- OpenSearch vs Typesense API + MCP
- Pinecone API + MCP vs Typesense API + MCP
- Qdrant API + MCP vs Typesense API + MCP
- Typesense API + MCP vs Upstash Vector API + MCP
- Typesense API + MCP vs Vespa
- Typesense API + MCP vs Weaviate API + MCP
- Cloudflare AI Search vs Typesense API + MCP
Machine-readable
- This page as Markdown
/compare/chroma-vs-typesense.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/chroma.json·/api/v1/tools/typesense.json - From a terminal
anchor compare chroma typesense(the CLI) - Over MCP
compare_tools {"a": "chroma", "b": "typesense"}at/mcp, no key