Rank #2 of 5 in Search Infrastructure
Install
Showcase


Try itExperimental
See what an agent can do with Meilisearch before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$meilisearch --db-path /tmp/pa-meili-probe --http-addr 127.0.0.1:7777 # no master key, then index 2 docs + typo search q=serverles over HTTPrecorded session — replayed, not liveVerified integrations
No integration evidence found in our corpus for this product yet — that means none was found, never that it doesn’t integrate.
By theme — the product's score on each story themeBy theme
Agent search — stories about agent search in this arenaAgent searchevidence →
Stories about agent search in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Ai search — stories about ai search in this arenaAi searchevidence →
Stories about ai search in this arena
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Developer experience — stories about developer experience in this arenaDeveloper experienceevidence →
Stories about developer experience in this arena
Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelinesevidence →
Stories about indexing pipelines in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Operations scale — stories about operations scale in this arenaOperations scaleevidence →
Stories about operations scale in this arena
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plansevidence →
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Relevance tuning — stories about relevance tuning in this arenaRelevance tuningevidence →
Stories about relevance tuning in this arena
Search experience — stories about search experience in this arenaSearch experienceevidence →
Stories about search experience in this arena
Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancyevidence →
Stories about security multitenancy in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 3 free · 1 paid · 0 enterprise · 24 not stated in evidence
Follow the green: where the map greys out is where Meilisearch stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent search — stories about agent search in this arenaAgent search
Stories about agent search in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
✓8/10
unlocks → Webhooks · Machine-readable spec · Versioning policy · Official CLI · Full data export
Subscribe to events via webhooks
—–
Build against official SDKs
✓8/10
Issue scoped/least-privilege API credentials for an agent
✓7/10
unlocks → Autonomous automations
Connect an agent via an official MCP server
✓8/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—–
Test against a sandbox environment without touching production data
~4/10
Explore an interactive API reference with runnable examples
—0/10
Docs for agents
Point an agent at llms.txt or agent-oriented docs
✓9/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
~4/10
Operate the product with natural-language commands
~6/10
unlocks → Autonomous automations
Plug MCP servers into this product so it can use their tools
n/an/a
Get AI-generated insights and suggestions from my data inside the product
~4/10
Set up automations that run autonomously in the background
—0/10
Ai search — stories about ai search in this arenaAi search
Stories about ai search in this arena
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Developer experience — stories about developer experience in this arenaDeveloper experience
Stories about developer experience in this arena
Create an index, add documents, and run my first search within minutes of starting the quickstart
!6/10
Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
!6/10
Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch
~6/10
Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines
Stories about indexing pipelines in this arena
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Operations scale — stories about operations scale in this arenaOperations scale
Stories about operations scale in this arena
Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss
~6/10
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
~4/10
Self-host the full engine — same features as the hosted product — on my own infrastructure
~6/10
Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans
Plan structure and value — what each tier costs and what it unlocks
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Relevance tuning — stories about relevance tuning in this arenaRelevance tuning
Stories about relevance tuning in this arena
Search experience — stories about search experience in this arenaSearch experience
Stories about search experience in this arena
Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancy
Stories about security multitenancy in this arena
Sorted by importance (agentic first) (high → low) · 53/53 stories · click a row’s chevron for the rationale and evidence
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | full | 8/10 | Tprobed | |
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 4/10 | Tprobed | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | n/a | 0/10 | ||
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Tprobed | |
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Xcommunity | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 7/10 | Cclaimed | |
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Tprobed | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 6/10 | Cclaimed | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 4/10 | Cclaimed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | partial | 4/10 | Cclaimed | |
Run hybrid search — semantic vector similarity fused with keyword matching — in a single query C Hybrid | developer | Ai search — stories about ai search in this arenaAi search | 3 | full | 9/10 | Cclaimed | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | fullfree | 9/10 | Xcommunity | |
Deliver as-you-type instant search with millisecond responses so results update on every keystroke C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 3 | full | 8/10 | Xcommunity | |
My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard C Agent ops | ai-native user | Agent search — stories about agent search in this arenaAgent search | 3 | full | 8/10 | Tprobed | |
Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 3 | full | 8/10 | Xcommunity | |
Create an index, add documents, and run my first search within minutes of starting the quickstart C Onboarding | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 3 | disputed | 6/10 | Dcontradicted | |
Self-host the full engine — same features as the hosted product — on my own infrastructure G Self host | platform-engineer | Operations scale — stories about operations scale in this arenaOperations scale | 3 | partialfree | 6/10 | Xcommunity | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | none | 0/10 | ||
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | none | 0/10 | ||
Published per-unit pricing (searches, records, or nodes) lets me predict what search will cost before committing G Pricing | founder | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 3 | none | 0/10 | ||
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | none | untested | none yet | |
Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query C Filtering | developer | Search experience — stories about search experience in this arenaSearch experience | 2 | full | 9/10 | Xcommunity | |
Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations C Agent ops | ai-native user | Agent search — stories about agent search in this arenaAgent search | 2 | full | 8/10 | Tprobed | |
Define synonyms and curate results — pin, boost, or hide specific hits for specific queries C Curation | developer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 2 | fullpaid | 8/10 | Cclaimed | |
Scoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per user C Tenancy | developer | Security multitenancy — stories about security multitenancy in this arenaSecurity multitenancy | 2 | full | 8/10 | Cclaimed | |
Shape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matching C Ranking | developer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 2 | full | 8/10 | Cclaimed | |
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline C Hybrid | developer | Ai search — stories about ai search in this arenaAi search | 2 | full | 8/10 | Cclaimed | |
Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss C Analytics | founder | Operations scale — stories about operations scale in this arenaOperations scale | 2 | partial | 6/10 | Cclaimed | |
Bulk-import millions of documents quickly, with async task tracking to know when indexing completes C Ingestion | platform-engineer | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 2 | partial | 6/10 | Xcommunity | |
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partialfree | 6/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 6/10 | Tprobed | |
Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more G Sdks | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 2 | disputed | 6/10 | Dcontradicted | |
Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch C Ui libraries | developer | Developer experience — stories about developer experience in this arenaDeveloper experience | 2 | partial | 6/10 | Cclaimed | |
Document adds, updates, and deletes become searchable in near real time without a full reindex C Ingestion | developer | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 2 | disputed | 5/10 | Dcontradicted | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 5/10 | Xcommunity | |
Serve query suggestions and autocomplete backed by real search traffic or a suggestions index C Experience | developer | Search experience — stories about search experience in this arenaSearch experience | 2 | partial | 5/10 | Cclaimed | |
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents C Scale | platform-engineer | Operations scale — stories about operations scale in this arenaOperations scale | 2 | partial | 4/10 | Xcommunity | |
Costs stay predictable as records and query volume grow — no surprise per-request cliffs G Pricing | founder | Pricing plans — plan structure and value — what each tier costs and what it unlocksPricing plans | 2 | disputed | 3/10 | Dcontradicted | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | 0/10 | ||
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | none | untested | none yet | |
Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIs C Rag | developer | Ai search — stories about ai search in this arenaAi search | 1 | partial | 6/10 | Cclaimed | |
Ingest content with an official crawler or connectors instead of writing my own indexing pipeline C Connectors | founder | Indexing pipelines — stories about indexing pipelines in this arenaIndexing pipelines | 1 | partial | 4/10 | Cclaimed | |
Inspect ranking scores or explanations to understand exactly why a result ranked where it did C Ranking | platform-engineer | Relevance tuning — stories about relevance tuning in this arenaRelevance tuning | 1 | none | 0/10 | ||
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | n/a | untested | none yet |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 31 stories with headroom
What would move Meilisearch’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Automation depth — how much of the product can run unattendedDefine rules that trigger actions automatically on events
nonemoves PA Scoreimpact 30
Meilisearch's evidence describes ranking/relevancy rules (typo tolerance, ranking rules, dynamic search rules for boosting/pinning results) and tenant tokens applied per search request, but none of this constitutes user-defined rules that trigger automated actions in response to events (e.g., webhooks, event-driven workflows).
Openness — open source, data portability, and self-hosting storiesExport all of my data in open formats and leave
nonemoves PA Scoreimpact 30
The evidence covers self-hosting, installation, and various search capabilities, but nowhere documents a data export/dump feature or open-format data portability mechanism that would let a user extract all their indexed documents and leave.
Privacy posture — data-handling and privacy storiesPrevent my data from being used to train AI models
nonemoves PA Scoreimpact 30
Missing: explicit privacy policy or docs statement on AI/model training data usage, opt-out mechanism, or contractual guarantee.
Pricing plans — plan structure and value — what each tier costs and what it unlocksPublished per-unit pricing (searches, records, or nodes) lets me predict what search will cost before committing
nonemoves PA Scoreimpact 30
The evidence pack shows a pricing page exists (mentioning feature tiers like 'Dynamic Search Rules' and a '14-day free trial') but never publishes concrete per-unit rates for searches, records, or nodes that a founder could use to forecast costs.
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
Missing: any scheduler/automation engine, background trigger system, or autonomous agent workflow capability.
Agenticness — how well agents can access and operate the productUse an official CLI
nonemoves agent-readyimpact 30
The evidence pack shows a self-hosted single binary, SDKs, Docker/Kubernetes integrations, and an official MCP server for natural-language interaction, but there is no mention of a dedicated official CLI tool for AI-native workflows (e.g., a `meilisearch-cli` package or command-line client distinct from the server binary itself).
Agenticness — how well agents can access and operate the productSubscribe to events via webhooks
nonemoves agent-readyimpact 30
No evidence in the pack mentions webhooks or event subscription mechanisms; only search, indexing, security, analytics, and MCP integration capabilities are documented.
Agenticness — how well agents can access and operate the productExplore an interactive API reference with runnable examples
nonemoves API qualityimpact 30
The evidence pack shows no interactive API reference or runnable-example playground; the openapi probe explicitly found all candidate OpenAPI/Swagger endpoints returning 404, and docs pages described are static markdown guides, not runnable interactive references.
Showing the top 8 of 31 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map9 surfaces · 36 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
docs30 stories
- My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard
- Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Issue scoped/least-privilege API credentials for an agent
- Get AI-generated insights and suggestions from my data inside the product
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Test against a sandbox environment without touching production data
- Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline
- Run hybrid search — semantic vector similarity fused with keyword matching — in a single query
- Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIs
- Perform bulk operations across many items at once
- Create an index, add documents, and run my first search within minutes of starting the quickstart
- Document adds, updates, and deletes become searchable in near real time without a full reindex
- Do everything through the API that I can do in the UI
- Self-host the core product
- Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and miss
- Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Choose where my data is stored (region/residency)
- Define synonyms and curate results — pin, boost, or hide specific hits for specific queries
- Shape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matching
- Serve query suggestions and autocomplete backed by real search traffic or a suggestions index
- Deliver as-you-type instant search with millisecond responses so results update on every keystroke
- Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies
- Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query
- Scoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per user
Integrations docs15 stories
- My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard
- Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operations
- Run the product headlessly / in CI for automation
- Connect an agent via an official MCP server
- Drive the product through a documented public API
- Build against official SDKs
- Delegate tasks to a built-in AI assistant inside the product
- Operate the product with natural-language commands
- Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
- Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratch
- Ingest content with an official crawler or connectors instead of writing my own indexing pipeline
- Self-host the core product
- Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Choose where my data is stored (region/residency)
Hacker News14 stories
- Build against official SDKs
- Perform bulk operations across many items at once
- Create an index, add documents, and run my first search within minutes of starting the quickstart
- Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
- Bulk-import millions of documents quickly, with async task tracking to know when indexing completes
- Document adds, updates, and deletes become searchable in near real time without a full reindex
- Self-host the core product
- Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documents
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Costs stay predictable as records and query volume grow — no surprise per-request cliffs
- Choose where my data is stored (region/residency)
- Deliver as-you-type instant search with millisecond responses so results update on every keystroke
- Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies
- Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query
Products docs7 stories
- Get AI-generated insights and suggestions from my data inside the product
- Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipeline
- Run hybrid search — semantic vector similarity fused with keyword matching — in a single query
- Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIs
- Deliver as-you-type instant search with millisecond responses so results update on every keystroke
- Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching applies
- Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single query
Pricing docs5 stories
- Test against a sandbox environment without touching production data
- Self-host the full engine — same features as the hosted product — on my own infrastructure
- Costs stay predictable as records and query volume grow — no surprise per-request cliffs
- Define synonyms and curate results — pin, boost, or hide specific hits for specific queries
- Shape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matching
Solutions docs5 stories
- My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboard
- Drive the product through a documented public API
- Build against official SDKs
- Official SDKs cover my language and framework, kept current across JavaScript, Python, PHP, Ruby, Go, and more
- Scoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per user
Cloud docs3 stories
llms.txt2 stories
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$meilisearch --db-path /tmp/pa-meili-probe --http-addr 127.0.0.1:7777 # no master key, then index 2 docs + typo search q=serverles over HTTPreproduced$ meilisearch --db-path /tmp/pa-meili-probe --http-addr 127.0.0.1:7777 # no master [redacted], then index 2 docs + typo search q=serverles over HTTP
{"taskUid":0,"indexUid":"arenas","status":"enqueued","type":"documentAdditionOrUpdate","enqueuedAt":"2026-09-06T22:13:03.252318Z"}
{"hits":[{"id":1,"name":"serverless databases"}],"query":"serverles","processingTimeMs":0,"limit":20,"offset":0,"estimatedTotalHits":1,"requestUid":"01a078c8-4285-7e93-89c4-fe2630149201"}
$printf '<jsonrpc initialize>' | uvx meilisearch-mcp # stdio handshake, no Meilisearch instancereproduced$ printf '<jsonrpc initialize>' | uvx meilisearch-mcp # stdio handshake, no Meilisearch instance
{"jsonrpc":"2.0","id":1,"result":{"capabilities":{"experimental":{},"prompts":{"listChanged":false},"resources":{"listChanged":false,"subscribe":false},"tools":{"listChanged":false}},"protocolVersion":"2025-06-18","serverInfo":{"name":"meilisearch","version":"0.7.0"}}}
$meilisearch --version # installed via `brew install meilisearch`reproduced$ meilisearch --version # installed via `brew install meilisearch` meilisearch 1.53.1
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
5 of 14 testable claims verified · 1 contradicted → integrity 21/100
19 distinct capability claims found in Meilisearch’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
5
Verified
8
Unverified
1
Contradicted
19
Undersold
Verified (7)
“Typo-tolerant search returns relevant results even with spelling mistakes”
Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching appliesfullproof ↗
“Faceted navigation lets shoppers filter by brand, color, size, and price with live counts”
Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single queryfullproof ↗
“Runs as a single dependency-free binary on Linux, macOS, or Windows, bare metal or containers”
Self-host the full engine — same features as the hosted product — on my own infrastructurepartialproof ↗
“Native clustering support guarantees read high availability”
Documented scaling paths — clustering, replication, high availability — carry me from prototype to hundreds of millions of documentspartialproof ↗
“Indexes, documents, settings, and searches can be managed via natural-language prompts”
Operate the product with natural-language commandspartialproof ↗
“Typo tolerance thresholds can be tuned per index via minWordSizeForTypos”
Searches tolerate typos and misspellings out of the box, with tunable rules for when and how fuzzy matching appliesfullproof ↗
“Facets and filters combine to build interactive, ecommerce-style navigation”
Build faceted navigation — filters with live counts across categories, ranges, and attributes — from a single queryfullproof ↗
Unverified (9)
“Single API exposes full-text, semantic, and conversational search over your documents and embeddings”
Power RAG and conversational answers on top of my indexes with documented retrieval or answer APIspartialproof ↗
“Seven built-in ranking rules determine relevance and their order can be customized”
Shape relevance with custom ranking rules and business signals (popularity, recency, margin) beyond textual matchingfullproof ↗
“Synonym lists can be defined so equivalent words return more relevant results”
Define synonyms and curate results — pin, boost, or hide specific hits for specific queriesfullproof ↗
“Dedicated facet-search endpoint powers autocomplete/type-ahead on individual facet values”
Serve query suggestions and autocomplete backed by real search traffic or a suggestions indexpartialproof ↗
“Configuring an embedder auto-generates vector embeddings for every document, no manual embedding pipeline needed”
Use built-in or managed embedders so documents and queries are vectorized without running my own embedding pipelinefullproof ↗
“Built-in analytics track search queries, click events, and conversions to measure search quality”
Built-in analytics show top queries, no-result queries, and click-through so I know what users search for and misspartialproof ↗
“Tenant tokens are scoped, short-lived credentials that restrict each user's search to their own data”
Scoped or tenant tokens restrict each end user's searches to their own documents without separate indexes per userfullproof ↗
“Dynamic search rules can boost, pin, or bury results based on the context of each request”
Define synonyms and curate results — pin, boost, or hide specific hits for specific queriesfullproof ↗
“Hybrid search fuses full-text keyword matching with semantic vector search in a single query”
Run hybrid search — semantic vector similarity fused with keyword matching — in a single queryfullproof ↗
Contradicted (1)
“Quickstart lets you create an index, add documents, and run your first search in minutes”
Create an index, add documents, and run my first search within minutes of starting the quickstartdisputedproof ↗
Undersold (19)
My coding agent can create an index, add documents, and run queries end to end — through the API, CLI, or MCP without touching a dashboardfullproof ↗
Agents can use my search indexes as a tool — an MCP server or tool-calling surface exposes query, analytics, and index operationsfullproof ↗
Point an agent at llms.txt or agent-oriented docsfullproof ↗
Run the product headlessly / in CI for automationpartialproof ↗
Drive the product through a documented public APIfullproof ↗
Issue scoped/least-privilege API credentials for an agentfullproof ↗
Get AI-generated insights and suggestions from my data inside the productpartialproof ↗
Delegate tasks to a built-in AI assistant inside the productpartialproof ↗
Test against a sandbox environment without touching production datapartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
Official UI component libraries let me assemble a full search interface — box, results, facets, pagination — without building it from scratchpartialproof ↗
Ingest content with an official crawler or connectors instead of writing my own indexing pipelinepartialproof ↗
Bulk-import millions of documents quickly, with async task tracking to know when indexing completespartialproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Choose where my data is stored (region/residency)partialproof ↗
Deliver as-you-type instant search with millisecond responses so results update on every keystrokefullproof ↗
Claims outside our story set (2)
Real capability claims found in Meilisearch’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Geosearch combined with faceting improves result relevancy”
source ↗“Personalization adapts search results for each user based on their preferences and behavior”
source ↗
Business model
Open-source engine (MIT core, BUSL-1.1 Enterprise Edition parts), free to self-host; Meilisearch Cloud has a free tier, then flat plans with usage-based overages and custom enterprise contracts.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
