# Meilisearch > Open-source search engine from Meili SAS in Paris with typo-tolerant keyword search, vector and hybrid search, filters and facets. It runs self-hosted or as Meilisearch Cloud, with a REST API, SDKs and an experimental built-in MCP route. - Canonical: https://www.anchorterminal.com/tools/meilisearch - Markdown: https://www.anchorterminal.com/tools/meilisearch.md (~7,450 tokens) - Slim: https://www.anchorterminal.com/tools/meilisearch.min.md (~1,880 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/meilisearch.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (full text: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - Updated: 2026-10-09 ## Overview **Grade A · 78.6/100 · rank #14 of 950 · #1 in Retrieval & vector search · agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Meilisearch (https://www.meilisearch.com) | | Kind | HTTP API | | Category | Retrieval & vector search (https://www.anchorterminal.com/categories/vector-search) | | Transport | HTTP | | Auth | API key · Every route except `/health` takes an API key as `Authorization: Bearer`. Keys are limited to named actions (`search`, `documents.add`, `indexes.get` and others) and to named indexes, with an optional expiry, and are created through `/keys` with the master key. Tenant tokens are short-lived tokens signed from a key that embed search filters for one user. A Cloud project is created by a person signed in at cloud.meilisearch.com, which generates the master key. The MCP route takes the same Bearer key and has no OAuth flow. | | Pricing | Pay per use ($30 / mo) · Meilisearch Cloud has a 14-day trial with no card. After that the usage-based Build plan includes 50,000 searches and 100,000 documents a month, then $0.40 per 1,000 searches and $0.30 per 1,000 documents. Resource-based projects pay hourly by instance size plus disk and bandwidth. Enterprise is by quote. The self-hosted Community Edition is free under MIT (https://www.meilisearch.com/pricing). | | x402 | No · No x402, MPP or L402 in the docs, the OpenAPI file or the pricing page (checked 2026-10-09). | | Licence | MIT for the Community Edition. Enterprise Edition code, which powers Meilisearch Cloud, is BUSL-1.1 | | Tools exposed | 4 | | Packages | npm: `meilisearch`; pypi: `meilisearch` | | Source | https://github.com/meilisearch/meilisearch | | Docs | https://www.meilisearch.com/docs | | llms.txt | https://www.meilisearch.com/llms.txt | | Last release | 2026-10-01 | | GitHub stars | 59,529 (as of 2026-10-09) | | npm downloads / week | 752,198 | | Surface graded | Meilisearch Cloud through the REST API (v1.54.3). The same API runs self-hosted from the MIT Community Edition | | Search modes | Typo-tolerant keyword, semantic (vector) and hybrid with `semanticRatio` from 0 to 1, filters, facets, sorting, geo search and federated multi-index search. Embeddings generated by a configured embedder (OpenAI, Cohere, Mistral, Hugging Face, Gemini, Voyage and others, or any REST endpoint) or supplied by the caller | | MCP server | Built in at `POST /mcp` since v1.54 (21 September 2026), experimental, enabled with the `mcpRoute` feature. Four read-only tools (`listIndexes`, `describeIndex`, `searchInIndexes`, `facetSearch`), MCP protocol version 2026-07-28, API key as Bearer, no OAuth. The older `meilisearch-mcp` Python package is deprecated | | Credentials | Bearer API keys limited to named actions and indexes with optional expiry, a default admin key and a default search key, and tenant tokens that embed search rules. The `/keys` route needs the master key | | Free trial | 14 days on Cloud, no card (https://www.meilisearch.com/pricing) | | Cloud billing | Usage-based Build plan at $30 a month in the estimator with 50,000 searches and 100,000 documents, then $0.40 per 1,000 searches and $0.30 per 1,000 documents. Resource-based projects pay hourly by instance size (XS, 0.5 vCPU and 1 GB RAM, $18 a month in the estimator), plus disk at $0.165 per GiB with a 32 GB minimum and bandwidth at $0.15 per GB. Enterprise by quote | | Limits | 1,000 concurrent searches, then 503 `too_many_search_requests` with `Retry-After` of 10 seconds. 1,000 results a search by default (`pagination.maxTotalHits`), 10 query words, 100 facet values in facet search. No Cloud request rate limit published | | Update delay | Not published. Writes are queued as asynchronous tasks and return a `taskUid`. We haven't measured the delay | | Regions | Nine on Cloud. Frankfurt, Paris, London, Singapore, Japan, Sydney, San Francisco, New York and São Paulo. A project's region can't be changed | | SLA | 99.9 per cent monthly uptime with service credits of 10 to 30 per cent, Enterprise plans only. The pricing page advertises up to 99.999 per cent by contract | | Self-hosted | Community Edition under MIT as a single binary or Docker image. Enterprise Edition (sharding) under BUSL-1.1. Telemetry is on by default and `--no-analytics` turns it off | | SDKs | Official clients for JavaScript (meilisearch 0.62.0 on npm), Python, PHP, Ruby, Java, Go, .NET and Dart, plus Laravel, Rails, Strapi and Firebase integrations | | Capabilities | db.vector, db.hybrid, db.fulltext, db.filters | | Tags | hosted, usage, free-trial, no-card, open-source, self-hosted, mcp, openapi, llms-txt, typescript, python, status-page, soc2 | | JSON | https://www.anchorterminal.com/api/v1/tools/meilisearch.json | ## Score breakdown (methodology v0.4, October 2026 research run) Assessed 2026-10-09 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 90 | 18.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 93 | 15.1 | | Agent ergonomics | 13% | 16.2 | 87 | 14.1 | | Security & auth | 14% | 17.5 | 67 | 11.7 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 93 | 8.1 | | Transparency & trust (editorial 72, provenance 76) | 7% | 8.8 | 74 | 6.5 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **78.6 → A** | ### Why each score - Reliability 90: Graded as the hosted Meilisearch Cloud service. BetterStack status page with nine regional clusters, the Cloud front end, the Cloud API, the landing page and the docs as components (20). Over 90 days it shows one incident, 16 minutes of downtime on the San Francisco cluster on 24 July 2026 (30). Engine limits are published with numbers (1,000 concurrent searches, 1,000 results a search by default, 10 query words), but no per-plan request rate limit for Cloud was found, although the monitoring docs name rate limiting as a cause of failed calls (8 of 15). A full search queue answers 503 `too_many_search_requests` with `Retry-After` set to 10 seconds, and document writes are keyed by primary key so a repeated write replaces the same document. No idempotency keys (12 of 15). A 99.9 per cent monthly uptime SLA with service credits is published for Enterprise plans (10). The REST API is at 1.54 and generally available. The MCP route is experimental and is not the surface graded here (10). - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 93: OpenAPI 3.1.0 file for v1.54.3 with 72 paths and 143 operations, linked from the docs, attached to each release and regenerated in a daily CI check (25). llms.txt on the main site (10). Every operation has a description and search parameters explain defaults and interactions. The four MCP tool descriptions are one line each (16 of 20). 219 schemas, 41 with enums. `filter` is a free-form expression string (12 of 15). Code samples in several languages, 142 of 143 operations document a 4xx response, and an error reference lists 290 codes, each with a type and a docs link (15). Semantic versioning, a dated changelog with an RSS feed and GitHub releases (15). - Agent ergonomics 87: `attributesToRetrieve`, `limit`, `cropLength` and `rankingScoreThreshold` size a search response, and the MCP route has four tools, with `describeIndex` capped at five sample documents (22 of 25). `offset` and `limit` or `page` and `hitsPerPage`, filters, facets and sorting (20). Errors return `message`, `code`, `type` and `link` (20). No idempotency keys. Writes by primary key are safe to repeat, and the MCP tool definition in the source has no annotations field, so no readOnlyHint is sent although all four tools only read (10 of 20). Search has no required parameter, and official clients cover JavaScript, Python, PHP, Ruby, Java, Go, .NET and Dart (15). - Security & auth 67: API keys are limited to named actions and indexes with an optional expiry, tenant tokens embed search rules for each user, keys are sent only in the `Authorization` header and the docs describe rotation (30). A default search-only key, a warning against `*` keys and a read-only MCP route. No confirmation step for destructive calls (15 of 20). Search returns stored documents as written. Guardrail guidance exists for the chat feature, none was found for the MCP route (5 of 15). The Cloud dashboard charts failed and successful API calls, and no audit log was found in the docs (3 of 15). security.txt valid to 26 May 2027, a SECURITY.md that promises a reply within 72 hours, and SOC 2 Type II stated on the pricing page. No bug bounty found, no advisories published on the repository, and the trust centre could not be read (14 of 20). - Payments & pricing 40: Graded on Meilisearch Cloud. No x402, MPP or L402 (0). Unit prices are public. The Build plan includes 50,000 searches and 100,000 documents a month, then $0.40 per 1,000 searches and $0.30 per 1,000 documents, and resource-based projects pay an hourly instance rate plus $0.165 per GiB of disk and $0.15 per GB of bandwidth (20). 14-day trial with no card (20). A person registers in a browser at cloud.meilisearch.com, and no programmatic sign-up was found (0). The self-hosted Community Edition is free under MIT. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 93: v1.54.3 tagged 1 October 2026 (30). v1.52 on 3 August, v1.53 on 10 August and v1.54 on 21 September 2026, plus patch releases (20). Of the 14 newest open issues, 11 had at least one reply, and the repository shows 321 open issues and pull requests against 59,529 stars. A Discord server is linked (20 of 25). Official clients are current, with meilisearch-js at 0.62.0 (15). A test suite, SDK tests and a daily OpenAPI check run in GitHub Actions with pinned action versions. We did not confirm the latest run passed (8 of 10). - Transparency & trust 74: The Community Edition is MIT. Enterprise Edition code, which powers Cloud and adds sharding, is under BUSL-1.1 (27 of 30). The privacy policy of 17 March 2025 names Meili SAS as controller and gives retention periods (the contract term, five years for liability, ten for invoices, three for prospects, six months for navigation data). It sends readers to the trust centre for sub-processors, which we could not read, and no DPA was linked from the pages read. The terms date from 18 March 2022 (20 of 30). A versioning policy commits to semantic versioning and says only the latest release is maintained, with no end-of-life policy. Breaking changes to experimental routes are called out in the changelog (10 of 20). Self-hosted telemetry is documented in full with a `--no-analytics` opt-out, and nine Cloud regions are listed (15 of 20). Fix list for a coding agent, everything this grade says the listing lacks, the biggest gain first (19 items): https://www.anchorterminal.com/fixes/meilisearch.md (JSON https://www.anchorterminal.com/fixes/meilisearch.json) ### What we couldn't check - unchecked: trust.meilisearch.com (sub-processor list, SOC 2 report, DPA). The request for its robots.txt failed at the TLS handshake from our network, so the host was treated as closed - unchecked: whether Meilisearch is in the official MCP registry - unchecked: cloud.meilisearch.com sign-up flow and the per-region instance rates, which the docs say appear only in the Cloud console - unchecked: PyPI download figures and the Python client's latest version (PyPI's robots.txt closes `/pypi/`) - Whether Cloud enforces a request rate limit, and at what number. The monitoring docs mention one and give no figure - The pricing page says Cloud starts at $20 a month while its estimator's lowest figures are $23 (resource-based XS) and $30 (Build plan) - The terms of use forbid comparative analysis of the service. This matters before any probe is run. No deduction taken - Cloud project hosts are on meilisearch.io, a second domain, which the provenance check may read as off the vendor's domain ### Sources - robots.txt for www.meilisearch.com (200, allows all but /api/, /_next/ and /private/): (seen 2026-10-09) - home page: (seen 2026-10-09) - llms.txt: (seen 2026-10-09) - pricing page: (seen 2026-10-09) - terms of use, in force 18 March 2022: (seen 2026-10-09) - privacy policy, updated 17 March 2025: (seen 2026-10-09) - service level agreement: (seen 2026-10-09) - security.txt: (seen 2026-10-09) - status page (robots.txt answered 200 with an empty body): (seen 2026-10-09) - docs source, read from a clone (MCP, API keys, pricing model, regions, errors, known limitations, versioning, telemetry, changelog): (seen 2026-10-09) - OpenAPI file, read from the docs repository copy and not the rendered reference: (seen 2026-10-09) - engine source, read from a clone (licence, SECURITY.md, tags, CI workflows, `crates/meilisearch/src/routes/mcp.rs`): (seen 2026-10-09) - repository metadata, advisories and newest open issues from the GitHub API: (seen 2026-10-09) - npm package version and weekly downloads: (seen 2026-10-09) - domain registration (RDAP; robots.txt answered 400): (seen 2026-10-09) ## Who's behind it (provenance 76/100, checked 2026-10-09) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Meili SAS | 20/20 | | Domain age | meilisearch.com, registered 2018-09-19 (8 years) | 11/15 | | Endpoint on the vendor's domain | is not on meilisearch.com | 0/15 | | Terms of service | read, states 4 of the 7 things a reader expects, and has 1 clause that costs points | 5.4/10 | | Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 | | Status page | status.meilisearch.com | 10/10 | | Changelog | published | 10/10 | | security.txt | valid | 10/10 | The terms of use and privacy policy name Meili, a simplified joint stock company at 52 boulevard de Sebastopol, 75003 Paris, registered in Paris under number 844 156 364. The repository licence names Meili SAS and the SLA names Meilisearch SAS. The terms of use cover the SaaS (Meilisearch Cloud) and the website in one document, in force since 18 March 2022. The privacy policy covers the website and the service, updated 17 March 2025. Cloud project hosts in the docs are on meilisearch.io (for example `ms-xxxxxxxxxxxx-xxxx.meilisearch.io`), a second domain. The console is at cloud.meilisearch.com. security.txt gives a support@ contact, expires 26 May 2027 and points its policy at trust.meilisearch.com, which we could not reach (TLS handshake failed from our network). RDAP for meilisearch.com gives a registration date of 2018-09-19. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service** (https://www.meilisearch.com/terms-of-use), read 2026-10-09, gives no date, states 4 of the 7 things a reader expects. - To know. Restricts benchmarking or competitive use (costs points). "use the Solution for purposes of comparative analysis or development of a competing product." - Not found in the text. Gives the date it was last updated. - Not found in the text. Names the governing law or courts. - States a limit on its liability. Capped at the fees paid in the 12 months before the claim. - Not found in the text. Says how changes to the terms are announced. - Also in the text (2026-10-08). Meilisearch may use the customer's name and logo on its website and in pitch materials without prior written consent. "Meilisearch may use the name of the Customer and its logo as a factual reference to the fact that the Customer is or was a customer, on its website and in pitch materials, without the prior written consent of Customer." - Also in the text (2026-10-08). A claim against Meilisearch must be made within thirty days of the event, after which no damages or compensation can be claimed. "Any claim against Meilisearch must be made within thirty (30) days following the occurrence of the event that is the subject of the claim. Failing this, you may not claim any damages or compensation for the alleged breach." - Also in the text (2026-10-08). Late payment carries interest at 5 per cent a month, alongside immediate suspension of access until all sums are paid. "interest for late payment calculated at the monthly rate of 5% calculated on the basis of a 365-day year." **Privacy policy** (https://www.meilisearch.com/privacy-policy), read 2026-10-09, dated 2025-03-17, states 7 of the 8 things a reader expects. - To know. Says it sells personal data or shares it for advertising. "Service Providers and other business partners: we may share your Personal Data with Service Providers to monitor and analyse the use of our Website and/or Solution, to show you advertisements, to help support and maintain our Website and/or Solution, to contact you, to advertise on third-party websites to you after yo…" - Gives the date it was last updated. Last updated 2025-03-17. - Says how long data is kept. Names a period of six months. - Not found in the text. Says whether personal data is sold or shared for advertising. - Gives a privacy contact. Gives an email address, hidden from our reader by the page. ## Live (updated 2026-10-10 00:50 UTC) - Vendor status page: unknown, no machine-readable status found - github `meilisearch/meilisearch` v1.54.3, released 2026-10-01 - npm `meilisearch` 0.62.0 - pypi `meilisearch` 0.43.0, released 2026-07-22 - Watching pricing - Watching privacy - Watching terms - Always current: https://www.anchorterminal.com/api/v1/live/meilisearch.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## Prices | Item | Price | Unit | Note | | --- | --- | --- | --- | | Build plan, 50,000 searches and 100,000 documents included | $30 | per month (plan) | Figure from the pricing page's estimator | | Extra searches on the Build plan | $0.40 | per 1,000 requests | Beyond the included 50,000 a month | | Cloud bandwidth, resource-based projects | $0.15 | per GB of traffic | May vary slightly by region | Across all listings: https://www.anchorterminal.com/prices/index.md ## Strengths - Keyword, vector and hybrid search in one request, with `semanticRatio`, filters, facets, sorting and federated multi-index search - OpenAPI 3.1 file for v1.54.3 with 143 operations, each described, checked daily in CI and attached to every release - API keys limited to named actions and indexes with an expiry, plus tenant tokens that embed per-user search filters - Status page shows one 16-minute outage of the San Francisco cluster in 90 days, on 24 July 2026 - Three minor releases between 3 August and 21 September 2026, and patch release v1.54.3 on 1 October 2026 ## Weaknesses - The `/mcp` route is an experimental feature that must be switched on, and its four tools carry no read-only annotations - No per-plan request rate limit is published for Cloud, although the monitoring docs list rate limiting as a cause of failed calls - The 99.9 per cent uptime SLA applies to Enterprise plans only - The terms of use date from 18 March 2022 and forbid using the service for comparative analysis, which matters before any probe is run - Cloud runs the Enterprise Edition, parts of which are under BUSL-1.1, and no audit log was found in the docs ## Before you call it (notes for agents) 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 ## Connect Install: ```bash npm install meilisearch ``` First request: ```bash curl \ -X POST 'MEILISEARCH_URL/indexes/movies/search' \ -H 'Authorization: Bearer API_KEY' \ -H 'Content-Type: application/json' \ --data-binary '{ "q": "american ninja" }' ``` Claude Code: ```bash claude mcp add --transport http meilisearch https://your-host/mcp \ --header "Authorization: Bearer YOUR_API_KEY" ``` Through letme (picks today, calling later): https://letme.dev/meilisearch (letme picks it for db.filters, the top-graded tool for the job, letme picks it for db.fulltext, the top-graded tool for the job, letme picks it for db.hybrid, the top-graded tool for the job, letme picks it for db.vector, the top-graded tool for the job). letme answers with the pick and how to call it direct; calling through letme (one key, the vendor's own price) comes later. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Pinecone API + MCP | BB | 76.2 | 38 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/pinecone.md | | Supabase API + MCP | BB | 75.6 | 45 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/supabase-mcp.md | | Qdrant API + MCP | BB | 75.3 | 51 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/qdrant.md | | Typesense API + MCP | BB | 70.7 | 146 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/typesense.md | | Vespa | BB | 70 | 165 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/vespa.md | | OpenSearch | B | 68 | 233 | db.vector, db.hybrid, db.fulltext, db.filters | no | https://www.anchorterminal.com/tools/opensearch.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - The built-in MCP server shipped in v1.54 on 21 September 2026 as an experimental feature at `POST /mcp`, with four read-only tools and Bearer key authentication (source: ) - The docs call the older `meilisearch-mcp` Python package deprecated and no longer actively maintained (source: ) - OpenAPI 3.1.0 file for v1.54.3 with 143 operations, attached to each release (source: ) - The status page shows 16 minutes of downtime on the San Francisco cluster on 24 July 2026 and no other incident in 90 days (source: ) - The terms of use, in force since 18 March 2022, forbid using the service for comparative analysis or to develop a competing product (source: ) - The Enterprise SLA commits to 99.9 per cent monthly uptime with service credits from 10 to 30 per cent (source: ) - #1 of 14 in Best vector search and retrieval databases for AI agents: https://www.anchorterminal.com/best/vector-search/index.md - All 85 retrieval comparisons: https://www.anchorterminal.com/compare/vector-search/index.md ## Compare - [Chroma API + MCP vs Meilisearch](https://www.anchorterminal.com/compare/chroma-vs-meilisearch.md): E 45.2 vs A 78.6 - [Elasticsearch vs Meilisearch](https://www.anchorterminal.com/compare/elasticsearch-vs-meilisearch.md): B 67.7 vs A 78.6 - [Epsilla Vector Database vs Meilisearch](https://www.anchorterminal.com/compare/epsilla-vs-meilisearch.md): F 35.7 vs A 78.6 - [LanceDB vs Meilisearch](https://www.anchorterminal.com/compare/lancedb-vs-meilisearch.md): B 65.4 vs A 78.6 - [Meilisearch vs Milvus and Zilliz Cloud API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-milvus-zilliz.md): A 78.6 vs C 57.3 - [Meilisearch vs OpenSearch](https://www.anchorterminal.com/compare/meilisearch-vs-opensearch.md): A 78.6 vs B 68 - [Meilisearch vs Pinecone API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-pinecone.md): A 78.6 vs BB 76.2 - [Meilisearch vs Qdrant API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-qdrant.md): A 78.6 vs BB 75.3 - [Meilisearch vs Typesense API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-typesense.md): A 78.6 vs BB 70.7 - [Meilisearch vs Upstash Vector API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-upstash-vector.md): A 78.6 vs B 62.4 - [Meilisearch vs Vespa](https://www.anchorterminal.com/compare/meilisearch-vs-vespa.md): A 78.6 vs BB 70 - [Meilisearch vs Weaviate API + MCP](https://www.anchorterminal.com/compare/meilisearch-vs-weaviate.md): A 78.6 vs B 67.9 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on meilisearch.com or one of its subdomains, or the README of github.com/meilisearch/meilisearch. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "meilisearch", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Meilisearch on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Meilisearch on Anchor Terminal](https://www.anchorterminal.com/badges/meilisearch.svg)](https://www.anchorterminal.com/tools/meilisearch) ``` Plain link: ```html Meilisearch on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Meilisearch is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/meilisearch-dark.png - Light: https://www.anchorterminal.com/assets/share/meilisearch-light.png