4,000+ servers built on vurb.ts
Vinkius

Proxycurl (LinkedIn Data) MCP Server for CrewAIGive CrewAI instant access to 18 tools to Add Monitor Target, Check Disposable Email, Company Website Lookup, and more

MCP Inspector GDPR Free for Subscribers

Connect your CrewAI agents to Proxycurl (LinkedIn Data) through Vinkius, pass the Edge URL in the `mcps` parameter and every Proxycurl (LinkedIn Data) tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Ask AI about this MCP Server for CrewAI

The Proxycurl (LinkedIn Data) MCP Server for CrewAI is a standout in the Sales Automation category — giving your AI agent 18 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Proxycurl (LinkedIn Data) Specialist",
    goal="Help users interact with Proxycurl (LinkedIn Data) effectively",
    backstory=(
        "You are an expert at leveraging Proxycurl (LinkedIn Data) tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Proxycurl (LinkedIn Data) "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 18 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Proxycurl (LinkedIn Data)
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About 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.

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.

What you can do

  • Company Intelligence — Resolve company names to websites, fetch logos, and retrieve deep metadata including industry and leadership using company_website_lookup and get_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 using search_employees.
  • Market Analysis — Identify competitors based on product similarity with get_competitor_listing and list probable customers or partners.
  • Monitoring — Create and manage monitor feeds to track organizational changes over time using create_monitor_feed.

The Proxycurl (LinkedIn Data) MCP Server exposes 18 tools through the Vinkius. Connect it to CrewAI in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 18 Proxycurl (LinkedIn Data) tools available for CrewAI

When CrewAI connects to Proxycurl (LinkedIn Data) through Vinkius, your AI agent gets direct access to every tool listed below — spanning linkedin-data, b2b-intelligence, company-enrichment, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

add

Add monitor target on Proxycurl (LinkedIn Data)

Add a target to an existing monitor feed

check

Check disposable email on Proxycurl (LinkedIn Data)

Detect temporary or throwaway email addresses

company

Company website lookup on Proxycurl (LinkedIn Data)

Resolve a company name to its canonical website URL

create

Create monitor feed on Proxycurl (LinkedIn Data)

Create a new monitor feed for company changes

get

Get company details on Proxycurl (LinkedIn Data)

Retrieve comprehensive company metadata and leadership teams

get

Get company employee count on Proxycurl (LinkedIn Data)

Retrieve the estimated headcount range for a company

get

Get company funding on Proxycurl (LinkedIn Data)

It may take up to 5 minutes. Retrieve full funding history, rounds, and participating investors

get

Get company logo on Proxycurl (LinkedIn Data)

Retrieve a 128x128 PNG logo URL for any company

get

Get company updates on Proxycurl (LinkedIn Data)

Aggregate blog posts and X/Twitter updates into a mixed timeline

get

Get competitor listing on Proxycurl (LinkedIn Data)

Find competitors and the reasoning (keyword overlap or product similarity)

get

Get credit balance on Proxycurl (LinkedIn Data)

Check your remaining API credit balance

get

Get customer listing on Proxycurl (LinkedIn Data)

Get a list of probable customers, investors, and partner platforms

get

Get employee profile on Proxycurl (LinkedIn Data)

Enrich professional profiles from work emails or name/employer combinations

get

Get monitor rss on Proxycurl (LinkedIn Data)

Get the RSS feed for a specific monitor feed

get

Get similar employees on Proxycurl (LinkedIn Data)

Repeat queries are served free from cache. Find counterparts in similar roles at competing companies

list

List monitor feeds on Proxycurl (LinkedIn Data)

List all active monitor feeds

lookup

Lookup work email on Proxycurl (LinkedIn Data)

Best-effort lookup of a public work email from a name and domain

search

Search employees on Proxycurl (LinkedIn Data)

Find current employees of a company by role and geography

Connect Proxycurl (LinkedIn Data) to CrewAI via MCP

Follow these steps to wire Proxycurl (LinkedIn Data) into CrewAI. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

01

Install CrewAI

Run pip install crewai
02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com
03

Customize the agent

Adjust the role, goal, and backstory to fit your use case
04

Run the crew

Run python crew.py. CrewAI auto-discovers 18 tools from Proxycurl (LinkedIn Data)

Why Use CrewAI with the Proxycurl (LinkedIn Data) MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Proxycurl (LinkedIn Data) through the Model Context Protocol.

01

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

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

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

04

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) + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Proxycurl (LinkedIn Data) MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Proxycurl (LinkedIn Data) for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Proxycurl (LinkedIn Data), analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Proxycurl (LinkedIn Data) tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Proxycurl (LinkedIn Data) against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Example Prompts for Proxycurl (LinkedIn Data) in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Proxycurl (LinkedIn Data) immediately.

01

"Find the official website for 'Nvidia'."

02

"Show me the funding history for 'SpaceX'."

03

"Who are the main competitors for 'Zoom'?"

Troubleshooting Proxycurl (LinkedIn Data) MCP Server with CrewAI

Common issues when connecting Proxycurl (LinkedIn Data) to CrewAI through Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

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.

Proxycurl (LinkedIn Data) + CrewAI FAQ

Common questions about integrating Proxycurl (LinkedIn Data) MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Explore More MCP Servers

View all →