Navigation
Meilisearch MCP Server: LLM Integration & AI-Driven Search - MCP Implementation

Meilisearch MCP Server: LLM Integration & AI-Driven Search

Meilisearch MCP Server bridges LLMs and Meilisearch via the Model Context Protocol, enabling seamless AI-driven search integration and future-ready contextual workflows.

Research And Data
4.4(60 reviews)
90 saves
42 comments

Users create an average of 43 projects per month with this tool

About Meilisearch MCP Server

What is Meilisearch MCP Server: LLM Integration & AI-Driven Search?

Meilisearch MCP Server is a middleware solution designed to integrate Large Language Models (LLMs) with Meilisearch's AI-driven search capabilities. It enables developers to extend Meilisearch's functionality by bridging it with external AI systems, providing advanced query interpretation, contextual search enhancements, and dynamic index management. This server acts as a communication layer, allowing seamless interaction between search operations and LLM-based processing pipelines.

Key Features of Meilisearch MCP Server: LLM Integration & AI-Driven Search

  • LLM Integration Framework: Supports real-time augmentation of search queries using external language models, improving relevance through contextual understanding.
  • Unified API Interface: Provides RESTful endpoints to manage Meilisearch tasks alongside LLM workflows, simplifying hybrid application development.
  • Task Orchestration: Includes robust task management for indexing, API key lifecycle control, and system health monitoring.
  • Advanced Search Capabilities: Offers filtering, sorting, and faceting with AI-enhanced ranking algorithms for personalized results.
  • Extensibility: Modular architecture allows customization for domain-specific use cases.

Meilisearch MCP Server Features

How to Use Meilisearch MCP Server: LLM Integration & AI-Driven Search

Getting Started

  1. Installation: Deploy via Docker or build from source, ensuring dependencies like Python and Redis are configured.
  2. Environment Setup: Configure .env files with Meilisearch endpoints, LLM API keys, and security parameters.
  3. API Initialization: Use Swagger UI to test core endpoints for search operations and task management.

Core Operations

Implement LLM-driven workflows by:

# Example: Query enrichment with an external model
POST /api/v1/ai_search
{
    "query": "Find Italian restaurants near me",
    "llm_model": "gpt-3.5-turbo",
    "context": "user_location: downtown"
}

Use Cases of Meilisearch MCP Server: LLM Integration & AI-Driven Search

  • Personalized E-commerce: Enhance product discovery by analyzing user intent through LLMs to recommend niche items.
  • Content Management: Automate document categorization and semantic search for knowledge bases or legal databases.
  • Dynamic Analytics: Combine search logs with LLM-generated insights for real-time customer behavior analysis.
  • Multi-lingual Support: Use AI translation capabilities to provide localized search experiences without manual index duplication.

Meilisearch MCP Server FAQ

FAQ from Meilisearch MCP Server: LLM Integration & AI-Driven Search

What LLM providers are supported?
Supports OpenAI, Anthropic, and custom models via API adapters. Add new providers by implementing the AbstractLLMClient interface.
How is query privacy maintained?
Data flows are encrypted end-to-end. Sensitive LLM interactions can be routed through private network segments using the PROXY_MODE configuration.
What is the cost model for AI operations?
LLM calls are metered separately. Implement usage tracking via the /api/v1/analytics/llm_usage endpoint to monitor costs.
Can I contribute to the project?
Yes. Submit pull requests through GitHub following the contributor guidelines.

Content

Meilisearch MCP Server

A Model Context Protocol (MCP) server for interacting with Meilisearch through LLM interfaces like Claude.

Meilisearch Server MCP server

Features

Installation

# Clone repository
git clone <repository_url>
cd meilisearch-mcp

# Create virtual environment and install
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
uv pip install -e .

Requirements

  • Python ≥ 3.9
  • Running Meilisearch instance
  • Node.js (for testing with MCP Inspector)

Usage

Environment Variables

MEILI_HTTP_ADDR=http://localhost:7700  # Default Meilisearch URL
MEILI_MASTER_KEY=your_master_key       # Optional: Default Meilisearch API key

Dynamic Connection Configuration

The server provides tools to view and update connection settings at runtime:

  • get-connection-settings: View current connection URL and API key status
  • update-connection-settings: Update URL and/or API key to connect to a different Meilisearch instance

Example usage through MCP:

// Get current settings
{
  "name": "get-connection-settings"
}

// Update connection settings
{
  "name": "update-connection-settings",
  "arguments": {
    "url": "http://new-host:7700",
    "api_key": "new-api-key"
  }
}

Search Functionality

The server provides a flexible search tool that can search across one or all indices:

  • search: Search through Meilisearch indices with optional parameters

Example usage through MCP:

// Search in a specific index
{
  "name": "search",
  "arguments": {
    "query": "search term",
    "indexUid": "movies",
    "limit": 10
  }
}

// Search across all indices
{
  "name": "search",
  "arguments": {
    "query": "search term",
    "limit": 5,
    "sort": ["releaseDate:desc"]
  }
}

Available search parameters:

  • query: The search query (required)
  • indexUid: Specific index to search in (optional)
  • limit: Maximum number of results per index (optional, default: 20)
  • offset: Number of results to skip (optional, default: 0)
  • filter: Filter expression (optional)
  • sort: Sorting rules (optional)

Running the Server

python -m src.meilisearch_mcp

Usage with Claude Desktop

To use this with Claude Desktop, add the following to your claude_desktop_config.json:

{
  "mcpServers": {
    "meilisearch": {
      "command": "uvx",
      "args": ["-n", "meilisearch-mcp"]
    }
  }
}

Testing with MCP Inspector

npx @modelcontextprotocol/inspector python -m src.meilisearch_mcp

Available Tools

Connection Management

  • get-connection-settings: View current Meilisearch connection URL and API key status
  • update-connection-settings: Update URL and/or API key to connect to a different instance

Index Management

  • create-index: Create a new index with optional primary key
  • list-indexes: List all available indexes
  • get-index-metrics: Get detailed metrics for a specific index

Document Operations

  • get-documents: Retrieve documents from an index with pagination
  • add-documents: Add or update documents in an index

Search

  • search: Flexible search across single or multiple indices with filtering and sorting options

Settings Management

  • get-settings: View current settings for an index
  • update-settings: Update index settings (ranking, faceting, etc.)

API Key Management

  • get-keys: List all API keys
  • create-key: Create new API key with specific permissions
  • delete-key: Delete an existing API key

Task Management

  • get-task: Get information about a specific task
  • get-tasks: List tasks with optional filters:
    • limit: Maximum number of tasks to return
    • from: Number of tasks to skip
    • reverse: Sort order of tasks
    • batchUids: Filter by batch UIDs
    • uids: Filter by task UIDs
    • canceledBy: Filter by cancellation source
    • types: Filter by task types
    • statuses: Filter by task statuses
    • indexUids: Filter by index UIDs
    • afterEnqueuedAt/beforeEnqueuedAt: Filter by enqueue time
    • afterStartedAt/beforeStartedAt: Filter by start time
    • afterFinishedAt/beforeFinishedAt: Filter by finish time
  • cancel-tasks: Cancel pending or enqueued tasks
  • delete-tasks: Delete completed tasks

System Monitoring

  • health-check: Basic health check
  • get-health-status: Comprehensive health status
  • get-version: Get Meilisearch version information
  • get-stats: Get database statistics
  • get-system-info: Get system-level information

Contributing

  1. Fork repository
  2. Create feature branch
  3. Commit changes
  4. Create pull request

License

MIT

Related MCP Servers & Clients