Claude + Klaviyo
Klaviyo MCP and Klaviyo Claude Integration: Set Up Read-Only First
For DTC lifecycle teams and agencies connecting Claude to Klaviyo for reporting, audits and drafts, without handing an AI the send button.
What the Klaviyo MCP server does
The Klaviyo MCP server lets an AI client such as Claude call Klaviyo's APIs as tools. Klaviyo documents more than 260 tools across campaigns, flows, reporting, templates, segments, lists, profiles, events, catalogs, coupons, forms and reviews, as of October 2026, and recommends its remote server at mcp.klaviyo.com over the local one.
Inside Claude, the simplest route is the Klaviyo connector in Claude's directory. It is made by Klaviyo, marked Anthropic verified, listed since January 2026 and currently shows 27 tools, including campaign reports, metric queries and campaign creation. In its K:BOS 2026 product update in September, Klaviyo said it is going headless, with its tools callable by Claude, ChatGPT or custom agents depending on account role and connector scope.
The connection is plumbing, not a lifecycle strategy. How we run Klaviyo programs is on our agentic Klaviyo page.
What you can automate with Klaviyo and Claude
These are the Klaviyo Claude jobs Operator Intelligence sets up most often. Most run read-only.
Campaign and flow reporting
Revenue per recipient, click rate and placed-order rate by campaign or flow, pulled from Klaviyo's reporting tools instead of exported spreadsheets.
Flow audits
Claude maps flows, triggers and messages against the core DTC flow map and flags gaps. A strategist checks every finding.
Segment analysis
Engaged, at-risk and VIP segments profiled, with the ones that are shrinking or over-mailed called out.
Campaign and template drafts
Drafts built from a brief and your brand rules. Drafts stay drafts until a person approves and schedules them.
Catalog and coupon setup
Catalog items and coupon codes for a launch, created from approved product and offer data.
Cross-system digests
A weekly digest that reads Klaviyo alongside Shopify and GA4, which a custom workflow handles better than a single connector.
Setup options for the Klaviyo Claude integration
Four ways to connect, as of October 2026. Most brands start with the first; agencies and stricter data rules push toward the second and third.
| Option | How it authenticates | How you limit it | Best for |
|---|---|---|---|
| Klaviyo connector in Claude's directory | OAuth sign-in from Claude's Connectors settings | Klaviyo role permissions, plus Claude admin limits on connector actions | One account, interactive reporting and drafts |
| Remote MCP server as a custom connector | OAuth with dynamic client registration to mcp.klaviyo.com | Settings for read-only, toolsets and excluding user-generated content | Agencies or brands with several Klaviyo accounts |
| Local MCP server | A Klaviyo private API key you create | The key's own scopes, plus read-only and user-generated-content settings | Tight control, such as lists and segments without profile access |
| Custom workflow (n8n + Claude) | API credentials held in the workflow platform | Each step's scope, plus human approval on any write | Scheduled audits, QA and digests across systems |
Klaviyo MCP permissions, scopes and security
Klaviyo's controls, from its developer documentation as of October 2026. Operator Intelligence sets them before the first prompt, not after.
| Control | What it does | How we use it |
|---|---|---|
| Role requirement | Remote connections need an Owner, Admin or Manager role | Connect through a named person's account, never a shared login |
| Read-only setting | Disables every tool that can write to the account | The default for reporting, audits and the first weeks of a rollout |
| Toolsets | Limits the server to tools whose API scopes fall within a list, such as campaigns:read | Only the resources the job needs |
| Exclude user-generated content | Disables tools that read content customers wrote, which a model could misread as instructions | On unless a job needs review or profile text |
| Private key scopes (local server) | The key carries only the permissions you grant | Used when profile data must stay out entirely |
| Tool-call review | Klaviyo advises reviewing each tool call so the client isn't acting on malicious instructions | Write tools need confirmation; sends stay with people |
Why read-only mode isn't the whole answer
Read-only mode stops changes, but it doesn't hide customer data. Klaviyo's K:BOS 2026 update notes that profile data stays readable in read-only mode, and points to a local server with a scoped private key when you need, for example, lists and segments without profile access.
The full tool list also includes tools that send or cancel campaigns, delete objects and subscribe profiles to marketing. Turning on write access is a decision for your lifecycle lead, made tool by tool. On Claude Team and Enterprise plans, admins can also restrict which actions each connector allows, such as reads without writes. Our MCP integration guardrails apply the same rules to every system we connect.
A typical build: Claude on Klaviyo with Shopify context
Operator Intelligence hasn't published a Klaviyo MCP case study yet, so this is a typical build. It starts with a read-only Klaviyo connection for a flow audit and weekly reporting. Claude reads Klaviyo alongside Shopify product and order data, maps every flow against the core DTC flows (plus jewelry add-ons for jewelry brands) and drafts a prioritized fix list for a strategist to review.
Once the reporting is trusted, we add narrow write tools: campaign drafts from approved briefs and template drafts checked against brand rules. A QA step checks links, UTMs and discount codes before a person schedules anything. Jewelry brands will find the flow-by-flow detail in our jewelry email marketing playbook. If you're weighing Klaviyo's own AI against custom agents, see Klaviyo Composer vs custom AI agents.
Klaviyo is a trademark of Klaviyo, Inc. Operator Intelligence is an independent consultancy.
How we set up the Klaviyo MCP server
Confirm accounts and roles
Which Klaviyo accounts, who connects, and whether profile data is in scope at all.
Choose the route
Claude's directory connector, a remote custom connector or a local server with a scoped key.
Lock it down
Read-only, toolsets and user-generated-content settings applied before the first question.
Check the answers
Run real reporting questions and compare the results with Klaviyo's own reports.
Add reviewed writes
Only once reporting is trusted, and only for drafts.
Hand over
A runbook, the list of enabled tools and a quarterly access review.
Frequently asked questions
Can Claude send Klaviyo campaigns through MCP?
Klaviyo's MCP tool list includes a send campaign tool, so it's possible with write access. We don't set it up that way: writes are limited to drafts, and a person schedules and sends.
Which Klaviyo role do we need?
Remote MCP connections require an Owner, Admin or Manager role. Klaviyo's docs describe adding the remote server as a custom connector when you work across multiple accounts, which suits marketing agencies running several client accounts.
Does read-only mode protect customer data?
It stops changes but still lets tools read profiles. To keep profile data out, exclude tools that read user-generated content or use a local server with a private key scoped to the job.
Which AI tools work with the Klaviyo MCP server?
Klaviyo's docs cover Claude, Cursor and VS Code among others. Web clients such as ChatGPT need the remote server; the local server suits desktop clients.
What does a Klaviyo Claude integration cost?
Connecting Klaviyo's official server takes far less work than a custom workflow. Cost depends on the number of accounts, which tools are enabled, whether writes and approvals are needed and how much Shopify or GA4 context is involved. Request a scoped proposal.
Connect Claude to Klaviyo without handing over the send button
Tell us what you want Claude to do in Klaviyo. We'll recommend the connector, the MCP server or a custom workflow, and the settings that keep it safe. Or browse other AI integrations.
Book a scoping callSources
- Klaviyo developer docs, Klaviyo MCP server (2026): Klaviyo MCP server enables AI clients to interact with Klaviyo data; remote-hosted server recommended over local server
- Klaviyo developer docs, Connect to the MCP server (2026): Remote server https://mcp.klaviyo.com/mcp; Owner, Admin or Manager role required; OAuth with dynamic client registration; read-only parameter disables write tools; toolsets parameter limits scopes; disable-tools-with-user-generated-content; local server via private API key with READ_ONLY and ALLOW_USER_GENERATED_CONTENT; custom connector for multiple accounts; web clients like ChatGPT need the remote server
- Klaviyo developer docs, Available tools (2026): Over 260 tools across campaigns, flows, reporting, templates, segments, lists, profiles, events, catalogs, coupons, forms, reviews and more; includes send_campaign, cancel_campaign_send, delete tools and subscribe_profile_to_marketing; review each tool call to ensure the client is not acting on malicious instructions
- Anthropic, Claude connector directory (2026): Klaviyo connector for Claude: made by Klaviyo, Anthropic verified, added January 2026, 27 tools, sign-in required
- Klaviyo Community, Product updates and announcements (2026): K:BOS 2026 (Sep 9, 2026): Klaviyo going headless, tools callable by Claude, ChatGPT or a custom agent depending on role and connector scope; read-only mode does not hide profile data; local server with scoped private key for tighter control
- Anthropic (claude.com blog) (2026): Admins can restrict which actions are available within each MCP connector, e.g. allowing read access but disabling write operations (April 9, 2026)
- Anthropic Help Center (2026): Custom connectors connect Claude to services not verified by Anthropic; malicious MCP servers may include hidden instructions; only Owners can add custom connectors on Team plans
Related
Agentic Klaviyo email and lifecycle
Flow audits, QA and digests run by agents.
Klaviyo Composer vs custom AI agents
When Klaviyo's built-in AI is enough.
Jewelry email marketing playbook
Klaviyo flows for jewelry buying cycles.
Custom MCP server development
Scopes, logging and review gates for any system.
Claude + Shopify integration
Connector, Dev MCP and custom workflows.
Agentic digital strategy for DTC brands
How lifecycle, paid, site and AI search agents fit together.