Bring Customersai
to Cursor
Learn how to connect Customers.ai to Cursor 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 Cursor?
Cursor's Agent mode turns Customers.ai into an in-editor superpower. Ask Cursor to generate code using live data from Customers.ai and it fetches, processes, and writes. all in a single agentic loop. 8 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
Customers.ai in Cursor
Customers.ai and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Customers.ai to Cursor 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 Cursor
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 Cursor 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 Cursor
Every tool call from Cursor 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.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.