Bring Visitor Identification
to CrewAI
Learn how to connect HappierLeads to CrewAI and start using 17 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the HappierLeads MCP Server?
Connect your HappierLeads account to any AI agent and turn anonymous website traffic into identified B2B leads through natural conversation.
What you can do
- Visitor Identification — List all identified B2B visitors with company data, filter by country, and search by company name or domain
- Lead Management — Browse all identified companies, filter by industry vertical, and focus on qualified high-intent leads
- Session Analysis — Inspect individual browsing sessions with page-by-page navigation paths and time spent
- Page View Tracking — List all pages viewed by a specific visitor for engagement insights
- Segmentation — Browse saved visitor segments and inspect criteria for targeted analysis
- Real-Time Alerts — Access notifications for high-value visitor activity
- Analytics Dashboard — Retrieve traffic overview: visitor count, identified companies, conversion rates, and top pages
How it works
1. Subscribe to this server
2. Enter your HappierLeads API Key from your account settings
3. Start identifying leads from Claude, Cursor, or any MCP-compatible client
Who is this for?
- Sales Teams — identify which companies visit your website and prioritize outreach based on browsing behavior
- Marketing Teams — analyze traffic sources, segment visitors, and track campaign-driven visits
- Growth Teams — monitor high-intent pages like pricing and demo requests to identify warm leads
Built-in capabilities (17)
Verify connectivity
Get analytics overview
Get lead details
Get segment details
Get session details
Get top pages
Get visitor details
List identified leads
Filter leads by industry
List notifications
List page views
List qualified leads
List segments
List visitor sessions
List website visitors
Filter visitors by country
Search visitors
Why CrewAI?
When paired with CrewAI, HappierLeads becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call HappierLeads 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
HappierLeads in CrewAI
HappierLeads and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect HappierLeads 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 HappierLeads in CrewAI
The HappierLeads 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 17 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
HappierLeads for CrewAI
Every tool call from CrewAI to the HappierLeads MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can I identify which companies are visiting my website?
Yes! The list_visitors tool retrieves all identified B2B website visitors with company name, industry, employee count, and visit details. Use search_visitors to find specific companies by name or domain, and list_visitors_by_country to filter by geographic region. Use get_visitor for the full company profile.
Can I see which pages each company visited and how long they stayed?
Yes. Use list_sessions with a Visitor ID to see all browsing sessions, then get_session for page-by-page navigation paths with time spent per page. Use list_page_views to get all pages viewed by a specific visitor. This reveals purchase intent — visitors spending time on pricing or demo pages are warm leads.
Can I focus only on high-intent qualified leads?
Yes. The list_qualified_leads tool retrieves only leads that meet your qualification criteria (e.g., multiple visits, pricing page views, minimum session duration). Use list_leads_by_industry to further filter by vertical. Use list_notifications for real-time alerts when high-value visitors are on your site.
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.