Bring B2b Database
to CrewAI
Learn how to connect RocketReach 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 RocketReach MCP Server?
Connect your RocketReach account to any AI agent and take full control of your B2B lead generation and contact enrichment orchestration through natural conversation. RocketReach provides a premier platform for finding verified emails and phone numbers, and this integration allows you to search for professionals, retrieve company metadata, and manage webhooks directly from your chat interface.
What you can do
- Lead & Person Orchestration — Search for professionals by name, title, or company and retrieve detailed profile metadata programmatically.
- Contact Enrichment Intelligence — Perform instant lookups for specific individuals using RocketReach IDs or LinkedIn URLs to reveal verified contact info directly from the AI interface.
- Company & Firmographic Control — Search and retrieve detailed company profiles, including domains and employee counts via natural language.
- Usage & Credit Oversight — Access real-time account profile metadata and monitor credit usage to ensure your outreach campaigns are always optimized.
- Operational Monitoring — Track system activity, manage webhooks, and retrieve billing info using simple AI commands.
How it works
1. Subscribe to this server
2. Enter your RocketReach API Key from your account settings
3. Start enriching your sales pipeline from Claude, Cursor, or any MCP-compatible client
No more manual LinkedIn scraping or credit wasting. Your AI acts as a dedicated sales development representative or lead analyst.
Who is this for?
- SDRs & Recruiters — quickly retrieve verified contact info for target prospects without switching apps.
- Marketing Teams — automate the enrichment of lead lists and track search history via natural conversation.
- Operations Teams — streamline the retrieval of account statistics and monitor organizational credit health directly within the chat.
Built-in capabilities (12)
Check async lookup status
complete. Create a new webhook
Delete a webhook
Get account profile
Get billing details
Get credit usage stats
List search history
List configured webhooks
Get company details
Consumes 1 credit. Get verified contact info
Search for companies
Search for professionals
Why CrewAI?
When paired with CrewAI, RocketReach becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call RocketReach 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
RocketReach in CrewAI
RocketReach and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect RocketReach 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 RocketReach in CrewAI
The RocketReach 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
RocketReach for CrewAI
Every tool call from CrewAI to the RocketReach 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 enrich a person's contact info using their LinkedIn URL?
Yes! Use the person_lookup tool. Provide the linkedin_url, and your agent will return the verified email addresses and phone numbers associated with that professional profile instantly.
How do I check how many RocketReach credits I have left?
Simply ask the agent to run the get_account_info or get_usage_stats action. It will retrieve your current plan details and remaining search/lookup credits.
How do I find my RocketReach API Key?
Log in to your RocketReach account, navigate to Account > API Usage & Settings, and you will find your unique secret API key there.
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.