Meilisearch Mcp

io.github.mrfentmenPublished by GitHub account mrfentmenv1.0.2Updated Oct 30, 2026

Search indexes, manage documents, check health and stats.

VerifiedSTDIODesktop onlyDatabasesWeb Search & Scraping

Overview

AI-generated overview

MCP server for MeiliSearch that lets an assistant search indexes, manage documents and indexes, and check instance health and stats.

What you can do
  • Search and read: run searches in an index, list documents, fetch a single document by ID.
  • Index management: list indexes, get index details, create and delete indexes.
  • Documents: add documents to an index and delete a document by ID.
  • Settings and keys: update index settings such as ranking rules and searchable attributes, list API keys.
  • Monitoring: check server health, get instance and per-index statistics, check async task status.
When to use it
Useful when you run a MeiliSearch instance and want an assistant to query its indexes or maintain their contents and settings in conversation, for example searching a products or blog-posts index or adding documents to it.
Requirements
Runs locally over stdio, typically via npx, so Node.js is needed. Requires a running MeiliSearch instance (v1.0+) reachable at MEILISEARCH_URL (default and, if the instance has authentication enabled, an API key in MEILISEARCH_API_KEY.
Before you install
The API key in MEILISEARCH_API_KEY is a secret and may carry write or admin rights. Several tools change data: create_index, delete_index, add_documents, delete_document and update_settings can add, alter or permanently remove indexes, documents and settings. Point it at a non-production instance or use a restricted key when experimenting.

Installation

In SourceWeft

  1. Open Meilisearch Mcp in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MeiliSearch MCP

An MCP server for MeiliSearch, the fast and typo-tolerant search engine.

What it does

Search through MeiliSearch indexes, manage documents, create/delete indexes, check health and stats, and manage API keys. Perfect for AI agents that need to search through your data.

Tools

  • check_health - Check if the MeiliSearch server is running
  • list_indexes - List all indexes
  • get_index - Get index details
  • create_index - Create a new index
  • delete_index - Delete an index
  • search_index - Search documents in an index
  • get_documents - List documents in an index
  • get_document - Get a single document by ID
  • add_documents - Add documents to an index
  • delete_document - Delete a document by ID
  • get_stats - Get instance statistics
  • get_index_stats - Get index-specific statistics
  • get_task - Check async task status
  • list_keys - List API keys
  • update_settings - Update index settings (ranking rules, searchable attributes, filters, etc.)

Install

bash
npx meilisearch-mcp

Environment Variables

  • MEILISEARCH_URL - MeiliSearch server URL (default: http://localhost:7575)
  • MEILISEARCH_API_KEY - API key for authentication (if your instance requires it)

Claude Desktop setup

Add this to your claude_desktop_config.json:

json
{  "mcpServers": {    "meilisearch": {      "command": "npx",      "args": ["-y", "meilisearch-mcp"],      "env": {        "MEILISEARCH_URL": "http://localhost:7575",        "MEILISEARCH_API_KEY": "your-api-key"      }    }  }}

Example usage

Ask Claude:

  • "Search my products index for 'wireless headphones'"
  • "Show me all indexes in my MeiliSearch instance"
  • "Add these documents to my blog-posts index"
  • "How many documents are in my main index?"
  • "Update my index settings to use title as searchable attribute"

Requirements

  • A running MeiliSearch instance (v1.0+)
  • Optional: API key if your instance has authentication enabled

License

MIT

Source: README.md at commit 065cc4b

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

2
  1. v1.0.2LatestSep 22, 2026
  2. v1.0.1Sep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.