Bring Linkedin Automation
to CrewAI
Learn how to connect MagicDrip 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 MagicDrip MCP Server?
Connect your MagicDrip (magicdrip.com) account to any AI agent and take full control of your LinkedIn sales orchestration and automated outreach through natural conversation. MagicDrip provides a powerful platform for scaling B2B social selling, and this integration allows you to retrieve lead metadata, trigger automated connection requests, and monitor campaign performance directly from your chat interface.
What you can do
- Lead & Prospect Orchestration — List all managed leads and retrieve detailed profile metadata programmatically to ensure your sales funnel is always synchronized.
- Campaign Lifecycle Management — Access and monitor your automated LinkedIn campaigns and retrieve detailed performance metadata directly from the AI interface.
- Outreach & Message Intelligence — Send automated connection requests and direct messages via natural language to drive better engagement and conversion rates.
- Analytics & Quota Oversight — Retrieve aggregated account statistics and monitor your available slots and limits using simple AI commands.
- Operational Monitoring — Track system responses and manage webhook metadata to ensure your social selling workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your MagicDrip Access Token from your dashboard settings
3. Start managing your LinkedIn outreach from Claude, Cursor, or any MCP-compatible client
No more manual connection sending in LinkedIn. Your AI acts as a dedicated sales development rep (SDR) or social selling assistant.
Who is this for?
- SDRs & BDRs — quickly retrieve lead summaries and coordinate follow-ups without switching apps.
- Growth Managers — automate the retrieval of campaign metadata and track sequence progress via natural conversation.
- Founders & Sales Teams — streamline the ingestion of new leads and monitor organizational growth directly within the chat.
Built-in capabilities (12)
Add a new lead to a campaign
Verify The Magic Drip API status
Get overall account performance
Get authenticated account info
Check account daily limits
Retrieve campaign analytics
Get details for a specific prospect
g., new reply). List active webhooks
List LinkedIn automation campaigns
List prospects from outreach campaigns
Send a direct LinkedIn message
Send a connection request
Why CrewAI?
When paired with CrewAI, MagicDrip becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call MagicDrip 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
MagicDrip in CrewAI
MagicDrip and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect MagicDrip 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 MagicDrip in CrewAI
The MagicDrip 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
MagicDrip for CrewAI
Every tool call from CrewAI to the MagicDrip 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 details for a specific lead by its ID?
Yes! Use the get_lead_details tool with the Lead ID. Your agent will respond with complete metadata for the record, including name, LinkedIn profile info, and campaign status in seconds.
How do I find my MagicDrip Access Token?
Log in to your MagicDrip account, navigate to Settings > API, and you will find your unique secret token there.
Can I send connection requests via the AI?
Absolutely. Use the send_connection_request tool. Provide the necessary profile metadata, and the AI will trigger the connection request on LinkedIn for you instantly.
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.