Update to Customer.io

{
  "name": "customerio",
  "description": "Customer.io MCP bootstrap. Use for Customer.io, Journeys, CDP Pipelines, Design Studio, sandbox testing, app integration, SDK setup, transactional messaging, sources, destinations, identify/track events, and Customer.io workspace errors.\n",
  "included_files": [],
  "skill_md_contents": "---\nname: customerio\ndescription: >\n  Customer.io MCP bootstrap. Use for Customer.io, Journeys, CDP Pipelines,\n  Design Studio, sandbox testing, app integration, SDK setup, transactional\n  messaging, sources, destinations, identify/track events, and Customer.io\n  workspace errors.\n---\n\n# Customer.io\n\nUse the official Customer.io MCP server bundled with this plugin, then drive the workspace with its live tools and hosted skills.\n\n## Connect\n\n1. Confirm the `customerio` MCP server is enabled and complete Customer.io OAuth.\n2. Select the workspaces and minimum permission scopes needed for the task.\n3. The plugin uses the Universal `mcp.customer.io` entry point for both US and EU accounts. OAuth identifies the selected account's data center, and Customer.io routes EU requests to `mcp-eu.customer.io`; do not ask the user to choose a region manually.\n4. Do not paste personal MCP URLs, API keys, or service-account tokens into plugin files.\n\n## First calls\n\nCall `cio_prime` before other Customer.io tools. It returns the current rules for schema lookup, pagination, dry-run writes, and hosted skill discovery.\n\nThen use:\n\n- `cio_auth_status` when authentication or workspace access is unclear.\n- `cio_schema` to discover endpoints. Never guess paths or field names.\n- `cio_skills_list` and `cio_skills_read` for task-specific workflows.\n- `cio_read_api` for GET requests.\n- `cio_write_api` and `cio_delete_api` with `dry_run: true` before execution.\n\n## Route to live skills\n\n| Need | Read with `cio_skills_read` |\n| --- | --- |\n| Builder, SDK, sandbox, first send, go-live | `cio` |\n| Automations, campaigns, broadcasts, profiles, segments, messaging | `fly-api` |\n| Design Studio emails, components, global styles, publishing | `design-studio` |\n| CDP sources, destinations, reverse ETL, identify/track | `cdp-api` |\n| Analysis, campaign review, goals, Liquid | `recipes` |\n\nPrefer the hosted skills over copied playbooks so instructions stay current with Customer.io.\n\n## Terminology and safety\n\n- Automations are the `campaigns` API resource.\n- Profiles are the `customers` API resource.\n- Dry-run every write and delete before executing it.\n- Do not embed service-account tokens (`sa_live_...`) in application code.\n- Use CDP source write keys for SDK identify/track/page/screen calls.\n- Use workspace-scoped App API keys for backend transactional sends.\n- Do not return raw customer PII unless the user explicitly requests it.\n"
}