Meilisearch MCP. Automate Indexing and Search Operations
Meilisearch MCP lets you automate your entire search engine lifecycle. Connect it to any AI client and manage everything from creating indexes and updating documents in bulk, to running complex searches across thousands of records. You control the data flow without ever touching a dashboard.
Give Claude and any AI agent real-world access
You can list all indexes and create new ones, or swap multiple indexes atomically for zero-downtime deployments.
Add, update, or replace large batches of documents, or get the details for a single document by its ID.
Remove data using granular methods, such as deleting all records in an index, removing specific matching groups, or cleaning up old tasks.
Run powerful searches against your content, including multi-query operations and finding documents similar to a starting ID.
Ask an AI about this
Waiting for input…
What AI agents can do with Meilisearch MCP: 44 Tools for Indexing and Search
Use these tools to handle every part of the Meilisearch workflow. From simple document retrieval to complex index swaps, you can manage your search data entirely through your AI client.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Meilisearch MCPAdd Documents
Adds or replaces one or more documents within a specified index.
Cancel Tasks
Stops any pending background tasks that haven't finished processing.
Chat Completion
Requests conversational text generation from a specific workspace.
Configure Experimental Features
Turns experimental search features on or off for better control.
Create Dump
Starts the process of creating a full data dump of the index content.
Create Index
Builds and initializes an entirely new search index from scratch.
Create Key
Generates a brand new API key for secure access to the system.
Create Snapshot
Triggers the creation of an immediate, point-in-time backup of the index data.
Delete All Documents
Wipes out every single document currently stored in a given index.
Delete Document
Removes one specific document when you know its unique ID.
Delete Documents Batch
Deletes multiple documents simultaneously by providing a list of IDs.
Delete Documents By Filter
Cleans up data by removing all documents that match complex search criteria.
Delete Dynamic Search Rule
Removes a specific, customized rule used to enhance search functionality.
Delete Index
Completely removes an entire index and all its associated data.
Delete Key
Deletes a specific API key, revoking its access permissions.
Delete Tasks
Cleans up records of tasks that have already completed processing.
Get Batch
Retrieves detailed status information for a specific data batch job.
Get Document
Fetches the full details of one document using its unique ID.
Get Health
Checks and reports the overall operational status of the entire Meilisearch instance.
Get Index Stats
Retrieves detailed performance statistics for one specific index.
Get Index
Gets all the metadata and configuration details for a specified index.
Get Key
Retrieves the full details and status of an existing API key.
Get Settings
Fetches all current configuration settings used by a particular index.
Get Stats
Returns global statistics, including data size and metrics for every index.
Get Task
Retrieves the current status and details of a specific background processing task.
Get Version
Checks which version of the Meilisearch instance is currently running.
List Batches
Retrieves a list of all data processing batches that have run or are pending.
List Chats
Lists the names and IDs of existing chat workspaces configured in the system.
List Documents
Fetches a list of document metadata from an index without retrieving full content.
List Dynamic Search Rules
Lists all custom rules that modify how search queries are processed for an index.
List Experimental Features
Shows the status (enabled or disabled) of various experimental features available in Meilisearch.
List Indexes
Provides a list of every index currently managed by the system.
List Keys
Displays all API keys associated with this Meilisearch instance.
List Tasks
Gets a comprehensive list of background tasks that are currently running or waiting...
Multi Search
Executes several distinct search queries in one single, efficient API call.
Reset Settings
Resets all configuration settings for a given index back to their factory defaults.
Search Documents
Performs a standard text search across the content of documents within an index.
Set Dynamic Search Rule
Creates or updates a custom rule to modify how certain data fields are searched.
Similar Documents
Finds other documents whose content is highly related to the text of a specified...
Swap Indexes
Swaps multiple indexes at once, ensuring the switch happens instantly and without...
Update Documents
Makes partial updates to documents, changing only specific fields instead of...
Update Index
Changes the primary key used by an index, allowing you to migrate data identifiers safely.
Update Key
Modifies the name or description of an existing API key for better tracking.
Update Settings
Changes specific operational settings, such as pagination limits or indexing rules...
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Meilisearch, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Meilisearch. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS CLOUD
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Managing a Live Search Engine Used to Be a Pain
If you're running a content site, the old process is a mess of tabs and clicking. You update data in one system, then have to log into your search dashboard, manually checking indexes and running separate commands just to see if everything synced correctly. It takes half an hour just to verify a single deployment.
With this MCP, you skip the UI entirely. Your agent handles the complexity. Instead of clicking through settings menus, you ask for it: 'Check the health and statistics.' You get immediate, actionable status reports that let you move forward without friction.
Meilisearch MCP Gives You Full Control Over Indexing
You don't have to rely on automated cron jobs or complex pipelines just for simple changes. If you need to change how documents are identified, `update_index` handles it. If the whole search structure needs a refresh, `create_snapshot` captures that moment perfectly.
The result is full operational command via chat. You manage the entire lifecycle—from creation (`create_index`) to daily operations and eventual deletion (`delete_index`)—all through simple prompts.
What Meilisearch MCP does for your AI
Need to keep your search database fresh? This MCP connects your Meilisearch instance directly to your agent. Instead of logging into a dedicated dashboard or writing boilerplate scripts just to check if your data is indexed, you tell your AI client what needs doing. You can list all existing indexes and manage their settings, running tasks like atomic swaps for zero-downtime updates.
Want to clean up old data? Your agent handles complex deletion operations, whether it’s removing a single document by ID or filtering out entire batches of records based on specific criteria. The ability to pull metadata details helps you monitor the engine's health in real time. It’s powerful management for developers and content teams alike, letting you perform heavy data engineering tasks right where your AI client is working, making it one of the most critical tools available in the Vinkius catalog.
019e38c0-872f-719f-bbd2-3df4b2c03fcd How to set up Meilisearch MCP
The bottom line is you get to manage mission-critical search infrastructure using natural language prompts through your preferred AI client.
Subscribe to this MCP and provide your Meilisearch Instance URL along with an API Key.
Your AI client authenticates and connects the credentials, making the search engine available as a toolset.
You prompt your agent (e.g., 'Find all documents in the 'products' index that were modified last week') and it executes the complex data retrieval.
Who uses Meilisearch MCP
This MCP is essential for developers and data engineers who spend too much time in web dashboards just to run basic indexing checks. If you're constantly dealing with structured, large-scale content or complex search requirements, this tool saves hours of manual API calls.
Automating index maintenance, triggering snapshots, and running full document synchronization tasks across multiple indexes.
Integrating search functionality directly into code generation or testing workflows without needing to switch contexts to a separate admin tool.
Quickly verifying if specific content has been correctly indexed and checking the metadata status of an entire collection.
Benefits of connecting Meilisearch MCP
Avoid manual UI clicks. Instead of navigating dashboards to create a new index, your agent runs the create_index tool directly when prompted.
Eliminate downtime risks. Use the swap_indexes function to transition between versions instantly, ensuring zero disruption to live users.
Handle massive data cleanup. Don't manually delete records; use delete_documents_by_filter to remove large groups of outdated content based on complex criteria.
Speed up development cycles. Need to test search results? Use the multi_search tool to run several queries in one call, saving API overhead.
Maintain data integrity. You can use get_index_stats and get_settings to verify that your index is configured exactly right before deploying changes.
Meilisearch MCP use cases
Refreshing a Product Catalog
A content manager needs to update the product search results after adding 500 new items. They ask their agent, 'Add these 500 JSON documents to the 'products' index.' The agent uses add_documents, handling the entire batch upload and queueing process instantly.
Debugging Search Failures
A developer finds that search results are missing fields. They prompt their agent, asking it to 'Get the metadata for the 'movies' index.' The agent uses get_index and reports back exactly what settings need changing.
Migrating Search Versions
A data engineer finishes a major content update. Instead of manually reconfiguring the live system, they prompt their agent to 'Swap indexes from v2_staging to v2_live.' The agent executes swap_indexes atomically.
Finding Related Content
A user searches for a specific article. To guide them better, the agent uses similar_documents, finding and listing three related articles that are contextually close to the original search term.
Meilisearch MCP tradeoffs
What to watch out for, and the recommended way to handle each one.
Deleting data piecemeal
Trying to delete old records by running 10 separate commands for 10 different date ranges. This is slow, error-prone, and misses complex filter logic.
Use delete_documents_by_filter. You pass one single instruction—like 'Remove all documents where status=archived AND created_at < last_year'—and it handles the bulk cleanup.
Ignoring index health
Assuming that just because a document was added, it is searchable. The system might be running on outdated settings or an old version.
Always run get_health first. If the health check passes, then you proceed with data operations like add_documents. It confirms everything is ready.
Overwriting all content
Running a basic 'delete all' command without checking if new documents were added since the last run.
Check first with list_indexes and get_index. If you confirm no one is using the index, then consider running delete_all_documents. Otherwise, stick to targeted updates.
When to use Meilisearch MCP
Use this MCP if your core problem involves managing complex, structured search data that needs constant indexing and manipulation. This tool shines when you need to run bulk operations—like using add_documents or swap_indexes—without writing custom CLI scripts. Don't use it if all you need is a simple database read (e.g., 'What is the user's name?'). For those cases, a general data retrieval tool is better. If your task involves advanced API management (like managing multiple credentials or keys), then this MCP provides the necessary granular control through tools like list_keys and get_key. It’s built for operations engineers who treat their search engine as mission-critical infrastructure.
Frequently asked questions about Meilisearch MCP
How do I check if my Meilisearch index is working correctly using Meilisearch MCP? +
Run the get_health tool. This immediately checks the overall operational status of your entire search engine instance, telling you if everything is green or if something needs attention.
Can I update my documents without losing the old data? Meilisearch MCP? +
Yes, use update_documents. This tool performs partial updates, meaning it only changes specific fields on existing records instead of replacing the whole document.
What's the difference between deleting documents and listing them with Meilisearch MCP? +
Listing (list_documents) just shows you what's there. Deleting involves actually removing data, which can be done individually with delete_document or by filtering.
How do I handle a major search version update safely? Meilisearch MCP? +
The safest way is to use swap_indexes. This tool allows you to transition between two versions of your index atomically, ensuring zero downtime for users.
Does Meilisearch MCP support running multiple searches at once? +
Yes. Use the multi_search tool to combine several different search queries into a single call, which is much faster and more efficient than calling each one separately.