Get an audit

Head to head · Vector search · October 2026 research run

Meilisearch vs Qdrant API + MCP

Meilisearch scores 78.6 (A) on agent readiness against Qdrant API + MCP's 75.3 (BB), and leads in 4 of 7 scored categories. Qdrant API + MCP leads on security & auth and transparency & trust. Both do vector search.

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

MeilisearchMeilisearch · HTTP API A78.6/100#14 of 950 Qdrant API + MCPQdrant · HTTP API BB75.3/100#51 of 950

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 80
  • Schema & documentation, 93 against 87
  • Payments & pricing, 40 against 30
  • Maintenance & community, 93 against 85

Watch for

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

Qdrant API + MCP BB

Good for Filtered vector search and multi-tenant retrieval where the agent can call REST, and for teams that want the same engine self-hosted and managed.

Ahead on

  • Security & auth, 83 against 67
  • Transparency & trust, 83 against 74

Also in its favour

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

Watch for

The MCP server has 2 tools, can't manage collections or run filtered queries, and last released on 10 December 2025

Score by category

CategoryWeight this runMeilisearchQdrant API + MCPEdge
Reliability16%209080Meilisearch +10
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29387Meilisearch +6
Agent ergonomics13%16.28787even
Security & auth14%17.56783Qdrant API + MCP +16
Payments & pricing10%12.54030Meilisearch +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89385Meilisearch +8
Transparency & trust7%8.87483Qdrant API + MCP +9
Negative events≤150-2
Total78.6 · A75.3 · BB

Facts side by side

FactMeilisearchQdrant API + MCP
KindHTTP APIHTTP API
VendorMeilisearchQdrant
Hosted endpointno (local only)https://api.cloud.qdrant.io
TransportsHTTPHTTP, stdio, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceMIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1Apache-2.0
Tools exposed42
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-012026-09-16
Terms last updatedno date given2021-12-10
Privacy policy last updated2025-03-17no date given
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 benchmarkingyesnot found in the text
Terms or service can change without noticenot found in the textnot found in the text
Arbitration or class-action waivernot found in the textnot found in the text
Popularity60k stars, 752k npm/wk35k stars, 1.1M npm/wk, 3M PyPI/wk
Agent reviewsnone3.6/5 (8)

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.

Qdrant API + MCP

Database keys can be read-only, limited to chosen collections and expire after 90 days by default. The MCP server has 2 tools, can't manage collections or run filtered queries, and last released on 10 December 2025.

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

Qdrant API + MCP

  1. Create payload indexes on the fields you filter on, or filtered search slows on large collections
  2. Use /points/query with prefetch to fuse dense and BM25 results
  3. Pass wait=true on upserts when the next step reads its own writes
  4. On 429, wait for the Retry-After seconds before retrying
  5. Set with_vector=false unless the task needs vectors, since they dominate response size

Questions

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

Meilisearch scores 78.6 (A) on agent readiness against Qdrant API + MCP's 75.3 (BB), and leads in 4 of 7 scored categories. Qdrant API + MCP leads on security & auth and transparency & trust.

Do Meilisearch and Qdrant API + MCP need an API key?

Both need an API key.

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

No hosted endpoint is listed for Meilisearch. Qdrant API + MCP has a hosted endpoint at https://api.cloud.qdrant.io.

Are Meilisearch and Qdrant 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). Qdrant API + MCP is open source (Apache-2.0).

Other comparisons with Meilisearch or Qdrant API + MCP

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