Can my agent check the ML ranking for a specific product search?

Yes. Use the 'search_products' tool. The agent will retrieve results ranked by Constructor's ML engine, allowing you to audit how products are surfaced based on specific keywords and intent signals.

How do I retrieve personalized recommendations via the agent?

Provide the 'pod_id' to your agent and use the 'get_recommendations' tool. The agent will query the collaborative filtering models to return a list of products tailored to your specified recommendation logic.

Can I test attribute filtering like color or size through chat?

Absolutely. The 'search_filtered' tool allows you to pass exact attribute mappings (e.g., 'color:blue,size:L'). Your agent will verify how the API restricts results to those specific structural bounds.

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

Name: Constructor
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

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

Connect your Constructor.io account to any AI agent and take full control of your site search and product discovery workflows through natural conversation.

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

AI-Powered Search — Execute ML-ranked product retrieval dynamically mapped to e-commerce signals and user intent
Predictive Autocomplete — Access fast predictive typing boundaries and trace exact matched categories for any partial query
Dynamic Recommendations — Surface personalized products using collaborative filtering models and custom recommendation pods
Category & Brand Browsing — Navigate through product directory trees and manufacturer taxonomies without any query bias
Advanced Filtering — Apply strict attribute filters (colors, sizes, features) and custom sort rules to refine product discovery results
Collection Management — Retrieve curated marketing clusters and static collections accurately for promotional auditing

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

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

Why Use CrewAI with the Constructor MCP Server

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

Constructor + CrewAI Use Cases

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

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

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

Constructor MCP Tools for CrewAI (10)

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

autocomplete

Perform structural extraction of properties driving active Account logic

browse_brand

Inspect deep internal arrays mitigating specific Plan Math

browse_category

Provision a highly-available JSON Payload generating hard Customer bindings

browse_collection

Identify precise active arrays spanning native Gateway auth

custom_search

Identify precise active arrays spanning native Hold parsing

get_recommendations

Retrieve explicit Cloud logging tracing explicit Vault limits

search_filtered

]` bounding JSON structures restricting arrays to exact colors/sizes or features. Irreversibly vaporize explicit validations extracting rich Churn flags

search_pagination

Dispatch an automated validation check routing explicit Gateway history

search_products

Identify bounded CRM records inside the Headless Constructor.io Platform

search_sorted

Enumerate explicitly attached structured rules exporting active Billing

Example Prompts for Constructor in CrewAI

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

"Search for 'running shoes' in Constructor"

"What products are recommended in the 'home-page-trending' pod?"

"Browse the 'Outdoor Furniture' category"

Troubleshooting Constructor MCP Server with CrewAI

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

Constructor + CrewAI FAQ

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