How does the AI validate JSON payloads before creating content?

Instruct the agent to call `list_components` first. It returns the exact field names and types each component expects, so the AI builds a compliant JSON payload before calling `create_content_story`.

Can the agent accidentally delete entire spaces?

No. `delete_content_story` targets a single story by ID — it cannot perform recursive or bulk deletions. For extra safety, use a token scoped with limited write permissions.

What content types can I manage through this integration?

Stories (pages, articles, blog posts), media assets (images, videos, documents), component definitions, and space-level settings. Use `list_stories`, `list_assets`, and `list_components` to explore your content.

Storyblok MCP Server for CrewAI 9 tools — connect in under 2 minutes

Name: Storyblok
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 9 Tools Framework

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

Integrate the powerful headless CMS capabilities of Storyblok directly into your conversational AI. Empower your content teams and developers to organically draft narratives, parse complex asset repositories, and orchestrate page component definitions without relying entirely on the visual editor. Bind your AI local context directly to your Storyblok environment securely, enabling programmatic schema generation and continuous iteration utilizing a streamlined conversational interface designed to accelerate creative velocity.

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

Space & Content Discovery — Instantly list active enterprise environments utilizing list_spaces and fetch broad overarching overviews referencing stories via list_stories.
Content Construction — Swiftly produce or update textual assets creating schemas directly from prompts invoking create_content_story and update_content_story systematically.
Asset & Structure Exploration — Analyze media repositories via list_assets and precisely inspect available schema blueprints calling list_components to standardize development.
Risk Management — Exercise safe administrative control over local projects, evaluating internal authorized operators implementing modifications using list_space_users.

The Storyblok MCP Server exposes 9 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 Storyblok to CrewAI via MCP

Follow these steps to integrate the Storyblok 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 9 tools from Storyblok

Why Use CrewAI with the Storyblok MCP Server

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

Storyblok + CrewAI Use Cases

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

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

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

Storyblok MCP Tools for CrewAI (9)

These 9 tools become available when you connect Storyblok to CrewAI via MCP:

create_content_story

Provide a name, slug, and content JSON. Creates a new story in a Storyblok space

delete_content_story

This action is irreversible. Permanently deletes a Storyblok story

get_story_details

Retrieves details for a specific content story

list_assets

Lists media assets in a Storyblok space

list_components

Lists available content components

list_space_users

Lists all users with access to a specific space

list_spaces

Lists all accessible Storyblok spaces

list_stories

Requires a space ID. Lists content stories within a specific space

update_content_story

Requires space and story IDs. Updates fields of an existing Storyblok story

Example Prompts for Storyblok in CrewAI

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

"List the recent articles from my Storyblok space and detail their structural components."

"List the structure blueprints by calling list_components and then formulate a new JSON to create a blog story."

"List all multimedia assets in my Storyblok space and display their URLs."

Troubleshooting Storyblok MCP Server with CrewAI

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

Storyblok + CrewAI FAQ

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