Skip to main content
hc
Submit
mcpSource-backedReview first Safety ✓ Privacy ✓

Meilisearch MCP Server for Claude

Connect Claude to Meilisearch — manage indexes, add and search documents, tune settings, and monitor tasks — with Meilisearch's official Model Context Protocol server.

by Meilisearch·added 2026-06-17·
Claude CodeCodexCursorClaude Desktop
HarnessClaude CodeCodexCursorClaude Desktop
Review first — review before installing

Open the source and read safety notes before installing.

Safety notes

  • Tools create and delete indexes and documents and rotate API keys — scope the key and confirm destructive actions.
  • Settings and index deletes change live search behavior; review before running them through Claude.

Privacy notes

  • Indexed documents and search results enter the MCP client context and the model's prompt.
  • MEILI_HTTP_ADDR and MEILI_MASTER_KEY are secrets — keep them in the client config or environment.

Prerequisites

  • A reachable Meilisearch instance URL (MEILI_HTTP_ADDR).
  • A Meilisearch master or API key (MEILI_MASTER_KEY) when your instance requires authentication.
  • uv (uvx) or pip to run meilisearch-mcp, or Docker (getmeili/meilisearch-mcp).
  • An MCP client such as Claude Code or Claude Desktop.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
10 minutes
Difficulty
intermediate
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"],
      "env": {
        "MEILI_HTTP_ADDR": "<your-meili-url>",
        "MEILI_MASTER_KEY": "<your-key>"
      }
    }
  }
}

About this resource

Overview

The Meilisearch MCP Server is Meilisearch's official Model Context Protocol server. It lets Claude manage a Meilisearch instance in natural language — creating and configuring indexes, adding and searching documents, tuning settings, managing API keys, and monitoring tasks. It runs over stdio via uvx/pip (or the getmeili/meilisearch-mcp Docker image) and is licensed under MIT.

Key capabilities

  • Index operations — create, list, update, and delete indexes.
  • Document management — add, update, and delete documents.
  • Search — run searches against an index.
  • Settings — configure ranking, filtering, and other index settings.
  • API keys & tasks — manage keys and monitor async task status, health, and system stats.

How it compares

Several search-engine MCP servers give Claude full-text and relevance search; they differ in hosting and focus:

MCP server Engine Hosting Notable
Meilisearch MCP Meilisearch Self-host or Meilisearch Cloud Fast, typo-tolerant search; simple setup
Elasticsearch MCP Elasticsearch Self-host or Elastic Cloud Query DSL + ES|QL analytics
Algolia MCP Algolia Hosted SaaS Managed relevance + analytics

Choose Meilisearch when you want a lightweight, typo-tolerant search engine you can self-host; the Elasticsearch and Algolia servers cover heavier analytics and fully managed search.

Installation

Claude Code

claude mcp add meilisearch -e MEILI_HTTP_ADDR=<your-meili-url> -e MEILI_MASTER_KEY=<your-key> -- \
  uvx -n meilisearch-mcp

Claude Desktop

{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"],
      "env": {
        "MEILI_HTTP_ADDR": "<your-meili-url>",
        "MEILI_MASTER_KEY": "<your-key>"
      }
    }
  }
}

Requirements

  • A reachable Meilisearch instance and (if required) a master/API key.
  • uv/pip or Docker to run the server.
  • An MCP client (Claude Code or Claude Desktop).

Security

  • Scope the Meilisearch key to least privilege; prefer a search-only key where Claude only queries.
  • Index/document deletes and settings changes affect live search — review before running.
  • Treat MEILI_HTTP_ADDR and MEILI_MASTER_KEY as secrets.

Source Verification Notes

Verified on 2026-06-17:

  • The official repository github.com/meilisearch/meilisearch-mcp (MIT) documents the meilisearch-mcp package (uvx/pip/Docker), stdio transport, the MEILI_HTTP_ADDR/MEILI_MASTER_KEY configuration, and the index, document, search, settings, API-key, and task tools above.
  • Meilisearch's documentation describes the underlying index and search features.
  • Claude Code's MCP documentation describes the connector setup pattern used here.
#meilisearch#search#full-text-search#indexing#database

Source citations

Add this badge to your README

