Bring Search Engine
to CrewAI
Learn how to connect Meilisearch to CrewAI 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 SubscribersCompatible with every major AI agent and IDE
Gemini
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 CrewAI?
When paired with CrewAI, Meilisearch becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Meilisearch tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools
- —
CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the
mcpsparameter and agents auto-discover every available tool at runtime - —
Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls
- —
Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports
Meilisearch in CrewAI
Meilisearch and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Meilisearch to CrewAI 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 CrewAI
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 CrewAI 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 CrewAI
Every tool call from CrewAI 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 CrewAI discover and connect to MCP tools?
CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
Can different agents in the same crew use different MCP servers?
Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
What happens when an MCP tool call fails during a crew run?
CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
Can CrewAI agents call multiple MCP tools in parallel?
CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
Can I run CrewAI crews on a schedule (cron)?
Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.
MCP tools not discovered
Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
Agent not using tools
Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
Timeout errors
CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
Rate limiting or 429 errors
Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.
Explore More MCP Servers
View all →
Cloudflare Tunnel
17 toolsManage Cloudflare Tunnels directly from your AI agent — list, create, and configure secure Zero Trust connections to your private infrastructure.
Bazaarvoice
10 toolsAnalyze and manage user-generated content via Bazaarvoice — list products, reviews, and customer questions directly from any AI agent.
Shutterstock
9 toolsEquip your AI agent to radically sift through Shutterstock's immense media vault. Search high-quality images, videos, audio, and audit editorial licenses directly from your prompt.
WorldNewsAPI
4 toolsSearch world news — audit articles, top stories, and sources via AI.