Compatible with every major AI agent and IDE
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 or replace documents in an index
Cancel pending or processing tasks
Request a chat completion from a workspace
Enable or disable experimental features
Trigger the creation of a Meilisearch dump
Create a new index
Create a new API key
Trigger the creation of a Meilisearch snapshot
Delete all documents in an index
Delete a single document
Delete multiple documents by ID
Delete documents matching a filter
Delete a dynamic search rule
Delete an index
Delete an API key
Delete finished tasks
Get details of a specific batch
Get a specific document by ID
Check the health of the Meilisearch instance
Get metadata for a specific index
Get stats of a specific index
Get details of a specific API key
Get all settings of an index
Get stats of all indexes and database size
Get details of a specific task
Get the version of the Meilisearch instance
List task batches
List chat workspaces
List documents in an index
List dynamic search rules for an index
List the status of experimental features
List all Meilisearch indexes
List API keys
List asynchronous tasks
Perform multiple search queries in a single call
Reset all settings of an index to defaults
Search for documents in an index
Create or update a dynamic search rule
Find documents similar to a given document ID
Swap multiple indexes atomically
Add or update documents (partial update)
Update an index primary key
Update an API key name or description
Update settings of an index
Why Mastra AI?
Mastra's agent abstraction provides a clean separation between LLM logic and Meilisearch tool infrastructure. Connect 44 tools through Vinkius and use Mastra's built-in workflow engine to chain tool calls with conditional logic, retries, and parallel execution. deployable to any Node.js host in one command.
- —
Mastra's agent abstraction provides a clean separation between LLM logic and tool infrastructure. add Meilisearch without touching business code
- —
Built-in workflow engine chains MCP tool calls with conditional logic, retries, and parallel execution for complex automation
- —
TypeScript-native: full type inference for every Meilisearch tool response with IDE autocomplete and compile-time checks
- —
One-command deployment to any Node.js host. Vercel, Railway, Fly.io, or your own infrastructure
Meilisearch in Mastra AI
Meilisearch and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Meilisearch to Mastra AI 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.
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 |
Why teams choose Vinkius for Meilisearch in Mastra AI
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 Mastra AI 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.

* 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
How Vinkius secures
Meilisearch for Mastra AI
Every tool call from Mastra AI to the Meilisearch MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
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 Mastra AI connect to MCP servers?
Create an MCPClient with the server URL and pass it to your agent. Mastra discovers all tools and makes them available with full TypeScript types.
Can Mastra agents use tools from multiple servers?
Yes. Pass multiple MCP clients to the agent constructor. Mastra merges all tool schemas and the agent can call any tool from any server.
Does Mastra support workflow orchestration?
Yes. Mastra has a built-in workflow engine that lets you chain MCP tool calls with branching logic, error handling, and parallel execution.
createMCPClient not exported
Install: npm install @mastra/mcp
Explore More MCP Servers
View all →
RCSB PDB
2 toolsExplore 220K+ 3D molecular structures — search proteins, DNA, and RNA by name, experimental method, resolution, and bound ligands from the Protein Data Bank.

MotionTools
10 toolsManage logistics and delivery operations via MotionTools — track bookings, drivers, and vehicles directly from your AI agent.

KnoCommerce
10 toolsAnalyze post-purchase surveys — list responses, audit customer feedback, and track attribution channels.

Fixably
12 toolsManage repair orders, track inventory, and handle customer data via AI agents with Fixably.
