Customerio Journeys Track MCP server

Read from the package source without running it. The installed server may list more.

• add_customers_to_segment

  Add customers to a manual segment by their identifiers. You can add up to 1000 customers per request using their ID, email, or CIO ID.

• batch_entitieswrite action

  Submit multiple entity operations in a single request to create or modify people and objects. Combine different entity types (people, objects, deliveries) in one batch for efficient bulk processing.

• delete_customerwrite action

  Permanently remove a customer and all associated information from Customer.io. Note that customers recreated through other integration methods (such as the Javascript snippet) after deletion may need to be deleted again.

• get_account_region

  Retrieve your account's region and environment details. This endpoint returns the appropriate regional URL and environment ID for your Track API credentials, which you should use for all subsequent API requests.

• log_anonymous_event

  Log an event for an unidentified person using an anonymous identifier. Events can be associated with a person later when their identity is confirmed, enabling campaign triggers within 72 hours of the event timestamp.

• manage_entitywrite action

  Create, update, delete, or manage relationships for a person or object (such as a company or product) in Customer.io. Supports operations like identifying profiles, tracking events, managing devices, and merging duplicate person records.

• mark_delivery_unsubscribed

  Mark a person as unsubscribed from a specific email delivery. Use this endpoint with custom unsubscribe pages to record unsubscribe requests and trigger email_unsubscribed events for audience segmentation.

• merge_customers

  Merge two customer profiles by consolidating the secondary profile into the primary profile, then deleting the secondary. This operation is irreversible and requires the primary profile to already exist in Customer.io.

• register_device

  Register or update a device for a customer. Customers can maintain multiple devices (iOS and Android) on their profile.

• remove_customers_from_segmentwrite action

  Remove customers from a manual segment by their identifiers. This operation supports up to 1000 customer IDs per request and requires customers to have id attributes in your workspace.

• remove_devicewrite action

  Remove a device from a customer profile. Ensure you stop sending device data to Customer.io to prevent the device from being automatically re-added.

• report_metric

  Report email metrics from external channels or non-SDK integrations by associating events with a delivery ID from a Customer.io message. Use the CIO-Delivery-ID header value as the delivery_id to track opens, clicks, conversions, bounces, and other email events.

• submit_formwrite action

  Submit a form response and create or update the respondent in Customer.io. Form submissions are associated with a form connection; if the form_id is unrecognized, a new form connection is automatically created.

• suppress_customer

  Permanently delete a customer profile and suppress their identifier(s) to prevent re-addition to the workspace. All future API calls referencing the suppressed identifier are ignored. This action cannot be undone and should be used primarily for GDPR/CCPA compliance requests.

• track_customer_event

  Record a behavioral event (page view, screen view, or custom event) for a customer to enable campaign triggering and audience segmentation. Events with timestamps within the past 72 hours can activate campaigns.

• unsuppress_customer

  Reactivate a suppressed customer profile to make their identifier available for new profile creation. Unsuppressing does not restore the previous profile history; it only makes the identifier usable again.

• upsert_customer

  Add a new customer or update an existing customer's profile. This operation handles identifier merging, profile creation, and attribute updates based on the identifiers provided in the path and request body.

• Code scan5 source files scanned25/25
• –Live reliabilityno gateway calls yet and no remote to proben/a
• –Tool poisoningtools not inspected (local package is not executed); not countedn/a
• Auth qualitylocal package, no credentials required12/15
• Maintenancelast push 138 days ago8/15
• Maintainer identityregistry namespace matches repository owner7/10

Safety score

80/100

higher than 60% of 48,255 servers

Tools

17

the typical server has 7

Tools that change things

35%

typical: 0%. Fewer write tools means less an agent can break

GitHub stars

31

more than 92% of 28,688 servers

Downloads a week

161

more than 72% of 12,191 servers with a package

Customerio Journeys Track: common questions

Is Customerio Journeys Track MCP server safe?

Mostly: it is graded B (80/100). Read the Customerio Journeys Track safety report

How do I install Customerio Journeys Track?

It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.

Does Customerio Journeys Track need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Customerio Journeys Track maintained?

The last commit was 176 days ago (2026-05-12). The latest release is v1.0.5.

How does Customerio Journeys Track compare with other MCP servers?

safety score 80/100 (higher than 60% of 48,255 servers); tools 17 (the typical server has 7); tools that change things 35% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.