Bring Site Search
to CrewAI
Learn how to connect Constructor to CrewAI and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the 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.
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
How it works
- Subscribe to this server
- Enter your Constructor.io Public API Key (found in Dashboard > Integration)
- Start optimizing your e-commerce discovery from Claude, Cursor, or any MCP-compatible client
Who is this for?
- E-commerce Managers — audit search rankings and recommendation pods without manual dashboard testing
- Product Owners — monitor category browsing performance and verify attribute filtering logic in real-time
- Developers — test and debug search API parameters and personalized recommendation outputs through natural language
- Marketing Teams — verify that curated collections and brand taxonomies are correctly mapped and rankable
Built-in capabilities (10)
Perform structural extraction of properties driving active Account logic
Inspect deep internal arrays mitigating specific Plan Math
Provision a highly-available JSON Payload generating hard Customer bindings
Identify precise active arrays spanning native Gateway auth
Identify precise active arrays spanning native Hold parsing
Retrieve explicit Cloud logging tracing explicit Vault limits
]` bounding JSON structures restricting arrays to exact colors/sizes or features. Irreversibly vaporize explicit validations extracting rich Churn flags
Dispatch an automated validation check routing explicit Gateway history
Identify bounded CRM records inside the Headless Constructor.io Platform
Enumerate explicitly attached structured rules exporting active Billing
Why CrewAI?
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.
- —
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
mcpsparameter 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 in CrewAI
Constructor and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Constructor to CrewAI through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Constructor in CrewAI
The Constructor 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. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in CrewAI only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Constructor for CrewAI
Every tool call from CrewAI to the Constructor MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
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.
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.
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.
Explore More MCP Servers
View all →
The Met Museum
8 toolsExplore 470,000+ artworks from The Metropolitan Museum of Art — search by artist, title, culture, date and department.
Google Lighthouse SEO Auditor
1 toolsTransform your AI into a Technical SEO & Performance Agency. Instantly run official Google PageSpeed Insights (Lighthouse) audits on any website and get exact code fixes to achieve a perfect 100/100 score.
Asaas
8 toolsManage payments, customers, and subscriptions with Asaas — the complete digital account for Brazilian businesses via AI.
Airbrake
10 toolsCatch application errors in real time, track performance bottlenecks, and keep your codebase healthy with proactive monitoring.