Bring Lead Nurturing
to CrewAI
Learn how to connect VBOUT to CrewAI and start using 9 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the VBOUT MCP Server?
Connect your VBOUT marketing automation account to any AI agent and simplify how you manage your lead lifecycle, multi-channel campaigns, and social presence through natural conversation.
What you can do
- Lead Management — List and search contacts, and add new leads to specific email marketing lists instantly.
- Automation Control — Query and trigger marketing automation workflows for specific contacts to scale your engagement.
- Campaign Monitoring — List active and past marketing campaigns to track your commercial efforts.
- Social Scheduling — Create and publish social media posts directly from your workspace via AI commands.
- E-commerce Sync — Log customer orders into VBOUT to power lifecycle marketing and personalized segments.
How it works
1. Subscribe to this server
2. Enter your VBOUT API Key (found in your account settings under API)
3. Start managing your marketing engine from Claude, Cursor, or any MCP client
Who is this for?
- Marketing Managers — quickly check campaign statuses and publish social updates via simple AI queries.
- Sales Teams — add new leads to nurture workflows and retrieve contact details without leaving the CRM or workspace.
- E-commerce Owners — sync order data and monitor customer engagement levels directly from the AI assistant.
Built-in capabilities (9)
Requires email and list_id. Add a contact to a list
Add an e-commerce order
Create a social media post
Get contact details
List marketing campaigns
List VBOUT email marketing lists
List automation workflows
Search for contacts
Trigger a workflow for a contact
Why CrewAI?
When paired with CrewAI, VBOUT becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call VBOUT 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
VBOUT in CrewAI
VBOUT and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect VBOUT 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 | 3,400+ 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 VBOUT in CrewAI
The VBOUT 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 9 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
VBOUT for CrewAI
Every tool call from CrewAI to the VBOUT MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I search for a specific contact using a keyword?
Yes! Use the search_contacts tool and provide your keyword. The agent will return matching contacts from your VBOUT database.
How do I trigger an automation for a new lead?
Use the trigger_workflow action. You'll need the Workflow ID and the contact's email address to start the automation manually via AI.
Is it possible to post to my social channels directly?
Absolutely. Use the create_social_post tool, provide your content and an optional link. VBOUT will handle the publishing to your connected profiles.
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.