Customers.ai MCP. Identify leads, tag contacts, and send messages.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Customers.ai lets you identify anonymous website visitors by name and turn them into actionable leads directly from your AI agent.
You can search contact databases, add custom tags, update attributes, and send rich messages or SMS texts across multiple channels.
What your AI agents can do
Add tag to contact
Applies a custom tag to an existing contact record.
Get contact
Retrieves all profile details for a specified contact by ID or identifier.
List xray leads
Provides a list of website visitors who have been identified via X-Ray Pixel tracking.
Retrieve detailed metadata and lists of website visitors captured by X-Ray Pixel.
Locate any existing contact profile using criteria like email or phone number.
Dispatch complex, formatted messages that include buttons and galleries across chat channels.
Transmit simple, plain text messages to a specific contact's phone number.
Programmatically modify custom attributes and audience tags on any contact profile.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 CompatibleWaiting for input…
Customers.ai MCP: 8 Tools for Contact Management
These tools let your agent find contacts by email or phone, update their records, list identified visitors, and execute various types of messaging.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Customers.ai on Vinkius019dd0daadd tag to contact
Applies a custom tag to an existing contact record.
019dd0daget contact
Retrieves all profile details for a specified contact by ID or identifier.
019dd0dalist xray leads
Provides a list of website visitors who have been identified via X-Ray Pixel tracking.
019dd0daremove tag from contact
Deletes one or more tags from a contact record.
019dd0dasearch contacts
Searches the entire database of contacts using specific criteria like email or name.
019dd0dasend rich message
Sends a highly structured, formatted message containing buttons and galleries across chat channels.
019dd0dasend text message
Sends simple, plain text messages via SMS to a contact's phone number.
019dd0daupdate contact attributes
Changes specific pieces of information or custom data points on a contact profile.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Customers.ai, then connect any of our 4,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Customers.ai. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Dealing with the mess of anonymous web traffic today.
Right now, when a promising visitor leaves your site, you're usually left staring at dashboards. You have to manually pull data from X-Ray Pixel, cross-reference that name against your CRM list using exported spreadsheets, and then decide who is worth calling. It’s slow, it’s tedious, and half the time, critical leads fall through the cracks because someone forgot to update a tag.
With this MCP, you just ask your agent about those anonymous visitors. You don't touch dashboards or spreadsheets; you simply tell the AI to run `list_xray_leads`. The result is clean data that your agent can use immediately to find and act on the contact.
Send personalized messages using the send_rich_message tool.
Before, sending a follow-up required you to jump into multiple platforms—the messaging tool for SMS, and another system for rich media. You had to manually format JSON or build out complex buttons just to keep the conversation going, which was a huge time sink.
Now, your agent handles it all in one go. It sends that structured message directly from the chat interface, ensuring the client sees exactly what you intended—buttons, galleries, and plain text—without any manual switching.
What you can do with this MCP connector
This MCP connects your automated messaging and B2B identity resolution to your natural language agent. When a prospect visits your site, you don't have to manually scrub through visitor logs; the AI does it for you. It identifies anonymous traffic, prioritizing high-intent leads so you know exactly who to talk to next.
You can then use the agent to find contacts by email or phone number and update their records with specific details. Need to segment them? The agent handles that, allowing you to add tags and update custom attributes instantly. Finally, once a lead is qualified, your AI sends out targeted outreach via rich JSON messages or simple SMS texts, keeping your follow-up consistent across all channels.
Because credentials pass through Vinkius's zero-trust proxy, your keys are used only in transit—they never sit on disk. This keeps your sensitive contact data secure while letting you run complex campaigns.
019dd0da-d6f7-738d-9506-afcc99d08ef7 How Customers.ai MCP Works
- 1 First, connect your API key to the MCP and establish context for a target lead (e.g., by asking your agent to find the name or email of an interested visitor).
- 2 Next, tell the agent what needs doing—maybe it needs to add a 'High Intent' tag or send a follow-up text message.
- 3 The platform executes the required actions, returning confirmation that the contact record was updated and/or the message was successfully sent.
The bottom line is you get a single point of access to manage lead data—from discovery to initial outreach—without leaving your AI agent's chat window.
Who Is Customers.ai MCP For?
Marketing Operations leads and Sales Development Reps who are tired of switching between the CRM, marketing automation platform, and messaging tools. This is for anyone whose job requires moving data or sending messages based on a prospect's online behavior.
They use this MCP to find new leads using the agent, tag them as 'Qualified', and then send an immediate follow-up text message without logging into a separate tool.
They rely on the system to pull in fresh data from identified visitors and use it to update contact attributes before triggering a campaign sequence.
Needs reliable methods to list identified website visitors and build complex, multi-stage nurturing sequences using natural language commands.
What Changes When You Connect
- Quickly find new opportunities: Use the
list_xray_leadsfunction to pull fresh data on anonymous website visitors without manual dashboard scrubbing. - Maintain clean records: The agent lets you run
add_tag_to_contactorremove_tag_from_contactinstantly, keeping your audience segmentation accurate for campaigns. - Multi-channel consistency: Whether it's a simple text alert via
send_text_messageor a detailed JSON message usingsend_rich_message, the outreach feels unified. - Deep data access: You can use
get_contactand then modify records withupdate_contact_attributesto build out a full prospect profile in one go. - Focused searching: Use
search_contactswhen you need to find someone by email or phone, bypassing the need for multiple search tabs.
Real-World Use Cases
A site visitor leaves without converting.
The problem is that a high-value prospect visits your pricing page but vanishes. You ask your agent to run list_xray_leads to identify them, find their full profile using search_contacts, and then send an immediate follow-up text message via send_text_message reminding them of the next steps.
A campaign requires complex follow-up.
You need to qualify a list of leads. You ask your agent to use get_contact on several IDs, then apply a 'Hot Lead' tag using add_tag_to_contact, and finally send them a rich JSON message detailing the next steps.
A lead record is missing key details.
An old contact profile needs current information. Your agent runs update_contact_attributes to add new department data, then uses remove_tag_from_contact to clean up outdated tags before a fresh outreach.
Coordinating multi-touchpoint sales efforts.
A sale involves multiple teams. Your agent first finds the contact via email using search_contacts, then sends an introductory text message, and finally updates their status to 'Sales Qualified' using update_contact_attributes.
The Tradeoffs
Trying to update data manually.
Copying a visitor's name from the X-Ray dashboard and then pasting it into the CRM record, only to realize you also need to change their job title somewhere else.
→
Let your agent run get_contact first. Then tell it to use update_contact_attributes to make all necessary changes in one go. This keeps everything consistent.
Sending repetitive messages.
Manually sending the same boilerplate text message every time a new lead comes through, wasting time and sounding robotic.
→
Instead of manual texting, use send_rich_message. This allows you to build out a structured message with custom buttons that feel far more personal and professional.
Forgetting to clean up old tags.
A contact is marked 'Trial User' but they bought a full package. The tag remains, confusing sales reps who see outdated information.
→
Always use remove_tag_from_contact after the status changes. This keeps your system accurate and prevents agents from misinterpreting old data.
When It Fits, When It Doesn't
Use this MCP if you need to bridge identity resolution (identifying who visited) with actioning that data (updating records or sending messages). You're building a complete loop: Visitor -> Identified Lead -> Tagged Contact -> Messaged. Don't use it, though, if your only goal is simple reporting; just viewing lists of visitors is better handled by dedicated analytics tools. If you only need to send one-off emails without any preceding data enrichment or tagging logic, a general email MCP would be cleaner.
If the process involves gathering visitor details and then performing an action on the contact record—like sending a message or changing their status—this is your core connector.
Common Questions About Customers.ai MCP
How do I list identified website visitors using the list_xray_leads tool? +
You prompt your agent to run list_xray_leads. The AI will retrieve a current list of all visitors identified by X-Ray Pixel, giving you metadata on who visited and when.
Can I update contact attributes using the update_contact_attributes tool? +
Yes. You ask your agent to run update_contact_attributes and specify exactly what data needs changing (like a department or title) for a given contact ID.
What's the difference between send_text_message and send_rich_message? +
Use send_text_message only when you need to send plain text, like a quick SMS reminder. Use send_rich_message for anything more complex that needs buttons or image galleries.
How do I find an existing lead by phone number? (search_contacts) +
You instruct your agent to use the search_contacts tool, providing the contact's phone number as a parameter. The AI returns all matching profile data.
What is the best way to manage audience segmentation using both `add_tag_to_contact` and `remove_tag_from_contact`? +
You control segments by directly manipulating tags. Use add_tag_to_contact when a lead meets criteria, like making a purchase. Always follow up with remove_tag_from_contact if that status changes or expires.
If I use the `get_contact` tool, what specific metadata fields can my agent retrieve about a user's profile? +
The tool retrieves comprehensive contact details beyond just names and emails. You get access to custom attributes, historical tags, and detailed identity resolution pipeline data for full context.
What happens if I run too many searches using the `search_contacts` tool in a short time? +
The system implements rate limiting to keep things stable. If you hit the limit, your agent will receive an explicit error code telling you how long to wait before trying again.
How does my AI client handle failures when sending messages using `send_text_message`? +
The tool call returns a detailed status log. If the send fails, the log specifies the reason—like invalid phone number or carrier rejection—so you know exactly why it failed.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.