Show that Meilisearch MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/meilisearch-mcp-server.svg)](https://heyclau.de/entry/mcp/meilisearch-mcp-server)

How it compares

Meilisearch MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

FieldMeilisearch MCP Server for Claude

Connect Claude to Meilisearch — manage indexes, add and search documents, tune settings, and monitor tasks — with Meilisearch's official Model Context Protocol server.

Open dossier 		Elasticsearch MCP Server for Claude

Connect Claude to your Elasticsearch cluster — search indices, inspect mappings, run ES|QL, and check shard health — with Elastic's official Model Context Protocol server.

Open dossier 		Weaviate MCP Server for Claude

Connect Claude to a Weaviate vector database — run hybrid search, inspect collection config, list tenants, and upsert objects — using Weaviate's built-in Model Context Protocol server.

Open dossier 		Code Index MCP Server

Local code indexing MCP server that lets AI assistants search repositories, build symbol indexes, inspect file summaries, monitor changes, and navigate multi-language codebases.

Open dossier
Trust
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedsource-backedsource-backedsource-backed
AuthorMeilisearchElasticWeaviatejohnhuang316
Added2026-06-172026-06-172026-06-172026-06-06
Platforms
Claude CodeCodexCursorClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Tools create and delete indexes and documents and rotate API keys — scope the key and confirm destructive actions. Settings and index deletes change live search behavior; review before running them through Claude.✓Search, ES|QL, and shard tools run live read queries against the configured cluster; a broad or expensive query can add load. Scope the Elasticsearch API key to least privilege (read-only on the indices Claude should see) before connecting.✓The MCP server runs inside your Weaviate instance and respects its existing RBAC; scope the API key to least privilege. The object-upsert tool writes data — restrict write access to the collections Claude should modify.✓Code Index MCP reads repository files, builds shallow and deep indexes, exposes file summaries, and can return source snippets through search and file resources. Point `--project-path` at one approved repository; avoid broad parent directories, home directories, generated dependency trees, or secret-heavy paths. Deep indexing and watcher refreshes can consume CPU, memory, disk IO, and temp storage on large codebases. The server can create and clear index/cache settings and temporary directories used for stored index data. Search results, file summaries, and symbol bodies can surface credentials, private code, customer data, internal URLs, or proprietary implementation details if they exist in the repository.
Privacy notes✓Indexed documents and search results enter the MCP client context and the model's prompt. MEILI_HTTP_ADDR and MEILI_MASTER_KEY are secrets — keep them in the client config or environment.✓Index data, field mappings, and query results enter the MCP client context and the model's prompt. ES_URL and ES_API_KEY are secrets — store them in the client config or environment, never in shared repositories.✓Query text, retrieved objects, and collection metadata enter the MCP client context and the model's prompt. The Weaviate endpoint URL and API key are secrets — keep them in the client config or environment, not in shared repositories.✓Tool calls may expose file paths, filenames, source code snippets, imports, classes, methods, functions, symbols, search matches, complexity summaries, and project settings. Index data and temp directories can persist derived repository structure or symbol metadata outside the source tree. File watcher status, exclude patterns, and settings can reveal local project layout and development conventions. If an MCP client forwards tool results to a model provider, repository contents and search snippets may leave the local machine. Exclude secrets, generated artifacts, vendored dependencies, build output, and private data before indexing.
Prerequisites
  • A reachable Meilisearch instance URL (MEILI_HTTP_ADDR).
  • A Meilisearch master or API key (MEILI_MASTER_KEY) when your instance requires authentication.
  • uv (uvx) or pip to run meilisearch-mcp, or Docker (getmeili/meilisearch-mcp).
  • An MCP client such as Claude Code or Claude Desktop.
  • Docker installed (the server is distributed as the docker.elastic.co/mcp/elasticsearch image).
  • An Elasticsearch cluster URL (ES_URL) you can reach.
  • An Elasticsearch API key (ES_API_KEY) or username/password (ES_USERNAME + ES_PASSWORD).
  • An MCP client such as Claude Code or Claude Desktop.
  • A Weaviate instance on v1.37.1 or later (self-hosted or Weaviate Cloud).
  • The MCP server enabled on that instance via MCP_SERVER_ENABLED=true.
  • A Weaviate API key with the RBAC permissions for the collections Claude should reach.
  • An MCP client such as Claude Code or Claude Desktop.
  • Python 3.10 or newer.
  • uv or another Python package runner that can install `code-index-mcp`.
  • An approved repository path that the MCP client is allowed to inspect.
  • Optional native search tools such as ripgrep, ugrep, ag, or grep for faster search backends.
Install
claude mcp add meilisearch -e MEILI_HTTP_ADDR=<your-meili-url> -e MEILI_MASTER_KEY=<your-key> -- uvx -n meilisearch-mcp
claude mcp add elasticsearch -- docker run -i --rm -e ES_URL=<your-cluster-url> -e ES_API_KEY=<your-api-key> docker.elastic.co/mcp/elasticsearch stdio
claude mcp add --transport http weaviate https://<your-weaviate-host>/v1/mcp
uvx code-index-mcp --project-path ABSOLUTE_PATH_TO_REPOSITORY
Config
{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"],
      "env": {
        "MEILI_HTTP_ADDR": "<your-meili-url>",
        "MEILI_MASTER_KEY": "<your-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "elasticsearch-mcp-server": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "ES_URL", "-e", "ES_API_KEY",
        "docker.elastic.co/mcp/elasticsearch", "stdio"
      ],
      "env": {
        "ES_URL": "<elasticsearch-cluster-url>",
        "ES_API_KEY": "<elasticsearch-api-key>"
      }
    }
  }
}
{
  "mcpServers": {
    "weaviate": {
      "url": "https://<your-weaviate-host>/v1/mcp",
      "type": "http"
    }
  }
}
Manual-only setup:
uvx code-index-mcp --project-path ABSOLUTE_PATH_TO_REPOSITORY
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.