Customer.io

@customer.io show me all segments in our workspace and how many people are in each one

Here are the segments currently configured in your Customer.io workspace: 'Active Trial Users' (1,247 members), 'Churned Last 30 Days' (89 members), 'High-Value Customers' (412 members), 'Onboarding Incomplete' (2,103 members), and 'Power Users' (156 members). Each segment reflects real-time membership based on your configured rules. This example illustrates the kind of overview you'd receive — actual segment names and counts will match your workspace configuration.

This example demonstrates read-only segment discovery. Requires API key with read access to segments. Membership counts are current at query time but may change as customer attributes update. Use this to audit segmentation strategy or identify which audiences are available for targeting in campaigns.

@customer.io what email messages did we send yesterday and what were the delivery rates

Yesterday your workspace sent 4 email messages: 'Weekly Product Update' (delivered to 8,421 of 8,500 recipients, 98.1% delivery rate), 'Cart Abandonment Reminder' (delivered to 1,203 of 1,250, 96.2%), 'Trial Ending Soon' (delivered to 445 of 450, 98.9%), and 'Welcome Series - Day 3' (delivered to 2,987 of 3,100, 96.4%). This example shows how the MCP surfaces message-level metrics — your actual results will include bounce reasons and engagement data for the specific time range you query.

This example uses the Get Messages tool with timestamp filtering. Requires API key with read access to message metrics. Results are paginated for workspaces with high message volume. Delivery rates shown here are illustrative — real queries return detailed bounce and engagement breakdowns you can analyze for deliverability issues.

@customer.io find everyone in the 'Churned Last 30 Days' segment and summarize common attributes that might explain why they left

The 'Churned Last 30 Days' segment contains 89 people. After retrieving their profiles, common patterns emerge: 67% had fewer than 3 logins in their final month, 54% never completed the onboarding checklist, 41% were on the free tier without upgrading, and 28% had support tickets that went unresolved for over 5 days. This example illustrates how the MCP can fetch segment membership and let the AI identify trends — your actual analysis will depend on which customer attributes you track in Customer.io.

This example chains Get Segments, Get Segment Details, and Get Segment Membership, then applies AI reasoning to the returned customer data. Requires API key with read access to people and segments. Segment membership queries are paginated, so large segments may take multiple requests. The AI's pattern analysis is only as good as the attributes you've instrumented in Customer.io.

When this MCP wins for campaign post-mortems

A 3-person growth team runs weekly email campaigns and needs to pull delivery stats into Slack for Friday retros. The Get Messages tool filters by timestamp and returns paginated metrics—open rates, bounces, deliveries—without logging into Customer.io's dashboard. This MCP is the right call if your team sends fewer than 10 campaigns a week and you're already using Switchy for cross-tool reporting. The API_KEY auth means anyone on the team can query last week's sends in under 30 seconds. If you're running 50+ campaigns a month or need real-time alerting, you'll hit rate limits and want a dedicated BI tool instead. For small teams doing weekly campaign reviews, this MCP turns a 10-minute dashboard hunt into a one-prompt pull.

When segment membership queries beat manual exports

A 5-person support team at a B2B SaaS company needs to verify which customers are in a 'churned-last-quarter' segment before sending a win-back offer. The Get Segment Membership tool pages through the list and surfaces email addresses without exporting a CSV or opening the Customer.io UI. This MCP works if you're auditing fewer than 20 segments a month and your compliance process lives in Switchy alongside Zendesk and Notion. The 14 tools cover segments, triggers, and webhooks, so you can cross-check who got what message. If your segments have 100k+ members or you need real-time sync to a CRM, the pagination will slow you down and you'll want a direct database connection. For quarterly audits or one-off segment checks, this MCP cuts the export-download-upload loop to zero.

When webhook and integration discovery saves debug time

A 2-person ops team at a startup troubleshoots why Stripe purchase events aren't triggering Customer.io campaigns. The Get Integrations and Get Workspace Webhooks tools list every configured integration and webhook endpoint in one query, surfacing stale URLs or missing API keys. This MCP is the right call if you manage fewer than 10 integrations and your debugging workflow already happens in Switchy with logs from Sentry and Datadog. The API_KEY auth means you don't need OAuth for a one-off health check. If you're managing 30+ integrations or need automated monitoring, you'll want a dedicated observability stack instead of manual queries. For small teams doing monthly integration audits or incident triage, this MCP turns a 20-minute UI hunt into a 2-minute prompt.