How do I get a Customer.io API Key?

Log in to your Customer.io workspace, navigate to **Settings > API Keys**, and you will find your Site ID and API Key there. You can create different keys for tracking and management purposes.

Can the agent trigger a campaign manually?

This integration currently focuses on identifying customers and monitoring campaign data. Triggering campaigns is typically done via behavioral events or within the Customer.io workflow builder.

Does the integration support SMS and Push notifications?

Yes, Customer.io is a multi-channel platform. The agent can monitor campaigns and broadcasts that include Email, SMS, Push, and Webhook actions.

Customer.io MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Customer.io
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Customer.io and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "customerio": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Customer.io MCP Server

Integrate Customer.io, the platform for sending personalized messages based on customer behavior, directly into your AI workflow. Manage your customer profiles, monitor automated campaigns, and track engagement metrics using natural language.

GitHub Copilot Agent mode brings Customer.io data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

What you can do

Customer Identification — Create or update customer profiles with behavioral attributes via the Identify API.
Campaign Monitoring — List automated campaigns and retrieve real-time performance and engagement metrics.
Broadcast & Newsletter Tracking — Track one-to-many broadcast messages and newsletter statuses.
Segment Oversight — Explore dynamic and manual customer segments to understand your audience composition.

The Customer.io MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Customer.io to VS Code Copilot via MCP

Follow these steps to integrate the Customer.io MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Customer.io

Ask Copilot: "Using Customer.io, help me...". 10 tools available

Why Use VS Code Copilot with the Customer.io MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Customer.io through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Customer.io + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Customer.io MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Customer.io MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Customer.io to VS Code Copilot via MCP:

get_campaign_performance

Resolves sent, opened, clicked, and converted counts. Interacts with the analytics and reporting engine. Get delivery and engagement metrics for a campaign

get_customer_details

Resolves custom attributes, device tokens, and segment memberships. Touches the granular profile and behavioral data boundary. Get full profile, attributes, and devices for a specific customer

get_engagement_summary

Resolves high-level engagement KPIs. Interacts with the global analytics boundary. Retrieve a high-level summary of campaign and broadcast performance

identify_customer

Resolves the identification status and profile state. Mutates the workspace identity database. Create or update a customer profile with attributes

list_automated_campaigns

Resolves campaign IDs, names, and trigger types. Interacts with the automation and messaging boundary. List all automated messaging campaigns

list_broadcast_messages

Resolves broadcast identifiers and scheduling metadata. Interacts with the bulk messaging boundary. List all one-to-many broadcast messages

list_customer_segments

Resolves segment IDs, types (manual/dynamic), and membership counts. Touches the audience segmentation and filtering boundary. List all dynamic and manual segments

list_customers

Resolves unique identifiers, email addresses, and last-seen timestamps. Interacts with the core identity and profile boundary. List all customers/people in your Customer.io workspace

list_newsletters

Resolves newsletter IDs and status. Touches the content distribution and newsletter management boundary. List all newsletter campaigns

search_customers_by_email

Resolves the associated customer identifiers. Touches the identity lookup and search boundary. Search for a customer profile by email address

Example Prompts for Customer.io in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with Customer.io immediately.

"List all active automated campaigns in my workspace."

"Show me the performance metrics for the 'Welcome Sequence' campaign."

"Identify a new customer with ID 'user_789' and email 'new.user@example.com'."

Troubleshooting Customer.io MCP Server with VS Code Copilot

Common issues when connecting Customer.io to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Customer.io + VS Code Copilot FAQ

Common questions about integrating Customer.io MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.