customerio
Server Details
Query people, segments, campaigns, and message deliveries; send transactional email or broadcasts.
- Status
- Healthy
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- m190/usefulapi-mcp
- GitHub Stars
- 0
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Tool Definition Quality
Score is being calculated. Check back soon.
Available Tools
13 toolscustomerio_get_campaignGet campaignRead-onlyInspect
Get a single campaign by id. App API: GET /v1/campaigns/{campaign_id}.
| Name | Required | Description | Default |
|---|---|---|---|
| campaign_id | Yes | Campaign id. |
customerio_get_campaign_metricsGet campaign metricsRead-onlyInspect
Get delivery/engagement metrics for a campaign over time. App API: GET /v1/campaigns/{campaign_id}/metrics.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Metric type filter (e.g. email, push, sms). | |
| steps | No | Number of periods to return. | |
| period | No | Bucket size. Default days. | |
| campaign_id | Yes | Campaign id. |
customerio_get_customer_attributesGet customer attributesRead-onlyInspect
Get a single person's attributes (profile fields). App API: GET /v1/customers/{customer_id}/attributes.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The person's id (or cio_id / email, per your identifier setup). |
customerio_get_customer_messagesGet customer messagesRead-onlyInspect
List messages (deliveries) sent to a single person. App API: GET /v1/customers/{customer_id}/messages.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max messages to return. | |
| start | No | Pagination cursor from a previous response's `next`. | |
| customer_id | Yes | The person's id. |
customerio_get_customer_segmentsGet customer segmentsRead-onlyInspect
List the segments a single person belongs to. App API: GET /v1/customers/{customer_id}/segments.
| Name | Required | Description | Default |
|---|---|---|---|
| customer_id | Yes | The person's id. |
customerio_list_campaignsList campaignsRead-onlyInspect
List all campaigns in the workspace. App API: GET /v1/campaigns.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
customerio_list_collectionsList collectionsRead-onlyInspect
List reusable data collections in the workspace. App API: GET /v1/collections.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
customerio_list_exportsList exportsRead-onlyInspect
List data exports in the workspace. App API: GET /v1/exports.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
customerio_list_messagesList messagesRead-onlyInspect
List sent messages (deliveries) across the workspace, filterable by type/campaign/newsletter. App API: GET /v1/messages.
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | Message type filter, e.g. email | push | sms | in_app | webhook | slack | twilio. | |
| limit | No | Max messages to return. | |
| start | No | Pagination cursor from a previous response's `next`. | |
| drafts | No | Include drafts. | |
| campaign_id | No | Filter to a specific campaign. | |
| newsletter_id | No | Filter to a specific newsletter. |
customerio_list_segmentsList segmentsRead-onlyInspect
List all segments in the workspace (id + name + type). App API: GET /v1/segments.
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
customerio_search_customersSearch customersRead-onlyInspect
Search/list people by a Customer.io filter (segment or attribute conditions). e.g. filter={"segment":{"id":7}} or {"and":[...]}. App API: POST /v1/customers.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max people to return. | |
| start | No | Pagination cursor from a previous response's `next`. | |
| filter | Yes | Customer.io filter object, e.g. {"segment":{"id":7}} or {"and":[{"attribute":{"field":"email","operator":"exists"}}]}. |
customerio_send_transactional_emailSend transactional emailDestructiveInspect
⚠️ SENDS A REAL EMAIL. Send a transactional email using a transactional message template. Delivers immediately to the to recipient. App API: POST /v1/send/email.
| Name | Required | Description | Default |
|---|---|---|---|
| to | Yes | Recipient email address. | |
| body | No | Override the email body. | |
| from | No | Override the sender address. | |
| subject | No | Override the subject line. | |
| identifiers | Yes | Person identifiers, e.g. {"id":"..."} or {"email":"..."}. | |
| message_data | No | Template variables (liquid) to interpolate into the message. | |
| send_to_unsubscribed | No | If true, send even to unsubscribed recipients. | |
| transactional_message_id | Yes | The transactional message template id (or trigger name). | |
| disable_message_retention | No | If true, don't retain the message body. |
customerio_trigger_broadcastTrigger broadcastDestructiveInspect
⚠️ SENDS TO REAL RECIPIENTS. Trigger an API-triggered broadcast, delivering to the resolved recipient set. App API: POST /v1/send/broadcast (posts to /v1/campaigns/{broadcast_id}/triggers).
| Name | Required | Description | Default |
|---|---|---|---|
| data | No | Liquid variables available to the broadcast templates. | |
| recipients | No | Recipient filter object (overrides the broadcast's configured audience). | |
| broadcast_id | Yes | The API-triggered broadcast id. | |
| id_ignore_missing | No | Skip recipients missing an id instead of erroring. | |
| email_add_duplicates | No | Allow duplicate email recipients. | |
| email_ignore_missing | No | Skip recipients missing an email instead of erroring. |
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!