How to integrate Customer.io MCP with Atomic Agent

Connect Atomic Agent to Customer.io MCP. Add user to onboarding campaign now, create broadcast for new feature announcement, and more using natural language, with authentication handled for you.

Customer.io MCP logoCustomer.io MCP
Dcr Oauth

Customer.io MCP is a behavioral messaging platform for managing people, campaigns, broadcasts, and workspace configuration. Use it to automate targeted lifecycle messaging, personalize communications, and orchestrate campaigns at scale.

8 Tools

Introduction

Atomic Agent is an open-source AI agent that runs on your machine and supports local models through llama.cpp. Connect it to 1,500+ apps through Composio, including Customer.io.

This guide uses Atomic Agent's built-in Composio integration. You need Atomic Agent v0.5.6 or later, your own Composio API key, and a Customer.io account. See the Atomic Agent documentation for installation instructions.

Also integrate Customer.io MCP with

How Atomic Agent connects to Customer.io

Atomic Agent connects to Composio's Tool Router over Streamable HTTP MCP. It discovers the tools needed for your request, and Composio handles account authentication.

Execution and account-connection tools follow Atomic Agent's configured approval policy. Review any approval prompt before allowing an action on your connected account.

Connect Customer.io to Atomic Agent

  1. Sign up or sign in to the Composio dashboard. Copy your API key.
  2. In Atomic Agent, open the Integrations tab and select Composio. Select API key, press e, paste the key, and press Enter. The tools become available immediately, without a restart.
  3. Ask Atomic Agent to do something in Customer.io. It searches Composio for the right tool.
  4. On first use, open the sign-in link returned in the chat. Connect your Customer.io account, then return to Atomic Agent to continue.

Headless setup

Add the following line to ~/.atomic-agent/.env, replacing YOUR_COMPOSIO_API_KEY with your key. Start Atomic Agent after saving the file.

bash
COMPOSIO_API_KEY=YOUR_COMPOSIO_API_KEY

What is the Customer.io MCP server, and what's possible with it?

The Customer.io MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Customer.io account. It provides structured and secure access to your people, campaigns, broadcasts, and workspace configuration, so your agent can read customer data, manage campaigns, update broadcasts, adjust workspace settings, and remove resources on your behalf.

  • People management: Have your agent read and update people in Customer.io to keep customer information current.
  • Campaign operations: Let the agent review, create, and update campaigns based on your instructions.
  • Broadcast management: Direct your agent to inspect, create, or modify broadcasts for your messaging work.
  • Workspace configuration: Instruct your agent to read and update supported Customer.io workspace settings.
  • Guided tasks and cleanup: Have your agent consult Customer.io task instructions, check the active authentication state, and delete supported resources you no longer need.

Use Customer.io from Atomic Agent

With your account connected, ask Atomic Agent to work with Customer.io in natural language. You can connect more apps through the same Composio integration as you need them.

Visit the Atomic Agent website or inspect the Atomic Agent source code.

Troubleshooting

Why is my API key rejected?

Copy the key directly from the Composio dashboard. Atomic Agent requires ASCII characters because it sends the key in an HTTP header. Remove any extra characters introduced when copying.

Why are Composio tools unavailable after saving a key?

Check that you use Atomic Agent v0.5.6 or later and that Composio is enabled in your configuration. A "composio": { "enabled": false } setting disables the integration while keeping the saved key on disk.

Does Composio have a free plan?

The Hobby plan includes 100,000 tool calls per month. Composio-managed OAuth apps have a lower included allowance. See Composio pricing for the current limits that apply to your connection.

TOOLS

Supported Tools

Every Customer.io MCP action and event your agent gets out of the box.

Cio auth status

Show the active authentication state.

Cio delete api

Delete a resource via the Customer.

Cio prime

Print LLM-ready instructions for using the Customer.

Cio read api

Read from the Customer.

Cio schema

Introspect the Customer.

Cio skills list

List available agent skills — task-specific instruction manuals maintained by Customer.

Cio skills read

Read the full content of a specific agent skill.

Cio write api

Write to the Customer.

FAQ

Frequently asked questions

With a standalone Customer.io MCP server, the agents and LLMs can only access a fixed set of Customer.io tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Customer.io and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. Atomic Agent fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Customer.io tools.

Yes, absolutely. You can configure which Customer.io scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Customer.io data and credentials are handled as safely as possible.

Start with Customer.io MCP.It takes 30 seconds.

Managed auth, hosted MCP servers, and every Customer.io MCP tool your agent needs.Free to start.

Start building