Can my AI read the strict structure of a custom model before creating a block?

Yes! We highly recommend asking your agent to use `get_model_schema` first. By retrieving the exact JSON fields (Strings, Lists, Booleans), the AI naturally learns the shape of your `Page` or `HeroContent` model and formats its `create_visual_block` mutation flawlessly avoiding validation errors.

How can I count how many blogs or pages are in my Builder space?

You can use the native `count_model_entities` tool. By querying a model like `blog-post`, the agent accesses the Builder backend with `limit=1` exclusively to extract the metadata counts without downloading heavyweight content arrays—highly efficient for broad analytics.

Can the agent wipe an accidentally created page completely?

Yes. If an error occurs or a staging draft needs removal, the agent can call `wipe_visual_block`. Supply the targeted entity ID, and the HTTP DELETE command is irreversibly broadcasted to the Builder environment. Always review IDs manually.

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

Name: Builder
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Builder through Vinkius, pass the Edge URL in the `mcps` parameter and every Builder 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="Builder Specialist",
    goal="Help users interact with Builder effectively",
    backstory=(
        "You are an expert at leveraging Builder 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 Builder "
        "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 Builder MCP Server

Connect your Builder.io space to any AI agent and take full programmatic control over your headless CMS architecture and visual pages through natural conversation.

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

Content Automation — Create, update, or wipe specific content entries across any data model dynamically
Schema Navigation — List your active Builder models and analyze exact field definitions and strict JSON bounds
Search & Retrieval — Use query strings to pull matched content documents or count entities effortlessly
Media Fetching — Inspect metadata and URLs of uploaded assets living on the Builder platform
Headless Maintenance — Delete deprecated components or page sections instantly using targeted endpoints

The Builder 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 Builder to CrewAI via MCP

Follow these steps to integrate the Builder 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 Builder

Why Use CrewAI with the Builder MCP Server

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

Builder + CrewAI Use Cases

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

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

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

Builder MCP Tools for CrewAI (10)

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

count_model_entities

Quickly count the number of live items stored within a specific model

create_visual_block

Create new content entries or visual blocks inside a Builder model

get_media_file

Retrieve details about an uploaded media asset within Builder.io

get_model_schema

Get the exact field structure and schema definitions for a single model

get_single_content

g. `query.data.title=Home`). Retrieve a specific content document by query matching from Builder.io

list_builder_models

List all defined data models and schemas in the Builder space

list_model_content

Useful for fetching dynamic content blocks or pages. Retrieve a list of content entries for a specific Builder.io model

search_active_models

Find Builder models matching a specific criteria or substring

update_visual_block

Update an existing Builder.io content block or document

wipe_visual_block

Permanently delete a specific content entry from Builder.io

Example Prompts for Builder in CrewAI

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

"List all active Builder models in my workspace."

"Fetch the schema for the 'custom-hero' model."

"Find a page with the title "Home" on the 'page' model."

Troubleshooting Builder MCP Server with CrewAI

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

Builder + CrewAI FAQ

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