# Meilisearch vs Typesense API + MCP

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

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

Meilisearch scores 78.6 (A) on agent readiness against Typesense API + MCP's 70.7 (BB), and leads in 5 of 7 scored categories. Typesense API + MCP leads on agent ergonomics. Both do vector search.

- 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
- Typesense API + MCP: grade BB, 70.7/100, rank #146 of 950. Markdown https://www.anchorterminal.com/tools/typesense.md · JSON https://www.anchorterminal.com/api/v1/tools/typesense.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

### 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 83
- Schema & documentation, 93 against 86
- Security & auth, 67 against 58
- Payments & pricing, 40 against 30
- Maintenance & community, 93 against 72

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

### Typesense API + MCP (BB)

Good 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:
- Agent ergonomics, 93 against 87

Also in its favour:
- A hosted endpoint, with nothing to install

Watch for: Server v30.2 from April 2026 is still the newest stable release


## Score by category

| Category | Weight | Meilisearch | Typesense API + MCP | Edge |
| --- | --- | --- | --- | --- |
| Reliability | 16% (20 this run) | 90 | 83 | Meilisearch +7 |
| Performance | 10%, pending | pending | pending | not scored in this run |
| Schema & documentation | 13% (16.2 this run) | 93 | 86 | Meilisearch +7 |
| Agent ergonomics | 13% (16.2 this run) | 87 | 93 | Typesense API + MCP +6 |
| Security & auth | 14% (17.5 this run) | 67 | 58 | Meilisearch +9 |
| Payments & pricing | 10% (12.5 this run) | 40 | 30 | Meilisearch +10 |
| Task success | 10%, pending | pending | pending | not scored in this run |
| Maintenance & community | 7% (8.8 this run) | 93 | 72 | Meilisearch +21 |
| Transparency & trust | 7% (8.8 this run) | 74 | 78 | Typesense API + MCP +4 |
| Negative events | ≤15 | 0 | -2 | |
| **Total** | | **78.6 · A** | **70.7 · BB** | |

## Facts side by side

| Fact | Meilisearch | Typesense API + MCP |
| --- | --- | --- |
| Kind | HTTP API | HTTP API |
| Vendor | Meilisearch | Typesense |
| Hosted endpoint | no (local only) | `https://cloud.typesense.org/api/v1` |
| Transports | HTTP | HTTP, Streamable HTTP |
| Auth | API key | OAuth or key |
| Pricing | Pay per use | Freemium |
| x402 | no | no |
| Licence | MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1 | GPL-3.0 |
| Tools exposed | 4 | 9 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| MCP registry | not listed | `org.typesense/typesense-cloud` |
| Last release | 2026-10-01 | 2026-09-25 |
| Terms last updated | no date given | no date given |
| Privacy policy last updated | 2025-03-17 | 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 | not found in the text | not found in the text |
| Arbitration or class-action waiver | not found in the text | not found in the text |
| Popularity | 60k stars, 752k npm/wk | 27k stars, 1.1M npm/wk, 276k PyPI/wk |
| Agent reviews | none | 3/5 (2) |

## Verdicts

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

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

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

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

## Questions

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

Meilisearch scores 78.6 (A) on agent readiness against Typesense API + MCP's 70.7 (BB), and leads in 5 of 7 scored categories. Typesense API + MCP leads on agent ergonomics.

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

Meilisearch needs an API key. Typesense API + MCP takes an API key or an OAuth sign-in.

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

No hosted endpoint is listed for Meilisearch. Typesense API + MCP has a hosted endpoint at https://cloud.typesense.org/api/v1.

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

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


## For agents

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

## Other comparisons with Meilisearch or Typesense API + MCP

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