Connect Customer.io to Microsoft Copilot via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Customer.io, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Customer.io + Microsoft Copilot

Let your AI work with Customer.io: look up people, their attributes, segments, activity and messages, review automations, broadcasts and one-time sends with their metrics, and send transactional emails or trigger broadcasts after you confirm.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

CUSTOMERIO_API_URL, CUSTOMERIO_APP_API_KEY

Step 1 — Get credentials

Setting up takes about 3 minutes. You need a Customer.io user who can create an App API key, and you need to know whether your account is hosted in the US or the EU.

1. In Customer.io, open Settings → Account Settings → API Credentials → App API Keys (fly.customer.io/settings/api_credentials) and click Create App API Key. Pick the workspace and the access the key gets: full access, or read-only plus sending if the AI should only read and send.
2. Copy the key right away: Customer.io shows it only once. Paste it into CUSTOMERIO_APP_API_KEY as shown, without a Bearer prefix. It is an App API key, not a Track API key.
3. Set CUSTOMERIO_API_URL to your account's data center: https://api.customer.io for US accounts, https://api-eu.customer.io for EU accounts, without /v1 or any other path. The region is fixed when the account is created.
4. Install the connector and start with customer_io_list_workspaces: it checks the key and shows the workspace with its people and message counts.

One key for the whole workspace: the App API key acts for its workspace, not for one person. Whoever uses this connector sees every person, segment and message the key can read, so share the MCP server only with people allowed to see that.

What it covers: people (find them by email, or search by segment membership and attribute values), their attributes, segments, activity of the last 30 days and the messages sent to them; segments with their conditions, live counts and members; automations, which the Customer.io API calls campaigns, with their message metrics; API-triggered broadcasts and one-time sends (newsletters in the API) with their metrics; deliveries and activity across the workspace; and the transactional message templates.

Sends wait for your yes: only two tools send, everything else reads.

• customer_io_send_transactional_email sends one real email (receipts, password resets, notifications) to up to 15 addresses in to, cc and bcc, from a transactional template or with your own subject and body. The AI shows you the recipient, the subject and the content first.
• customer_io_trigger_broadcast sends to many people at once. The AI first shows the broadcast, the size of the audience (customer_io_get_segment_customer_count) and the data, and triggers it only after an explicit "yes, send". It then follows progress with customer_io_get_broadcast_trigger.

Track API not included: identifying people, tracking events and deleting people go through Customer.io's Track API, which uses a different credential (Site ID and Track API key). This connector does not use it, so it cannot change profiles or delete anyone.

Limits: the App API allows about 10 requests a second. Transactional sends share a soft limit of 3,000 requests per 3 seconds, and a broadcast can be triggered at most once every 10 seconds. Long lists come in pages, and the AI keeps reading until the last one. Timestamps are Unix seconds.

Common errors: 401 means the App API key is wrong or was deleted, or the account lives in the other region; check CUSTOMERIO_API_URL. 403: the key's access does not include this action, for example a read-only key used to send. 404: the id does not exist in this workspace. 400 or 422: a parameter or the search filter is invalid; the error names it. 429: a rate limit is reached; wait and try again.

The connector does not use the Track API or the Pipelines API, run exports or imports, manage collections, snippets, reporting webhooks or ESP suppressions, or change the content of automations and broadcasts.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Microsoft Copilot

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Microsoft Copilot uses MCP servers through agents built in Copilot Studio: you add AnythingMCP to an agent as a tool, then publish the agent to Microsoft 365 Copilot and Teams. Copilot Studio connects from Microsoft's cloud over Streamable HTTP, which AnythingMCP supports.

1. In Copilot Studio, open your agent (or create one), go to Tools and choose Add a tool → New tool → Model Context Protocol.
2. Enter a Server name (for example AnythingMCP), a Server description that says what the connector does, and the Server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID. Copilot Studio uses the description to decide when to call the server.
3. Under authentication, choose API key, set Type to Header and the header name to X-API-Key, then select Create.
4. In Add tool, choose Create a new connection, paste an MCP API key from AnythingMCP (MCP Servers → your server → API keys) and select Add to agent.
5. Try it in the agent's Test pane: ask for something that needs the Customer.io tools.
6. Select Publish, then Channels → Microsoft 365 and Microsoft Teams, keep Make agent available in Microsoft Copilot selected and choose Add channel. See agent in Teams installs it for you; in Microsoft 365 Copilot, type @ and pick the agent.

Prefer per-user sign-in? Choose OAuth 2.0 → Dynamic discovery instead of an API key: each user then signs in to AnythingMCP the first time the agent calls it.

Self-hosting? Use your instance's public HTTPS address instead of https://cloud.anythingmcp.com. Copilot Studio connects from Microsoft's cloud, so localhost does not work.

Available tools

Example prompts

• "Find [email protected] in Customer.io and show me her attributes, her segments and the last emails we sent her."
• "How did our Onboarding automation perform over the last 30 days: sent, delivered, opened, clicked and unsubscribed?"
• "How many people are in the Trial ending segment right now, and which of them are on the pro plan?"
• "Trigger the Product update broadcast, but show me who will receive it and how many people that is before you send."

FAQ

Which Copilot is this for? Microsoft 365 Copilot at work, through agents built in Copilot Studio. The Microsoft Copilot app for personal accounts has no option to add your own MCP server.

What do I need? A work account with access to Copilot Studio (a license or a trial) to build the agent. People who use it in Microsoft 365 Copilot or Teams need access to the agent: share it with them, or ask an admin to publish it to the organization. If your organization applies data policies to Power Platform connectors, they cover MCP servers too.

The agent doesn't call the tools. Check that the header name is exactly X-API-Key and that the key belongs to the same MCP server as the URL, and make the server description specific: Copilot Studio uses it to decide when to call the server. Publish the agent again after each change; in an open chat, type "start over" to get the new version.

Next steps

• Connector landing page
• Connect to Claude
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse