Bring Linkedin Data
to CrewAI
Learn how to connect Proxycurl (LinkedIn Data) to CrewAI and start using 18 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Proxycurl (LinkedIn Data) MCP Server?
Connect Proxycurl to your AI agent to access real-time B2B intelligence and LinkedIn-derived data. This server provides a powerful suite of tools for sales, recruitment, and market research.
What you can do
- Company Intelligence — Resolve company names to websites, fetch logos, and retrieve deep metadata including industry and leadership using
company_website_lookupandget_company_details. - Financial Insights — Access complete funding histories, investment rounds, and participating investors for private and public companies via
get_company_funding. - People Data — Enrich professional profiles from work emails or names with
get_employee_profile, and search for employees within specific organizations usingsearch_employees. - Market Analysis — Identify competitors based on product similarity with
get_competitor_listingand list probable customers or partners. - Monitoring — Create and manage monitor feeds to track organizational changes over time using
create_monitor_feed.
How it works
- Subscribe to this server
- Enter your Proxycurl API Key
- Start querying B2B data from Claude, Cursor, or any MCP client
Who is this for?
- Sales & RevOps — Automate lead enrichment and find decision-makers without manual searching.
- Recruiters — Identify talent pools and enrich candidate profiles instantly.
- Market Researchers — Map out competitive landscapes and track company growth metrics.
Built-in capabilities (18)
Add a target to an existing monitor feed
Detect temporary or throwaway email addresses
Resolve a company name to its canonical website URL
Create a new monitor feed for company changes
Retrieve comprehensive company metadata and leadership teams
Retrieve the estimated headcount range for a company
It may take up to 5 minutes. Retrieve full funding history, rounds, and participating investors
Retrieve a 128x128 PNG logo URL for any company
Aggregate blog posts and X/Twitter updates into a mixed timeline
Find competitors and the reasoning (keyword overlap or product similarity)
Check your remaining API credit balance
Get a list of probable customers, investors, and partner platforms
Enrich professional profiles from work emails or name/employer combinations
Get the RSS feed for a specific monitor feed
Repeat queries are served free from cache. Find counterparts in similar roles at competing companies
List all active monitor feeds
Best-effort lookup of a public work email from a name and domain
Find current employees of a company by role and geography
Why CrewAI?
When paired with CrewAI, Proxycurl (LinkedIn Data) becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Proxycurl (LinkedIn Data) 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
Proxycurl (LinkedIn Data) in CrewAI
Proxycurl (LinkedIn Data) and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Proxycurl (LinkedIn Data) 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 | 4,000+ 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 Proxycurl (LinkedIn Data) in CrewAI
The Proxycurl (LinkedIn Data) 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 18 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
Proxycurl (LinkedIn Data) for CrewAI
Every tool call from CrewAI to the Proxycurl (LinkedIn Data) 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 a company's official website if I only have their name?
Use the company_website_lookup tool. It resolves a company name to its canonical URL, which is the primary identifier needed for most other company-related tools.
Can I see who invested in a specific startup?
Yes. The get_company_funding tool provides a detailed history of funding rounds, including the amounts raised and the names of participating investors.
Is it possible to get professional details from just a work email?
Absolutely. Use the get_employee_profile tool with the work_email parameter to retrieve enriched professional data, including current role and employer information.
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.
Explore More MCP Servers
View all →
FlowUs
10 toolsAll-in-one knowledge management and collaboration platform — manage pages, blocks, and databases via AI.
Donately
11 toolsManage Donately fundraising and donor data using AI agents.
Finmo
12 toolsManage global pay-ins, payouts, and multi-currency wallets through AI agents with Finmo.
Nuclino
12 toolsEquip your AI agent with full read/write access to your Nuclino workspaces, teams, and items — the unified tool for knowledge, docs, and projects.