Claude DesktopIDE

Meilisearch MCP Server

Bring Search Engine
to Claude Desktop

Name: Meilisearch MCP Server
Price: 29 USD
Availability: InStock
Rating: 4.9 (1 reviews)
Author: Vinkius

Learn how to connect Meilisearch to Claude Desktop and start using 44 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

GDPR Free for Subscribers

Add DocumentsCancel TasksChat CompletionConfigure Experimental FeaturesCreate DumpCreate IndexCreate KeyCreate SnapshotDelete All DocumentsDelete DocumentDelete Documents BatchDelete Documents By FilterDelete Dynamic Search RuleDelete IndexDelete KeyDelete TasksGet BatchGet DocumentGet HealthGet IndexGet Index StatsGet KeyGet SettingsGet StatsGet TaskGet VersionList BatchesList ChatsList DocumentsList Dynamic Search RulesList Experimental FeaturesList IndexesList KeysList TasksMulti SearchReset SettingsSearch DocumentsSet Dynamic Search RuleSimilar DocumentsSwap IndexesUpdate DocumentsUpdate IndexUpdate KeyUpdate Settings

Unlock for AI Agents

Ask AI about this MCP Server ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

What is the Meilisearch MCP Server?

Connect your Meilisearch instance to any AI agent to automate your search engine management and data indexing workflows.

What you can do

Index Management — Create, list, update, and delete indexes. Perform atomic swaps between indexes for zero-downtime deployments.
Document Operations — Add, update, or replace documents in bulk. Retrieve specific documents by ID or list them with advanced filtering and sorting.
Granular Deletion — Remove documents individually, in batches, or by applying complex filter expressions to clean up your data.
Metadata Inspection — Fetch detailed metadata for your indexes and documents to monitor your search engine's state.

How it works

Subscribe to this server
Enter your Meilisearch Instance URL and API Key
Start managing your search data from Claude, Cursor, or any MCP-compatible client

Who is this for?

Developers — Index new data or debug search results directly from the code editor.
Data Engineers — Automate index maintenance and document synchronization tasks.
Content Managers — Quickly verify if specific content is correctly indexed without using a dedicated dashboard.

Built-in capabilities (44)

add_documents

Add or replace documents in an index

cancel_tasks

Cancel pending or processing tasks

chat_completion

Request a chat completion from a workspace

configure_experimental_features

Enable or disable experimental features

create_dump

Trigger the creation of a Meilisearch dump

create_index

Create a new index

create_key

Create a new API key

create_snapshot

Trigger the creation of a Meilisearch snapshot

delete_all_documents

Delete all documents in an index

delete_document

Delete a single document

delete_documents_batch

Delete multiple documents by ID

delete_documents_by_filter

Delete documents matching a filter

delete_dynamic_search_rule

Delete a dynamic search rule

delete_index

Delete an index

delete_key

Delete an API key

delete_tasks

Delete finished tasks

get_batch

Get details of a specific batch

get_document

Get a specific document by ID

get_health

Check the health of the Meilisearch instance

get_index

Get metadata for a specific index

get_index_stats

Get stats of a specific index

get_key

Get details of a specific API key

get_settings

Get all settings of an index

get_stats

Get stats of all indexes and database size

get_task

Get details of a specific task

get_version

Get the version of the Meilisearch instance

list_batches

List task batches

list_chats

List chat workspaces

list_documents

List documents in an index

list_dynamic_search_rules

List dynamic search rules for an index

list_experimental_features

List the status of experimental features

list_indexes

List all Meilisearch indexes

list_keys

List API keys

list_tasks

List asynchronous tasks

multi_search

Perform multiple search queries in a single call

reset_settings

Reset all settings of an index to defaults

search_documents

Search for documents in an index

set_dynamic_search_rule

Create or update a dynamic search rule

similar_documents

Find documents similar to a given document ID

swap_indexes

Swap multiple indexes atomically

update_documents

Add or update documents (partial update)

update_index

Update an index primary key

update_key

Update an API key name or description

update_settings

Update settings of an index

Why Claude Desktop?

Claude Desktop is the definitive way to connect Meilisearch to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 44 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

—
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
—
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
—
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
—
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

See it in action

Meilisearch in Claude Desktop

AI Agent→Vinkius

High Security·Kill Switch·Plug and Play

Why Vinkius

Meilisearch and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Meilisearch to Claude Desktop through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready

<40msCold start

60%Token savings

	Raw MCP	Vinkius
Server catalog	Find and host yourself	4,000+ managed
Infrastructure	Self-hosted	Sandboxed V8 isolates
Credential handling	Plaintext in config	Vault + runtime injection
Data loss prevention	None	Configurable DLP policies
Kill switch	None	Global instant shutdown
Financial circuit breakers	None	Per-server limits + alerts
Audit trail	None	Ed25519 signed logs
SIEM log streaming	None	Splunk, Datadog, Webhook
Honeytokens	None	Canary alerts on leak
Custom domains	Not applicable	DNS challenge verified
GDPR compliance	Manual effort	Automated purge + export

Unlock for AI Agents View step-by-step setup guide for Claude Desktop →

Enterprise Security

Why teams choose Vinkius for Meilisearch in Claude Desktop

The Meilisearch MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 44 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in Claude Desktop only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Unlock for AI Agents View full Meilisearch details →

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures
Meilisearch for Claude Desktop

Every tool call from Claude Desktop to the Meilisearch MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start

Ed25519Signed audit chain

60%Token savings

FAQ

Frequently asked questions

Can I delete documents based on a specific condition or category?

Yes! You can use the delete_documents_by_filter tool. Just provide the index UID and a filter expression (e.g., 'category = electronics') to remove all matching documents at once.

How do I perform a zero-downtime index update?

You can use the swap_indexes tool. This allows you to swap the names of two or more indexes atomically, ensuring your search remains active while you switch to a newly populated index.

Is it possible to retrieve only specific fields from a document?

Absolutely. When using get_document or list_documents, you can provide a comma-separated list of fields to return, reducing the payload size and focusing on the data you need.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).