Bring Customer Io
to Claude Desktop
Learn how to connect Customer.io to Claude Desktop 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 Customer.io MCP Server?
Connect your Customer.io account to any AI agent and take full control of your automated lifecycle marketing and customer engagement workflows through natural conversation.
What you can do
- Audience Orchestration — List and manage customer profiles programmatically, retrieving detailed attributes, traits, and segment memberships to coordinate personalized journeys
- Segment Intelligence — Access your complete directory of data-driven and manual segments to understand audience distributions and monitor real-time membership counts
- Campaign Architecture — Monitor automated marketing campaigns and retrieve high-fidelity performance reports including delivery, open, and click metrics
- Message Dispatch — Programmatically trigger manual broadcasts or send specific transactional emails to individuals using pre-defined message templates
- Regional Flexibility — Connect to both US and EU regions using specialized app API keys and regional base URLs directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your App API Key from Customer.io (Settings > Account Settings > API Keys)
3. Identify your Region (US or EU) to ensure correct endpoint routing
4. Start managing your lifecycle marketing from Claude, Cursor, or any MCP client
No more manual scrubbing through people tables or checking individual campaign logs in the portal. Your AI acts as your dedicated growth marketer and automation coordinator.
Who is this for?
- Growth Marketers — instantly retrieve campaign results and check user segment memberships using natural language commands
- Product Managers — monitor customer engagement metrics and verify profile attributes without leaving your workspace
- Developers & Ops — automate transactional messaging and manage app-level metadata through simple AI queries
Built-in capabilities (12)
Trigger manual broadcast
Check campaign stats
Check API health
Get person profile
List automated campaigns
List user segments
io. List audience people
List saved newsletters
List one-to-many messages
Get people in segment
g. password resets). List 1-to-1 messages
Send individual email
Why Claude Desktop?
Claude Desktop is the definitive way to connect Customer.io to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 12 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.
- —
Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available
- —
Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface
- —
Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions
- —
Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network
Customer.io in Claude Desktop
Customer.io and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect Customer.io to Claude Desktop 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 Customer.io in Claude Desktop
The Customer.io 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 Claude Desktop 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
Customer.io for Claude Desktop
Every tool call from Claude Desktop to the Customer.io 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 Customer.io App API Key?
Log in to Customer.io, navigate to Settings > Account Settings > API Keys, and select the App API Keys tab to generate a new token.
Does it support EU regional accounts?
Yes! You can specify your region ('us' or 'eu') via the CUSTOMER_IO_REGION credential to ensure the agent connects to the correct data center.
Can I trigger a broadcast via AI?
Yes! Use the dispatch_broadcast tool with a specific broadcast ID. You can optionally provide JSON parameters for Liquid data injection.
How does Claude Desktop discover MCP tools?
When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
What happens if the MCP server is temporarily unavailable?
Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
Can I connect multiple MCP servers simultaneously?
Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
Is there a limit on the number of tools per server?
Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
Does Claude Desktop support Streamable HTTP transport?
Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.
Server not appearing after restart
Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
Authentication error
Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
Tools not showing in chat
Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.