Bring Customersai
to CrewAI
Learn how to connect Customers.ai to CrewAI and start using 8 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the Customers.ai MCP Server?
Connect your Customers.ai (formerly MobileMonkey) account to any AI agent and take full control of your automated messaging and B2B identity resolution workflows through natural conversation.
What you can do
- Contact Orchestration — List and search your contact database programmatically, retrieving detailed metadata from identity resolution pipelines like X-Ray Pixel
- Multichannel Engagement — Programmatically dispatch plain text or high-fidelity JSON messages (including galleries and buttons) across SMS and chat channels
- Identity Resolution Intelligence — Access leads identified through website visits to prioritize high-intent prospects and maintain a high-fidelity sales pipeline
- Attribute Management — Programmatically update custom contact attributes and manage audience segments through dynamic tagging directly from your agent
- Lead Discovery — Find contacts by email, phone, or external identifiers to perfectly coordinate your multichannel outreach and follow-ups
How it works
1. Subscribe to this server
2. Retrieve your API Key from your Customers.ai dashboard (Settings > API)
3. Start managing your lead engagement from Claude, Cursor, or any MCP client
No more manual scrubbing through identified visitor logs. Your AI acts as your dedicated growth engineer and messaging coordinator.
Who is this for?
- Marketing Operations — instantly retrieve lists of identified website visitors and trigger nurturing sequences using natural language commands
- Sales Development (SDRs) — automate the personalized outreach to high-intent leads without leaving your workspace
- Growth Marketers — integrate identity resolution data and automated messaging into custom performance workflows through simple AI queries
Built-in capabilities (8)
Add a tag to a contact
Get contact profile details
List identified website visitors
Remove a tag from a contact
Search for contacts in Customers.ai
Send a structured JSON message
Send a text message to a contact
Update attributes for a contact
Why CrewAI?
When paired with CrewAI, Customers.ai becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Customers.ai 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
Customers.ai in CrewAI
Customers.ai and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Customers.ai 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 Customers.ai in CrewAI
The Customers.ai 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 8 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
Customers.ai for CrewAI
Every tool call from CrewAI to the Customers.ai 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 Customers.ai API Key?
Log in to your dashboard, navigate to Settings > API, and generate or copy your unique API Key.
What is the X-Ray Pixel?
The X-Ray Pixel is a tool that identifies anonymous website visitors and resolves their identity into actionable lead profiles.
Can I send rich JSON messages?
Yes! Use the send_rich_message tool and provide a JSON payload containing image URLs, buttons, or gallery structures.
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.