Bring Customersai
to LangChain
Learn how to connect Customers.ai to LangChain 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 LangChain?
LangChain's ecosystem of 500+ components combines seamlessly with Customers.ai through native MCP adapters. Connect 8 tools via Vinkius and use ReAct agents, Plan-and-Execute strategies, or custom agent architectures. with LangSmith tracing giving full visibility into every tool call, latency, and token cost.
- —
The largest ecosystem of integrations, chains, and agents. combine Customers.ai MCP tools with 500+ LangChain components
- —
Agent architecture supports ReAct, Plan-and-Execute, and custom strategies with full MCP tool access at every step
- —
LangSmith tracing gives you complete visibility into tool calls, latencies, and token usage for production debugging
- —
Memory and conversation persistence let agents maintain context across Customers.ai queries for multi-turn workflows
Customers.ai in LangChain
Customers.ai and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Customers.ai to LangChain 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 LangChain
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 LangChain 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 LangChain
Every tool call from LangChain 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 LangChain connect to MCP servers?
Use langchain-mcp-adapters to create an MCP client. LangChain discovers all tools and wraps them as native LangChain tools compatible with any agent type.
Which LangChain agent types work with MCP?
All agent types including ReAct, OpenAI Functions, and custom agents work with MCP tools. The tools appear as standard LangChain tools after the adapter wraps them.
Can I trace MCP tool calls in LangSmith?
Yes. All MCP tool invocations appear as traced steps in LangSmith, showing input parameters, response payloads, latency, and token usage.
MultiServerMCPClient not found
Install: pip install langchain-mcp-adapters