Customer.io MCP Logo
Download the Customer.io MCP logo in PNG, JPG, WebP, and SVG formats. Free high-resolution brand assets for editorial, comparison, and educational use.
Download Customer.io MCP Logo
How to use this logo
The Customer.io MCP logo is a trademark of Customer.io MCP and is used here for identification and editorial purposes only. Toolradar does not claim ownership.
- Allowed: reviews, comparisons, news articles, educational content, integration directories.
- Check the Customer.io MCP official brand guidelines before commercial use, advertising, or merchandising.
- Do not modify the colors, proportions, or add effects unless the brand guidelines explicitly permit it.
About Customer.io MCP
Customer.io MCP is the official Model Context Protocol server for Customer.io, the lifecycle messaging and automation platform. It authenticates through OAuth against a workspace and exposes the Journeys and data pipeline surfaces as tools, so campaign work can be driven from an assistant rather than the web UI. The server covers audiences, messages and results. On audiences, an agent can inspect an individual customer profile with its attributes, event history and engagement, list segments, create segments from attribute and behavioral conditions, and add people to a manual segment in bulk. On messages, it can create, read, update and delete campaigns, broadcasts and transactional messages, and send a broadcast with personalization data attached. On results, it pulls campaign and broadcast metrics so an assistant can report on what a send actually did. Tools are grouped into read, write and delete categories, which lets an operator approve each class of access separately instead of granting everything at once. Lifecycle marketers and growth engineers are the intended users: building a segment from a behavioral definition, drafting and scheduling a broadcast, or debugging why a specific person did or did not receive a message. The write and delete tools act on live messaging infrastructure, so the category based permissions are worth using rather than skipping.
See full Customer.io MCP review on Toolradar