Meilisearch MCP Server for CrewAIGive CrewAI instant access to 44 tools to Add Documents, Cancel Tasks, Chat Completion, and more

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

GDPR Free for Subscribers

Connect your CrewAI agents to Meilisearch through Vinkius, pass the Edge URL in the `mcps` parameter and every Meilisearch tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

Open in ChatGPT Open in Claude Open in Perplexity

The Meilisearch MCP Server for CrewAI is a standout in the Loved By Devs category — giving your AI agent 44 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Meilisearch Specialist",
    goal="Help users interact with Meilisearch effectively",
    backstory=(
        "You are an expert at leveraging Meilisearch tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Meilisearch "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 44 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

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

About Meilisearch MCP Server

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

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.

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.

The Meilisearch MCP Server exposes 44 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 44 Meilisearch tools available for CrewAI

When CrewAI connects to Meilisearch through Vinkius, your AI agent gets direct access to every tool listed below — spanning search-engine, indexing, full-text-search, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add documents on Meilisearch

Add or replace documents in an index

cancel

Cancel tasks on Meilisearch

Cancel pending or processing tasks

chat

Chat completion on Meilisearch

Request a chat completion from a workspace

configure

Configure experimental features on Meilisearch

Enable or disable experimental features

create

Create dump on Meilisearch

Trigger the creation of a Meilisearch dump

create

Create index on Meilisearch

Create a new index

create

Create key on Meilisearch

Create a new API key

create

Create snapshot on Meilisearch

Trigger the creation of a Meilisearch snapshot

delete

Delete all documents on Meilisearch

Delete all documents in an index

delete

Delete document on Meilisearch

Delete a single document

delete

Delete documents batch on Meilisearch

Delete multiple documents by ID

delete

Delete documents by filter on Meilisearch

Delete documents matching a filter

delete

Delete dynamic search rule on Meilisearch

Delete a dynamic search rule

delete

Delete index on Meilisearch

Delete an index

delete

Delete key on Meilisearch

Delete an API key

delete

Delete tasks on Meilisearch

Delete finished tasks

get

Get batch on Meilisearch

Get details of a specific batch

get

Get document on Meilisearch

Get a specific document by ID

get

Get health on Meilisearch

Check the health of the Meilisearch instance

get

Get index on Meilisearch

Get metadata for a specific index

get

Get index stats on Meilisearch

Get stats of a specific index

get

Get key on Meilisearch

Get details of a specific API key

get

Get settings on Meilisearch

Get all settings of an index

get

Get stats on Meilisearch

Get stats of all indexes and database size

get

Get task on Meilisearch

Get details of a specific task

get

Get version on Meilisearch

Get the version of the Meilisearch instance

list

List batches on Meilisearch

List task batches

list

List chats on Meilisearch

List chat workspaces

list

List documents on Meilisearch

List documents in an index

list

List dynamic search rules on Meilisearch

List dynamic search rules for an index

list

List experimental features on Meilisearch

List the status of experimental features

list

List indexes on Meilisearch

List all Meilisearch indexes

list

List keys on Meilisearch

List API keys

list

List tasks on Meilisearch

List asynchronous tasks

multi

Multi search on Meilisearch

Perform multiple search queries in a single call

reset

Reset settings on Meilisearch

Reset all settings of an index to defaults

Search documents on Meilisearch

Search for documents in an index

set

Set dynamic search rule on Meilisearch

Create or update a dynamic search rule

similar

Swap indexes on Meilisearch

Swap multiple indexes atomically

update

Update documents on Meilisearch

Add or update documents (partial update)

update

Update index on Meilisearch

Update an index primary key

update

Update key on Meilisearch

Update an API key name or description

update

Update settings on Meilisearch

Update settings of an index

Connect Meilisearch to CrewAI via MCP

Follow these steps to wire Meilisearch into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 44 tools from Meilisearch

Why Use CrewAI with the Meilisearch MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Meilisearch through the Model Context Protocol.

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 `mcps` parameter 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 + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Meilisearch MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Meilisearch for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Meilisearch, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Meilisearch tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Meilisearch against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Meilisearch in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Meilisearch immediately.

"List all my Meilisearch indexes and their primary keys."

"Add these three product documents to the 'products' index: [JSON data]."

"Get the document with ID 'prod_99' from the 'products' index, but only show the 'name' and 'price' fields."

Troubleshooting Meilisearch MCP Server with CrewAI

Common issues when connecting Meilisearch to CrewAI through Vinkius, and how to resolve them.

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.

Meilisearch + CrewAI FAQ

Common questions about integrating Meilisearch MCP Server with CrewAI.

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.

Explore More MCP Servers

View all →

Meta Ads

10 tools

Equip your AI agent with direct access to Meta Ads — manage Facebook and Instagram campaigns, track ad performance, and optimize spend without opening Meta Ads Manager.