Skip to directory

About Customer.io MCP

Customer.io's hosted MCP connects an authenticated workspace to tools for reading and managing Journeys and CDP Data Pipelines resources, with separately granted read, write, live-write, sensitive-data, and configuration scopes.

What you can use it for

  • Inspect workspaces, campaigns, segments, profiles, content, and delivery metrics
  • Discover API schemas and perform scoped reads or changes
  • Work with integrations, webhooks, channel settings, and messaging configuration
  • Get Customer.io-maintained task skills and workflow guidance
Connection and setup
Hosting
Remote, hosted by Customer.io
Transport
Streamable HTTP
Endpoint
https://mcp.customer.io/mcp
Authentication
OAuth. Each user authenticates with their own Customer.io account and selects workspaces/scopes. Account admin must enable MCP in Settings > AI. Default scope is read; additional scopes are independently granted.

Requirements

  • Customer.io workspace and user access
  • Account admin enables MCP
  • MCP-compatible client and browser for OAuth
  • Admin enablement is required for sensitive-data or live-data access

Setup steps

  1. Ask an account admin to enable Customer.io MCP in Settings > AI.
  2. Add the official Customer.io connector using the client-specific setup guide; endpoint is selected by region for direct MCP clients.
  3. Start OAuth in the client, sign in, choose the workspace, and grant only required scopes.
  4. Use read scope by default. Request read:sensitive, write, write:live, or configure only when the task requires it and account policy permits.
  5. Verify with a read-only workspace listing. Review dry-run previews and require approval for writes/deletes/live actions.
Tools 8

Eight exact tools are listed in Customer.io’s current official reference. Tool scope and live/sensitive-data access are account and OAuth permission dependent.

  • cio_prime

    Load Customer.io API reference for a task.

    01
  • cio_schema

    Discover API endpoints and inspect their parameters.

    02
  • cio_read_api

    Perform authenticated GET requests for reads, filtering, pagination, and dry-run previews.

    03
  • cio_write_api

    Perform authenticated POST, PUT, and PATCH requests with dry-run previews.

    04
  • cio_delete_api

    Perform authenticated DELETE requests with dry-run previews.

    05
  • cio_skills_list

    List Customer.io-maintained workflow skills.

    06
  • cio_skills_read

    Read a specific workflow skill.

    07
  • cio_auth_status

    Show authentication state and accessible workspaces.

    08
Limitations and notes
  • Account admins alone can enable/disable MCP and control sensitive/live-data access.
  • Tool permissions are bounded by the user's existing Customer.io role and selected OAuth scopes.
  • write, write:live, and configure are separate scopes; live changes may require an administrator setting.
  • MCP tool calls may expose workspace/customer information to the connected AI provider; use organization-approved clients.
  • Tools may need client refresh/reconnect after server updates.
Original sources
  • official documentation

    Current official documentation enumerates the same eight tools as the catalog and documents US/EU endpoints, OAuth, workspace scopes, and read/write/delete separation. Account admins must enable MCP; live-data and sensitive-data scopes require additional account controls.

  • official tool reference

    Current official documentation enumerates the same eight tools as the catalog and documents US/EU endpoints, OAuth, workspace scopes, and read/write/delete separation. Account admins must enable MCP; live-data and sensitive-data scopes require additional account controls.

Documentation checked 2026-10-28T13:19:36Z. Connection has not been runtime tested.

Similar tools