Bring Outreach
to CrewAI
Learn how to connect Outreach 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 Outreach MCP Server?
Connect your Outreach.io account to any AI agent and take full control of your sales orchestration and prospect engagement through natural conversation. Outreach is the premier sales engagement platform, and this integration allows you to retrieve prospect metadata, enroll leads into automated sequences, and monitor mailing performance directly from your chat interface.
What you can do
- Prospect & Audience Orchestration — List all managed prospects and retrieve detailed profile metadata programmatically to ensure your sales database is always synchronized.
- Sequence & Automation Control — Enroll prospects into automated sequences and monitor sequence states directly from the AI interface to track lead nurturing progress.
- Communication Intelligence — Access and monitor sent mailings and retrieve detailed engagement metadata via natural language to drive better follow-up efficiency.
- Account & Deal Oversight — Access organizational accounts and monitor sales opportunities using simple AI commands to maintain a clear overview of your pipeline.
- Operational Monitoring — Track system responses and manage sales tasks to ensure your outreach workflows are always optimized.
How it works
1. Subscribe to this server
2. Enter your Outreach.io OAuth2 Access Token from your developer portal
3. Start managing your sales engagement from Claude, Cursor, or any MCP-compatible client
No more manual status checking in the CRM. Your AI acts as a dedicated sales operations lead or engagement coordinator.
Who is this for?
- SDRs & BDRs — quickly retrieve prospect summaries and monitor sequence health without switching apps.
- Sales Managers — automate the retrieval of mailing stats and track team productivity via natural conversation.
- Growth Marketers — streamline the retrieval of account metadata and monitor pipeline health directly within the chat.
Built-in capabilities (12)
Enroll prospect in sequence
Add new prospect
Get full prospect info
Get account profile
List outreach accounts
List message templates
List sales deals
List engageable people
List pending actions
List sent mailings
List sales sequences
Modify prospect info
Why CrewAI?
When paired with CrewAI, Outreach becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Outreach 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
Outreach in CrewAI
Outreach and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Outreach 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 Outreach in CrewAI
The Outreach 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
Outreach for CrewAI
Every tool call from CrewAI to the Outreach 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 prospect by their ID?
Yes! Use the get_prospect tool with the Prospect ID. Your agent will respond with complete metadata for the record, including custom fields, sequence history, and owner info in seconds.
How do I find my Outreach.io OAuth2 Access Token?
Log in to your Outreach Developer Portal, create a new App, and use the provided client credentials to perform the OAuth 2.0 flow to obtain a secret access token.
Does this work with the Outreach API v2?
Yes, this MCP server is specifically built using the Outreach JSON:API v2 specification to ensure full compatibility with modern sales workflows.
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.