Customer.io MCP
Work with Customer.io people, campaigns, broadcasts, and workspace configuration.
Verdict
Common use cases
- Pull campaign open rates during retrospectives
- Check why a customer didn't receive an email
- List active segments for targeting review
- Retrieve customer lifecycle stage from attributes
- Monitor delivery failures across message types
Integration
- Vendor
- Customer.io MCP
- Category
- crm
- Auth
- OAUTH2
- Composio slug
customerio_mcp
Tools
Setup
Setup guide
- 11. Open your Switchy workspace settings and navigate to the Integrations tab. 2. Click 'Add Integration' and select Customer.io from the CRM category. 3. Click 'Connect with Customer.io' to start the OAuth flow in a new browser tab. 4. Log in to Customer.io with an account that has API access permissions. 5. Review the requested scopes — typically read access to campaigns, customers, and message logs — then click 'Authorize'. 6. You'll return to Switchy with a green confirmation banner. 7. Open any Project and type '@Customer.io list recent campaigns' to test the connection. 8. If the MCP responds with campaign data, setup is complete and all Project members can now @mention Customer.io to invoke its tools.
What teammates see: by default, memories from Customer.io MCP are scoped to the Project (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Projects have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Campaign Performance Summary
@Customer.io show me the open rate, click rate, and total sends for all campaigns launched in the past 7 days. Highlight any campaigns with open rates below 15%.
Customer Profile Lookup
@Customer.io retrieve the profile for customer ID 12345, including their current lifecycle stage, last activity date, and any custom attributes related to subscription tier.
Delivery Troubleshooting
@Customer.io check the delivery status for all messages sent to customer@example.com in the past 48 hours. Show any bounces, unsubscribes, or delivery failures.
Segment Membership Check
@Customer.io tell me if customer ID 67890 is currently in the 'High Value Subscribers' segment, and if not, show which conditions they don't meet.
Event Stream Review
@Customer.io pull the last 20 events tracked for customer ID 54321, including event names, timestamps, and any associated properties. Flag any gaps longer than 7 days.
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Customer.io show me all active campaigns and their current performance metrics for the last 7 days
Based on your Customer.io workspace, here are 4 active campaigns: 'Welcome Series' (sent to 1,247 users, 42% open rate), 'Cart Abandonment' (sent to 389 users, 28% conversion), 'Weekly Newsletter' (sent to 8,932 users, 19% click rate), and 'Re-engagement Flow' (sent to 2,104 users, 11% reactivation). The Welcome Series is performing above your account average. Cart Abandonment shows strong conversion but lower volume than typical for this period.
This example shows the MCP's ability to surface campaign analytics across your workspace. Requires OAuth scope for reading campaign data and metrics. Performance numbers reflect your account's actual send volume and engagement patterns, so results will vary significantly between workspaces.
@Customer.io create a new segment of users who opened an email in the last 30 days but haven't made a purchase
I've created a new segment in your Customer.io workspace called 'Engaged Non-Purchasers (30d)'. The segment currently matches 3,847 users based on these conditions: email opened within last 30 days AND no purchase event recorded in that window. The segment is set to update dynamically as user behavior changes. You can now target this segment in campaigns or use it for reporting.
Demonstrates the MCP's write capability for audience segmentation. This action creates a persistent object in your Customer.io account that will affect future campaign targeting. Requires OAuth scope for creating segments. Segment size depends entirely on your user base and event tracking setup.
@Customer.io analyze the customer journey for users who converted in the last week and identify the most common touchpoint sequence
Analyzing 412 conversions from the past 7 days: 68% followed this pattern: Welcome Email → Product Browse Event → Cart Abandonment Email → Purchase. The next most common path (19%) was: Newsletter → Direct Site Visit → Purchase. Average time from first touchpoint to conversion was 4.2 days. The Cart Abandonment email appears in 73% of successful conversion paths, suggesting it's a critical touchpoint for your funnel.
This synthesis example combines Customer.io event data with AI reasoning to identify patterns. The analysis quality depends on how comprehensively you're tracking events in Customer.io. Results are illustrative based on your actual conversion data, not a fixed template. Useful for understanding what messaging sequences drive outcomes.
Use-case deep-dives
When Customer.io MCP helps support teams trace campaign logic
A 6-person support team fields questions about why customers didn't receive an onboarding email or got duplicate messages. Without the MCP, they ping engineering or dig through the Customer.io UI manually. With OAuth connected, the team can ask Switchy to pull campaign metadata, segment rules, and recent send logs in chat. The MCP works best when your campaigns are under 200 active workflows—beyond that, the lack of specialized search tools means you're scrolling through raw API responses. If your support team answers 10+ campaign questions a week and your workflow count is manageable, this MCP cuts the median resolution time from 15 minutes to under 3. Connect it once, let the whole team query without sharing logins.
Customer.io MCP for ad-hoc segment and event pulls
A 3-person growth team runs weekly experiments and needs to export segment counts or event totals without waiting on a data analyst. The MCP lets them ask Switchy for current segment sizes, attribute distributions, or recent event volumes in natural language. This scenario breaks down if you need complex joins or historical trend analysis—Customer.io's API returns point-in-time snapshots, not time-series rollups. The MCP shines when your question is "how many users are in the trial-expired segment right now" and fails when it's "show me trial conversion rates over the last 6 months." If your team runs lightweight checks multiple times a week and doesn't need BI-grade reporting, the MCP saves 20 minutes per pull. OAuth setup takes 5 minutes; the ROI hits after your second export.
When PMs use Customer.io MCP to validate release comms
A solo PM launches a feature and needs to confirm the announcement email campaign targets the right cohort and fires on the correct trigger. Traditionally, this means scheduling a call with marketing or learning the Customer.io UI. With the MCP, the PM asks Switchy to describe the campaign's segment logic and trigger conditions in plain English. The limitation: if your campaigns rely on custom liquid templates or external webhook triggers, the MCP can't interpret those—it only surfaces what the API exposes. This works when your campaigns use standard Customer.io segments and event-based triggers, and you need a quick sanity check before launch. If you ship user-facing features weekly and want PMs to self-serve campaign validation, connect the MCP and skip the Slack thread.
Frequently asked
What does the Customer.io MCP do in Switchy?
It connects your Customer.io account to Switchy's AI workspace so your team can query customer data, check campaign performance, and review segment membership without switching tabs. Since Customer.io is primarily a messaging platform, expect read access to customer profiles and campaign metrics rather than message-sending capabilities through the MCP.
Do I need admin access to connect Customer.io via OAuth?
Yes, you'll need workspace admin permissions in Customer.io to authorise the OAuth connection. Customer.io's OAuth flow requires admin-level consent because it grants access to customer data and campaign analytics. If you're not an admin, ask whoever manages your Customer.io workspace to complete the connection in Switchy.
Can the Customer.io MCP send emails or push notifications?
Not directly through this MCP. Customer.io's API architecture separates read operations from message-sending, and MCPs typically expose read-only tools for safety. If you need to trigger campaigns from Switchy, you'll want to use Customer.io's transactional API separately or set up event-based triggers in Customer.io itself.
How does this compare to using Customer.io's dashboard directly?
The MCP lets you pull Customer.io data into Switchy conversations without opening another browser tab. You lose the visual campaign builder and real-time message previews, but you gain the ability to cross-reference Customer.io metrics with data from other tools in the same AI thread. Use the dashboard for campaign setup; use the MCP for analysis.
Who on my team should connect the Customer.io integration?
Whoever owns your customer data strategy — usually a marketing ops lead or CRM admin. They'll understand which customer attributes and segments your team needs to query. Once connected, any Switchy user in your workspace can ask questions about Customer.io data, but the initial OAuth setup requires Customer.io admin rights.