Head to head · Vector search · October 2026 research run
Elasticsearch vs Meilisearch
Meilisearch scores 78.6 (A) on agent readiness against Elasticsearch's 67.7 (B), and leads in 6 of 7 scored categories. Elasticsearch leads on security & auth. Both do vector search.
Best vector search and retrieval databases for AI agents · All 85 retrieval comparisons
Which one, for what
Good for Retrieval that needs keyword relevance, filters and vectors in one query, and teams already running Elastic for logs or security.
Ahead on
- Security & auth, 72 against 67
Watch for
More than 20 status notices marked major between 10 July and 8 October 2026, three of them regional service incidents
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 62
- Schema & documentation, 93 against 88
- Agent ergonomics, 87 against 77
- Payments & pricing, 40 against 35
- Maintenance & community, 93 against 83
Also in its favour
- Agent-ready, a grade of BB or better
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 this run | Elasticsearch | Meilisearch | Edge |
|---|---|---|---|---|
| Reliability | 16%20 | 62 | 90 | Meilisearch +28 |
| Performance | 10%pending | pending | pending | not scored in this run |
| Schema & documentation | 13%16.2 | 88 | 93 | Meilisearch +5 |
| Agent ergonomics | 13%16.2 | 77 | 87 | Meilisearch +10 |
| Security & auth | 14%17.5 | 72 | 67 | Elasticsearch +5 |
| Payments & pricing | 10%12.5 | 35 | 40 | Meilisearch +5 |
| Task success | 10%pending | pending | pending | not scored in this run |
| Maintenance & community | 7%8.8 | 83 | 93 | Meilisearch +10 |
| Transparency & trust | 7%8.8 | 71 | 74 | Meilisearch +3 |
| Negative events | ≤15 | -2 | 0 | |
| Total | 67.7 · B | 78.6 · A |
Facts side by side
| Fact | Elasticsearch | Meilisearch |
|---|---|---|
| Kind | HTTP API | HTTP API |
| Vendor | Elastic | Meilisearch |
| Hosted endpoint | no (local only) | no (local only) |
| Transports | HTTP | HTTP |
| Auth | OAuth or key | API key |
| Pricing | Pay per use | Pay per use |
| x402 | no | no |
| Licence | AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The x-pack folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms | MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1 |
| Tools exposed | none | 4 |
| Read-only variant documented | no | no |
| llms.txt | yes | yes |
| Last release | 2026-10-06 | 2026-10-01 |
| Terms last updated | couldn't be read | no date given |
| Privacy policy last updated | 2026-09-07 | 2025-03-17 |
| Customer content may train models | couldn't be read | not found in the text |
| Terms restrict automated access | couldn't be read | not found in the text |
| Terms restrict benchmarking | couldn't be read | yes |
| Terms or service can change without notice | couldn't be read | not found in the text |
| Arbitration or class-action waiver | couldn't be read | not found in the text |
| Popularity | 3.1M npm/wk, 7.8M PyPI/wk | 60k stars, 752k npm/wk |
Verdicts
Elasticsearch
Keyword, dense and sparse vector, and hybrid search with rank fusion sit behind one OpenAPI-described REST API, with API keys scoped to indices and privileges. The status page lists more than 20 incidents marked major since July 2026, and Elasticsearch 9.5.0 returned incorrect results for some queries without raising an error.
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
Elasticsearch
- Send
Authorization: ApiKey <key>to the project's Elasticsearch URL. The MCP server is on the Kibana URL at/api/agent_builder/mcp - Create the MCP key with
feature_agentBuilder.readand only the index patterns needed, or the endpoint answers 403 - On 429, wait and retry with exponential backoff. Do not set short client timeouts, because a retried request joins the back of the queue
- Page past 10,000 hits with
search_after, notfromandsize - Tool calls made directly through the Tools API skip Agent Builder's confirmation prompts, so restrict the key instead
Meilisearch
- Create a key with only
search,documents.getandindexes.geton the indexes needed. The default search key failslistIndexesanddescribeIndexover MCP - Enable the
mcpRouteexperimental feature first. Until then/mcpanswersfeature_not_enabled - For hybrid search send
hybridwith anembeddername configured in the index settings and asemanticRatiofrom 0 to 1 - Writes return a
taskUidand run asynchronously. Poll the task before searching for the new documents - On 503
too_many_search_requests, wait for theRetry-Afterheader (10 seconds) before retrying
Questions
Which is better for AI agents, Elasticsearch or Meilisearch?
Meilisearch scores 78.6 (A) on agent readiness against Elasticsearch's 67.7 (B), and leads in 6 of 7 scored categories. Elasticsearch leads on security & auth.
Do Elasticsearch and Meilisearch need an API key?
Elasticsearch takes an API key or an OAuth sign-in. Meilisearch needs an API key.
Can an agent call Elasticsearch and Meilisearch without installing anything?
No hosted endpoint is listed for Elasticsearch. No hosted endpoint is listed for Meilisearch.
Are Elasticsearch and Meilisearch open source?
Yes. Elasticsearch is open source (AGPL-3.0, SSPL-1.0 or Elastic Licence 2.0 at the user's choice for most source. The `x-pack` folder is under Elastic Licence 2.0 only. Elastic Cloud is a proprietary service under Elastic's terms). Meilisearch is open source (MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1).
Other comparisons with Elasticsearch or Meilisearch
- Chroma API + MCP vs Elasticsearch
- Chroma API + MCP vs Meilisearch
- Elasticsearch vs Epsilla Vector Database
- Elasticsearch vs LanceDB
- Elasticsearch vs Milvus and Zilliz Cloud API + MCP
- Elasticsearch vs OpenSearch
- Elasticsearch vs Pinecone API + MCP
- Elasticsearch vs Qdrant API + MCP
- Elasticsearch vs Typesense API + MCP
- Elasticsearch vs Upstash Vector API + MCP
- Elasticsearch vs Vespa
- Elasticsearch vs Weaviate API + MCP
- Epsilla Vector Database vs Meilisearch
- LanceDB vs Meilisearch
- Meilisearch vs Milvus and Zilliz Cloud API + MCP
- Meilisearch vs OpenSearch
- Meilisearch vs Pinecone API + MCP
- Meilisearch vs Qdrant API + MCP
- Meilisearch vs Typesense API + MCP
- Meilisearch vs Upstash Vector API + MCP
- Meilisearch vs Vespa
- Meilisearch vs Weaviate API + MCP
Machine-readable
- This page as Markdown
/compare/elasticsearch-vs-meilisearch.md· slim.min.md· JSON.json(or sendAccept: text/markdown) - Each listing in full
/api/v1/tools/elasticsearch.json·/api/v1/tools/meilisearch.json - From a terminal
anchor compare elasticsearch meilisearch(the CLI) - Over MCP
compare_tools {"a": "elasticsearch", "b": "meilisearch"}at/mcp, no key