Bring B2b Intelligence
to CrewAI
Learn how to connect Lusha to CrewAI and start using 12 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Lusha MCP Server?
Connect your Lusha account to any AI agent and take full control of your sales prospecting and data enrichment through natural conversation. Lusha provides a premier B2B database, and this integration allows you to retrieve high-fidelity contact details (email, phone), enrich company metadata, and search for new prospects directly from your chat interface.
What you can do
- Contact & Person Enrichment — Lookup detailed contact metadata programmatically using name, company, or LinkedIn URLs to ensure your CRM is always synchronized.
- Company & Firmographic Intelligence — Access and monitor company data including industry, revenue, and headcount directly from the AI interface to qualify accounts in real-time.
- Prospecting & Search Control — Search for new contacts and companies matching your Ideal Customer Profile (ICP) via natural language to drive better sales efficiency.
- Usage & Credit Oversight — Access granular details for your credit consumption and remaining balance using simple AI commands to maintain a clear overview of your resources.
- Operational Monitoring — Track system responses and manage data ingestion to ensure your sales workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Lusha API Key from your dashboard settings
3. Start enriching your sales data from Claude, Cursor, or any MCP-compatible client
No more manual copy-pasting from LinkedIn profiles. Your AI acts as a dedicated sales researcher or lead qualification assistant.
Who is this for?
- Sales Development Reps (SDRs) — quickly retrieve phone numbers and monitor account health without switching apps.
- Account Executives — automate the enrichment of new leads and track prospecting progress via natural conversation.
- Marketing Teams — streamline the retrieval of firmographic metadata and monitor data quality directly within the chat.
Built-in capabilities (12)
Enrich multiple companies
Enrich multiple contacts
Get firmographics
Get contact details
Check connection
Check account balance
Enrich by email
Enrich by LinkedIn
Check API usage
Search for businesses
Search for contacts
Verify API key
Why CrewAI?
When paired with CrewAI, Lusha becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Lusha 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
Lusha in CrewAI
Lusha and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Lusha 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 Lusha in CrewAI
The Lusha 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 12 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
Lusha for CrewAI
Every tool call from CrewAI to the Lusha MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
Can my AI automatically find the phone number for a LinkedIn profile?
Yes! Use the get_person_by_linkedin tool. Provide the LinkedIn URL, and your agent will respond with complete metadata for the record, including verified emails and direct phone numbers in seconds.
How do I find my Lusha API Key?
Log in to your Lusha account, navigate to Settings > API & Integrations, and you will find your unique secret token there.
Does it support bulk enrichment?
Yes, use the bulk_enrich_person tool to provide an array of contacts. The AI will process the batch and return enriched metadata for all entries in a single operation.
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.