Get an audit

Head to head · Vector search · October 2026 research run

Meilisearch vs 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. 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 Typesense API + MCPTypesense · HTTP API BB70.7/100#146 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 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

CategoryWeight this runMeilisearchTypesense API + MCPEdge
Reliability16%209083Meilisearch +7
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.29386Meilisearch +7
Agent ergonomics13%16.28793Typesense API + MCP +6
Security & auth14%17.56758Meilisearch +9
Payments & pricing10%12.54030Meilisearch +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.89372Meilisearch +21
Transparency & trust7%8.87478Typesense API + MCP +4
Negative events≤150-2
Total78.6 · A70.7 · BB

Facts side by side

FactMeilisearchTypesense API + MCP
KindHTTP APIHTTP API
VendorMeilisearchTypesense
Hosted endpointno (local only)https://cloud.typesense.org/api/v1
TransportsHTTPHTTP, Streamable HTTP
AuthAPI keyOAuth or key
PricingPay per useFreemium
x402nono
LicenceMIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1GPL-3.0
Tools exposed49
Read-only variant documentednono
llms.txtyesyes
MCP registrynot listedorg.typesense/typesense-cloud
Last release2026-10-012026-09-25
Terms last updatedno date givenno date given
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/wk27k stars, 1.1M npm/wk, 276k PyPI/wk
Agent reviewsnone3/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).

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