How do I find my Instance ZUID?

You can list all your accessible instances using the `list_zesty_instances` tool, or find it in your Zesty.io URL (it starts with `8-`).

Can I see all content items for a particular model?

Yes, use the `list_content_items` tool with the unique ZUID of the model (starts with `6-`) to retrieve all associated entries.

Is it possible to update content via the agent?

Absolutely. Use the `update_content_item` tool by providing the Model ZUID, the Item ZUID, and a JSON object containing the fields you wish to modify.

Zesty.io MCP Server for CrewAI 8 tools — connect in under 2 minutes

Name: Zesty.io
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Zesty.io through the Vinkius — pass the Edge URL in the `mcps` parameter and every Zesty.io 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="Zesty.io Specialist",
    goal="Help users interact with Zesty.io effectively",
    backstory=(
        "You are an expert at leveraging Zesty.io 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 Zesty.io "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 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 Zesty.io MCP Server

Connect your Zesty.io account to any AI agent to streamline your headless CMS operations. This MCP server enables your agent to interact with instances, content models, and data entries (items) directly from natural language.

When paired with CrewAI, Zesty.io becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Zesty.io tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Instance Oversight — List all Zesty.io instances associated with your account and retrieve their metadata
Schema Management — List content models to understand your data structures and identify Model ZUIDs
Content Operations — List, retrieve, create, and update content items within specific models
Technical Auditing — Access instance settings and technical metadata for any of your properties
Workflow Automation — Delete content items and maintain your CMS hierarchy via natural language commands

The Zesty.io MCP Server exposes 8 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 Zesty.io to CrewAI via MCP

Follow these steps to integrate the Zesty.io 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 8 tools from Zesty.io

Why Use CrewAI with the Zesty.io MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Zesty.io 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 the 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

Zesty.io + CrewAI Use Cases

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

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

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

Zesty.io MCP Tools for CrewAI (8)

These 8 tools become available when you connect Zesty.io to CrewAI via MCP:

create_content_item

Requires a JSON object with field values. Create a new content item

delete_content_item

Delete a content item

get_content_item

Get details for a specific content item

get_instance_settings

Get configuration settings for the instance

list_content_items

List content items for a specific model

list_content_models

Use this to identify Model ZUIDs. List all content models for the current instance

list_zesty_instances

List all Zesty.io instances associated with the account

update_content_item

Update an existing content item

Example Prompts for Zesty.io in CrewAI

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

"List all Zesty instances I have access to."

"Show me the content items for the 'Press Releases' model (ZUID: '6-ghi-987')."

"Update the title of content item '7-jkl-654' in model '6-ghi-987' to '2024 Product Roadmap'."

Troubleshooting Zesty.io MCP Server with CrewAI

Common issues when connecting Zesty.io 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

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Zesty.io + CrewAI FAQ

Common questions about integrating Zesty.io 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.