How do I get a Customer.io API Key?

Log in to your Customer.io workspace, navigate to **Settings > API Keys**, and you will find your Site ID and API Key there. You can create different keys for tracking and management purposes.

Can the agent trigger a campaign manually?

This integration currently focuses on identifying customers and monitoring campaign data. Triggering campaigns is typically done via behavioral events or within the Customer.io workflow builder.

Does the integration support SMS and Push notifications?

Yes, Customer.io is a multi-channel platform. The agent can monitor campaigns and broadcasts that include Email, SMS, Push, and Webhook actions.

Customer.io MCP Server for Claude Desktop 10 tools — connect in under 2 minutes

Name: Customer.io
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 10 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Customer.io and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "customerio": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* 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

About Customer.io MCP Server

Integrate Customer.io, the platform for sending personalized messages based on customer behavior, directly into your AI workflow. Manage your customer profiles, monitor automated campaigns, and track engagement metrics using natural language.

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 10 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

Customer Identification — Create or update customer profiles with behavioral attributes via the Identify API.
Campaign Monitoring — List automated campaigns and retrieve real-time performance and engagement metrics.
Broadcast & Newsletter Tracking — Track one-to-many broadcast messages and newsletter statuses.
Segment Oversight — Explore dynamic and manual customer segments to understand your audience composition.

The Customer.io MCP Server exposes 10 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Customer.io to Claude Desktop via MCP

Follow these steps to integrate the Customer.io MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Customer.io

Look for the 🔌 icon in the chat. your 10 tools are now available

Why Use Claude Desktop with the Customer.io MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Customer.io through the Model Context Protocol.

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 + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Customer.io MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Customer.io MCP Tools for Claude Desktop (10)

These 10 tools become available when you connect Customer.io to Claude Desktop via MCP:

get_campaign_performance

Resolves sent, opened, clicked, and converted counts. Interacts with the analytics and reporting engine. Get delivery and engagement metrics for a campaign

get_customer_details

Resolves custom attributes, device tokens, and segment memberships. Touches the granular profile and behavioral data boundary. Get full profile, attributes, and devices for a specific customer

get_engagement_summary

Resolves high-level engagement KPIs. Interacts with the global analytics boundary. Retrieve a high-level summary of campaign and broadcast performance

identify_customer

Resolves the identification status and profile state. Mutates the workspace identity database. Create or update a customer profile with attributes

list_automated_campaigns

Resolves campaign IDs, names, and trigger types. Interacts with the automation and messaging boundary. List all automated messaging campaigns

list_broadcast_messages

Resolves broadcast identifiers and scheduling metadata. Interacts with the bulk messaging boundary. List all one-to-many broadcast messages

list_customer_segments

Resolves segment IDs, types (manual/dynamic), and membership counts. Touches the audience segmentation and filtering boundary. List all dynamic and manual segments

list_customers

Resolves unique identifiers, email addresses, and last-seen timestamps. Interacts with the core identity and profile boundary. List all customers/people in your Customer.io workspace

list_newsletters

Resolves newsletter IDs and status. Touches the content distribution and newsletter management boundary. List all newsletter campaigns

search_customers_by_email

Resolves the associated customer identifiers. Touches the identity lookup and search boundary. Search for a customer profile by email address

Example Prompts for Customer.io in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Customer.io immediately.

"List all active automated campaigns in my workspace."

"Show me the performance metrics for the 'Welcome Sequence' campaign."

"Identify a new customer with ID 'user_789' and email 'new.user@example.com'."

Troubleshooting Customer.io MCP Server with Claude Desktop

Common issues when connecting Customer.io to Claude Desktop through the Vinkius, and how to resolve them.

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.

Customer.io + Claude Desktop FAQ

Common questions about integrating Customer.io MCP Server with Claude Desktop.

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.