Bring Contact Discovery
to CrewAI
Learn how to connect ContactOut to CrewAI and start using 7 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ContactOut MCP Server?
Connect your ContactOut account to any AI agent to streamline your B2B lead generation and talent acquisition workflows through natural conversation. ContactOut provides a powerful intelligence layer for discovering verified contact information and enriching professional profiles at scale.
What you can do
- Contact Discovery Orchestration — Instantly retrieve verified email addresses and direct phone numbers using LinkedIn profile URLs programmatically
- Professional Enrichment — Enrich contact and company data with detailed attributes, including job titles, locations, and social links to maintain a high-fidelity CRM
- Deep Semantic Search — Programmatically search the ContactOut database of 300M+ people using advanced filters for skills, titles, and locations
- Identity Resolution — Find the LinkedIn profile associated with a specific email address to perfectly coordinate your multichannel outreach
- Administrative Visibility — Programmatically track your credit balance and API usage statistics to coordinate your recruitment and sales budgets
How it works
1. Subscribe to this server
2. Retrieve your API Key from your ContactOut dashboard (Settings > API)
3. Start finding decision-makers and enriching your lead lists from Claude, Cursor, or any MCP client
No more manual profile scraping or guessing email formats. Your AI acts as your dedicated sales associate and recruitment coordinator.
Who is this for?
- Sales Development (SDRs) — build highly targeted outreach lists with verified contact info using natural language commands
- Technical Recruiters — search for candidates with specific skills and retrieve contact details without leaving your workspace
- Growth Marketers — automate lead enrichment and identify LinkedIn profiles from email lists through simple AI queries
Built-in capabilities (7)
Enrich company data
Enrich contact data
Find email by LinkedIn profile
Find LinkedIn profile by email
Get API usage statistics
Search for companies
Search for people
Why CrewAI?
When paired with CrewAI, ContactOut becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call ContactOut 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
ContactOut in CrewAI
ContactOut and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ContactOut 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 ContactOut in CrewAI
The ContactOut 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 7 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
ContactOut for CrewAI
Every tool call from CrewAI to the ContactOut MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my ContactOut API Key?
Log in to your account, navigate to Settings > API, and copy your unique access token.
Can I search for people by skills and location?
Yes! The search_people tool accepts a JSON object with filters like skills, location, and job_title programmatically.
How do I find an email using a LinkedIn URL?
Use the find_email_by_linkedin tool and provide the full LinkedIn profile URL to retrieve verified contact details.
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.