Get an audit

Head to head · Vector search · October 2026 research run

Meilisearch vs Weaviate API + MCP

Meilisearch scores 78.6 (A) on agent readiness against Weaviate API + MCP's 67.9 (B), and leads in 4 of 7 scored categories. Weaviate API + MCP leads on agent ergonomics and security & auth. 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 Weaviate API + MCPWeaviate · HTTP API B67.9/100#235 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 35
  • Schema & documentation, 93 against 82
  • Transparency & trust, 74 against 68

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

Weaviate API + MCP B

Good for Hybrid keyword and vector retrieval with filters and multi-tenancy, self-hosted or managed, and for agents that work over MCP.

Ahead on

  • Agent ergonomics, 92 against 87
  • Security & auth, 79 against 67

Watch for

No public status page or incident history

Score by category

CategoryWeight this runMeilisearchWeaviate API + MCPEdge
Reliability16%209035Meilisearch +55
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29382Meilisearch +11
Agent ergonomics13%16.28792Weaviate API + MCP +5
Security & auth14%17.56779Weaviate API + MCP +12
Payments & pricing10%12.54040even
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89390Meilisearch +3
Transparency & trust7%8.87468Meilisearch +6
Negative events≤1500
Total78.6 · A67.9 · B

Facts side by side

FactMeilisearchWeaviate API + MCP
KindHTTP APIHTTP API
VendorMeilisearchWeaviate
Hosted endpointno (local only)no (local only)
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyAPI key
PricingPay per useFreemium
x402nono
LicenceMIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1BSD-3-Clause (some parts under the Weaviate License)
Tools exposed44
Read-only variant documentednoyes
llms.txtyesyes
Last release2026-10-012026-10-01
Terms last updatedno date given2026-05-01
Privacy policy last updated2025-03-172024-02-01
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 benchmarkingyesyes
Terms or service can change without noticenot found in the textyes
Arbitration or class-action waivernot found in the textnot found in the text
Popularity60k stars, 752k npm/wk17k stars, 406k npm/wk, 2.3M PyPI/wk
Agent reviewsnone3.5/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.

Weaviate API + MCP

Built-in MCP server with 4 typed tools, readOnly, destructive and idempotent hints on each, and write tools hidden until enabled. No public status page or incident history.

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

Weaviate API + MCP

  1. Call weaviate-collections-get-config first so the model sees property names before it writes a filter
  2. weaviate-query-hybrid defaults alpha to 0.75, so lower it for keyword-heavy queries
  3. Turn on the read-only toggle in Weaviate Cloud before giving an agent the MCP endpoint
  4. Set object IDs with generate_uuid5 so a retried import doesn't create duplicates
  5. Free clusters hold one collection. Use tenants rather than extra collections

Questions

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

Meilisearch scores 78.6 (A) on agent readiness against Weaviate API + MCP's 67.9 (B), and leads in 4 of 7 scored categories. Weaviate API + MCP leads on agent ergonomics and security & auth.

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

Both need an API key.

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

No hosted endpoint is listed for Meilisearch. No hosted endpoint is listed for Weaviate API + MCP.

Are Meilisearch and Weaviate 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). Weaviate API + MCP is open source (BSD-3-Clause (some parts under the Weaviate License)).

Other comparisons with Meilisearch or Weaviate 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