How do I find my Cluster Endpoint?

You can find your Cluster Endpoint in the Zilliz Cloud Console under the 'Cluster Details' page. It typically looks like `https://in01-xxxxxxxxxxxx.vectordb.zillizcloud.com`.

Why do I need to 'load' a collection before searching?

Zilliz requires collections to be loaded into memory to perform high-performance similarity searches. Use the `load_collection` tool to make your data available for search.

Can I filter my vector search using metadata?

Yes, Zilliz supports hybrid search. You can use the `query_entities` tool for metadata-only filtering or include filtering expressions in your `search_vectors` JSON configuration.

Zilliz Cloud MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Zilliz Cloud
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Zilliz Cloud Specialist",
    goal="Help users interact with Zilliz Cloud effectively",
    backstory=(
        "You are an expert at leveraging Zilliz Cloud 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 Zilliz Cloud "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Zilliz Cloud MCP Server

Connect your Zilliz Cloud cluster to any AI agent to automate your vector database operations. This MCP server enables your agent to manage collections, insert data, and perform high-performance similarity searches directly from natural language.

When paired with CrewAI, Zilliz Cloud becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zilliz Cloud 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

Collection Management — List, describe, create, and drop vector collections in your cluster
Memory Control — Load and release collections to optimize cluster resource usage and search availability
Vector Search — Execute complex vector similarity searches (ANN) using customizable metrics and parameters
Metadata Querying — Query entities using boolean expressions and metadata filters to find specific records
Data Maintenance — Insert new vector/scalar data and delete entities from your collections

The Zilliz Cloud MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Zilliz Cloud to CrewAI via MCP

Follow these steps to integrate the Zilliz Cloud MCP Server with CrewAI.

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 10 tools from Zilliz Cloud

Why Use CrewAI with the Zilliz Cloud MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Zilliz Cloud 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

Zilliz Cloud + CrewAI Use Cases

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

Automated multi-step research: a reconnaissance agent queries Zilliz Cloud 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 Zilliz Cloud, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Zilliz Cloud 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 Zilliz Cloud against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Zilliz Cloud MCP Tools for CrewAI (10)

These 10 tools become available when you connect Zilliz Cloud to CrewAI via MCP:

create_collection

Requires a JSON body. Create a new vector collection

delete_entities

Delete entities from a collection

describe_collection

Get details for a specific collection

drop_collection

Drop a collection

insert_entities

Insert data into a collection

list_collections

List all collections in the Zilliz cluster

load_collection

Load a collection into memory

query_entities

Query entities using metadata filtering

release_collection

Release a collection from memory

search_vectors

Requires a JSON search configuration. Perform a vector similarity search

Example Prompts for Zilliz Cloud in CrewAI

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

"List all vector collections in my Zilliz cluster."

"Show the schema and status for collection 'text_docs'."

"Drop the collection named 'old_data_backup'."

Troubleshooting Zilliz Cloud MCP Server with CrewAI

Common issues when connecting Zilliz Cloud to CrewAI through the 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.

Zilliz Cloud + CrewAI FAQ

Common questions about integrating Zilliz Cloud 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.