Frequently Asked Questions About Klaviyo App For Claude

General

What are the key use cases for the Klaviyo MCP connector with Claude?

The Klaviyo MCP connector works with Claude Chat and Cowork, allowing Claude to pull Klaviyo reports, reason across them, and help generate ready-to-use briefs, audits, and campaign assets that customers simply review and ship. Marketers can describe an outcome and come back to finished work. Here are some of the main use cases:

• Campaign management Create email campaigns, assign templates to them, pull campaign performance reports, and review historical campaign data without clicking through the Klaviyo UI.
• Email template work Build new email templates, fetch existing ones, and create or manage translations for multi-language sends.
• Audience and profile operations Look up individual profiles, search across profiles, update profile attributes, and subscribe or unsubscribe people from marketing. Useful for quick data lookups or bulk corrections.
• List and segment analysis Pull lists, inspect segments, and check segment definitions when you're trying to understand who's getting what.
• Flow performance Get details on automated flows and their reports, which is handy for diagnosing whether a welcome series or abandoned cart flow is performing as expected.
• Metrics and analytics Query metric aggregates and pull events, so you can ask things like "how did revenue from email compare last month vs this month" and get an answer without exporting CSVs.
• Catalog and content Pull catalog items and upload images from URLs, useful when prepping product-driven campaigns.

How do users enable and access the Klaviyo MCP connector with Claude?

Before you connect:

• You must have a Claude plan.
• You must have an Owner, Admin, or Manager role in the Klaviyo account you want to connect.

Start in Claude (desktop or web): go to Settings > Connectors, click Browse Connectors, search for Klaviyo, and connect.

Alternatively, open the Claude listing in the Klaviyo App Marketplace and follow the prompts to connect.

1. When prompted, sign in to Klaviyo and confirm that you are connecting the correct account. If you need another account, click Switch account.
2. Review the requested permissions, then click Allow to approve access and return to Claude.

Permissions and access control

What permissions does the Klaviyo MCP connector use?

When connecting the Klaviyo MCP server, users grant the following OAuth scopes:

• accounts read
• agents read and write
• applications read and write
• brands read and write
• campaigns read and write
• catalogs read and write
• conversations read and write
• coupon codes read and write
• coupons read and write
• custom objects read and write
• data privacy write
• events read and write
• flows read and write
• forms read and write
• images read and write
• lists read and write
• metrics read and write
• profiles read and write
• push tokens read and write
• reviews read and write
• segments read and write
• sender config read and write
• subscriptions read and write
• tags read and write
• templates read and write
• tracking settings read and write
• translations read and write
• web-feeds read and write
• webhooks read and write

Review the permissions shown on the Klaviyo approval screen before connecting. OAuth permissions describe what data the app can access or change; they do not mean that every action is available as a tool in Claude.

Since MCP is client-agnostic, is there any Klaviyo-side way to restrict which AI clients can connect?

Not currently. MCP server is designed to be client-agnostic, so Klaviyo does not currently restrict which compatible AI clients can connect. Additional controls are under consideration for the future.

Auditability and logging

What logging and auditability are available for MCP activity — specifically, can we see which user connected, which tools were called, and whether data was read or written?

The Klaviyo MCP connector uses Klaviyo's public APIs. To review its API activity, open Integrations, select Developers > Developer tools, then open Logs. Use the Source filter to select the connected app. Select an API call to view its method, request path, status code, and available request and response details.

These logs do not provide a complete record of what Claude read or changed: request or response bodies can be omitted, including when they are too large. The logs also do not identify the user who authorized the connection.

Sensitive data and PII

Are email addresses, phone numbers, or other personally identifiable information (PII) surfaced in this integration?

Yes. Depending on your Klaviyo account configuration, data accessible through the connector can include profile properties (such as email addresses, phone numbers, and custom attributes), list membership, and event history. Note that processing of such data is governed solely by your existing agreements with Anthropic, including Anthropic's Privacy Policy and any applicable Data Processing Agreements. How your personal data is handled — including whether it may be used for model training or other purposes — will vary depending on your Anthropic plan and any applicable data processing terms. Customers on certain plans, such as those with an enterprise agreement or an executed DPA, may have different data handling commitments. We encourage you to review your specific agreement with Anthropic or contact Anthropic directly to understand the protections applicable to your account.

Will the Klaviyo app for Claude access sensitive customer data like credit card numbers or highly sensitive PII?

The Klaviyo app is designed to have access to standard marketing-related data (customer profiles, orders, segmentation, campaign history, etc.). This includes custom profile properties, so review what those properties contain before granting access.

What protections are in place to make sure PII is not exposed? (Beyond the connector settings in Claude.) Are there any parameters/guardrails already set up? If not, are we able to set any up within the connector or Claude itself?

Data processing is governed solely by your existing agreements with Anthropic, including Anthropic's Privacy Policy and any applicable Data Processing Agreements. Klaviyo's data protection policies apply to data stored within the Klaviyo platform, but once that data is passed to Claude through the MCP integration, it falls under Anthropic's data governance framework. Customers will have to review Claude settings and security framework to understand what protections Anthropic has in place.

Helpful resources:

• How to use the Klaviyo app for ChatGPT
• Klaviyo MCP with Claude: https://www.klaviyo.com/blog/mcp-server-wins-for-working-efficiently
• Klaviyo MCP Server Connectors: https://developers.klaviyo.com/en/docs/klaviyo_mcp_server

Data privacy

Which data is shared with Anthropic if a customer establishes the MCP connector?

Data returned through the connector can include profile properties, list membership, and event history, depending on your Klaviyo account configuration. The Klaviyo MCP connector operates under the customer organization's own agreement with Anthropic. Klaviyo recommends reviewing Anthropic's subscription agreement and data processing terms as part of your due diligence. Klaviyo does not make representations on Anthropic's behalf regarding how connector data is handled or retained. For more information, please visit Anthropic’s Privacy Center.

How long does Anthropic retain data accessed through the Klaviyo MCP connector?

Retention of data processed through the Klaviyo MCP connector is governed by Anthropic's terms, not Klaviyo's. For full details on session data, logging, and retention windows, you can review your specific agreement with Anthropic, Anthropic's Privacy Policy and their applicable API terms.

Helpful resources:

• Claude Free, Pro, Max and when accounts from those plans use Claude Code: https://privacy.claude.com/en/articles/10023548-how-long-do-you-store-my-data
• For commercial products such as Claude for Work and the Anthropic API: https://privacy.claude.com/en/articles/7996866-how-long-do-you-store-my-organization-s-data

Accuracy and reliability

Can Claude hallucinate or provide inaccurate data? What can customers do to protect against that?

Yes, Claude can make mistakes. This means the generated text or data analysis may sometimes be inaccurate, nonsensical, or based on incorrect assumptions about your Klaviyo data. We recommend the following techniques to help you check the results produced by the Klaviyo app for Claude:

• Make sure your connected Klaviyo account data (segments, events, custom properties) is up-to-date and accurate, as the AI relies entirely on this source data.
• Always have a human in the loop to review, refine, and fact-check all AI-generated output before using it in a campaign or making a business decision.
• Ask Claude to cite the specific Klaviyo segment names, flow names, or campaign IDs it used for any important facts and assertions so that you can quickly confirm them within your Klaviyo account.