Included because its regional hosted MCP exposes the Journeys UI and CDP Data Pipelines APIs while separating reads, writes, deletes, live operations, configuration, and sensitive profile access into controllable boundaries.
Concrete capability record
A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.
Accounts and workspaces, profiles and sensitive attributes, events, segments, campaigns and automations, newsletters and other one-time sends, templates and Design Studio content, delivery metrics, subscriptions and suppressions, integrations, webhooks, channels, sources, pipelines, API schemas, sessions, and agent skills.
Discover Journeys UI and CDP Data Pipelines endpoints and parameters, inspect workspace resources and delivery metrics, and preview authenticated GET requests with filtering and pagination.
Create and edit resources with POST, PUT, and PATCH; remove resources with a separate DELETE tool; and, only with distinct authorization, change live data, send messages, manage subscriptions or suppressions, and configure integrations or channels.
Each user authenticates through Customer.io OAuth, chooses workspaces, and grants MCP scopes that cannot exceed that user's Customer.io role. Connections default to read; read:sensitive, write, write:live, and configure are separately authorized.
Account admins can disable MCP immediately and independently allow live-data edits or sensitive profile access; both elevated account settings are off by default. Clients can also approve read, write, and delete tools separately, and users can revoke their own sessions.
The service has separate US and EU endpoints. Terminal-based agents are directed to the Customer.io CLI instead, and MCP clients may need a reconnect or refresh to discover newly added tools.
Agent access
Support: Official MCP server
Read scope: Read the full Journeys UI and CDP Data Pipelines API surfaces available to the connected user, with endpoint discovery, filtering, pagination, and dry-run previews; sensitive profile attributes require separate access.
Write scope: Create, update, and delete permitted API resources with dry-run support; sending, subscriptions, suppressions, live-resource changes, and workspace configuration require additional independent scopes and account settings.
Authentication: Per-user Customer.io OAuth to the regional hosted endpoint, with user-managed connected-client sessions and workspace selection during use.
Approval boundary: Use dry-run output and require explicit confirmation for the target workspace, audience or profile set, payload, and scope before DELETE, write:live, configure, send, subscription, suppression, or sensitive-data operations.
Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.
Editorial assessment
A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.
Proposed customer-shaped experiences
The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Customer.io ships them.
Evidence and dates
“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.
Customer.io documents regional hosted endpoints and tools spanning the full Journeys UI API and CDP Data Pipelines API.
Targeted first-party MCP/agent-role review; broader API inventory retained
First-party API reference or API overview recorded for this platform.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party developer documentation or platform overview.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party product homepage used to confirm product identity and current positioning.
Inventory source: structurally normalized; content was not individually reopened in this pass.
First-party webhook, event, SDK, embedded-app, or extension documentation.
Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.
Tied to cited first-party evidence reviewed for this profile.
Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.
System role, maturity interpretation, and architectural boundary.
Interface patterns and compositions—not vendor product claims.
