The Klaviyo MCP, Tested: What Works, What Breaks, and What's Missing

TL;DR: On May 7, Klaviyo expanded its Anthropic integration. The native Klaviyo Connector is now in the Claude directory, Cowork can run unattended marketing workflows, and a new Query Metric Aggregates tool exposes raw revenue and engagement data the in-app reports do not. I connected it to a real Klaviyo account and ran the new flow audit mode end-to-end. The integration works. Two things stand out that nobody else is reporting: a metric semantics gotcha that can produce a confident, wrong audit finding if you trust metric names without verifying them, and a real tool gap that limits compliance review for supplement, health, and CBD brands. This post is the hands-on review every existing piece of coverage skipped.

Three MCPs landed in nine days. Meta on April 29. Higgsfield on April 30. Klaviyo on May 7. Different surfaces, same direction: the tools DTC brands use to ship ads, generate creative, and run email are no longer locked behind dashboards. They are addressable from inside a Claude chat or a Cowork session that can run unattended.

I have been writing the Meta MCP series and the compliance follow-up for the last week. Klaviyo's update is the third pillar of the same wave. Andrew Bialecki, Klaviyo's CEO, framed the integration as Claude shifting from "analyst who tells you what to do" to "teammate who actually does the work." Giri Sreenivas, Klaviyo's CPO, put it more bluntly in their infrastructure post: the industry question is becoming "Why should you ever log into Klaviyo again?"

That is a strong claim. So I tested it. Here is the part of the story you have not read in the press release.

What Klaviyo and Anthropic actually shipped on May 7

Most of the coverage of the announcement is a rewrite of the Klaviyo blog post. The substance is real, but the press cycle smoothed over what changed mechanically. Here is the unvarnished list.

1. The Klaviyo MCP server is now in the Claude Connector directory. Earlier in the year, you could connect Klaviyo to Claude Code or Claude Desktop using a remote MCP URL plus an OAuth flow. As of May 7, the connector lives in claude.ai/directory/connectors. You search for Klaviyo, click connect, approve the OAuth scopes, and you are done. No CLI, no API keys, no copy-pasted config. The setup time dropped from "30 minutes for a technical user" to "two minutes for anyone."

2. Claude Cowork now sees Klaviyo data. Cowork is the unattended-execution surface Anthropic shipped earlier this year. It has filesystem access, multi-step tool chaining, and the ability to keep working while you are not at the keyboard. Before May 7, Cowork could not call Klaviyo tools. Now it can. The pitch for this is the one Klaviyo is leaning on hardest: describe an outcome ("audit my flows," "build my weekly report," "draft a re-engagement campaign for at-risk subscribers"), step away, come back to a finished document.

3. Query Metric Aggregates is the most important new tool. This is the one most coverage is glossing over. The existing Klaviyo MCP exposed read tools for campaigns, flows, profiles, lists, segments, and templates. What it did not expose was the raw event/revenue data that powers Klaviyo's in-app Metric Reporting. Without that, an MCP run could pull "this campaign opened at 38%" but could not answer "what is my total Klaviyo-attributed revenue from email this month, broken down by flow vs campaign, week over week." Query Metric Aggregates closes that gap. You can now grouping by attributed flow, attributed message, campaign, segment, send cohort, and run a sum_value aggregation against the Placed Order metric for any time window up to a year. It is essentially a SQL-style query layer on top of Klaviyo events.

4. MCP Apps support means inline charts and dashboards. This is for builders. Anthropic's ext-apps SDK plus Claude Code now lets developers build interactive surfaces that render directly inside a Claude conversation. A revenue-by-flow bar chart that updates as you drill in. A flow-audit dashboard with a sortable table. Klaviyo and Anthropic are positioning this as the path for partners and agencies to build domain-specific tools on top of the connector.

That is the actual May 7 update. Everything else in the announcement is reframing existing capabilities for the new audience now that the connector is one click away.

How to connect it in two minutes

If you are coming to this fresh, here is the path:

1. Go to claude.ai/directory/connectors.
2. Search "Klaviyo." Click Connect.
3. Approve the Claude scopes. Klaviyo will redirect you to its OAuth screen.
4. Approve the Klaviyo permissions. You need to be an Owner, Admin, or Manager on the Klaviyo account.
5. You are done.

Plan requirement: You need Claude Pro, Max, Team, or Enterprise. The free tier does not get connectors. If you are running this on Claude Code instead of claude.ai, the same connector works through the IDE.

For multi-account agencies, you will hit a current limitation. Each connector instance binds to one Klaviyo account. There is no built-in account switcher inside Claude. The agency-friendly workaround is either (a) manage one client at a time per session, or (b) drop down to a custom remote MCP URL and pass account-specific OAuth tokens, which is more setup but supports multiple accounts in one workspace. We will come back to this in the Native Connector vs Composio section.

I tested the audit mode against a real account

Earlier this week I shipped a v1.1 update to the klaviyo-flow-architect skill that runs in what I called Live Data Mode. When the new Connector is detected, the skill pulls real flow performance via klaviyo_get_flow_report, compares per-message metrics against the benchmarks the skill already had, generates a prioritized fix-it list, and saves a markdown audit report. Then I ran it against an actual Klaviyo account.

Most of it worked exactly the way the press release would lead you to expect. The skill listed flows. It pulled per-message performance. It compared opens, clicks, and revenue per recipient against the benchmark table. It computed dollar-impact estimates for closing each gap and saved the entire audit to a markdown file in under a minute. This is the part most existing coverage gets right, and it is the part that earns the integration its weight: a 30-minute deliverable that used to be a half-day analyst job.

Here is the part you will not read in any existing piece on the May 7 announcement.

The metric semantics gotcha nobody is reporting

Klaviyo's MCP exposes hundreds of metrics. Some are core platform events like "Subscribed to List" and "Placed Order." Some are integration-specific like "Fulfilled Order" (Shopify) or "Viewed Product" (custom API). Some are page-level interaction events that fire on signup-form click activity.

Those last ones are dangerous if you treat them as evidence without verifying what they represent.

During the audit run, I almost shipped a finding built on a metric named subscribe_page_submit. The metric name reads like "successful form submission." Klaviyo categorizes it as an Internal metric, which I initially interpreted as a Klaviyo-native subscription confirmation. Cross-referencing its monthly counts against Subscribed to Email Marketing produced an alarming gap that, taken at face value, looked like a broken acquisition pipeline.

It was not a broken pipeline. It was a misread metric.

When I pulled raw events for subscribe_page_submit using klaviyo_get_events, every event had a null profile attached. The events clustered three at a time within ten-second windows from the same browser fingerprint - a pattern consistent with bot or scraper activity, not human submissions. The metric does not track successful subscriptions. It tracks page-level submit-button click activity, including from non-humans.

If the audit had run autonomously through Cowork without a second-pass check, it would have produced a confident, professional-looking report with a wrong diagnosis. The brand operator would have spent the next week chasing a problem that did not exist. The risk is highest in unattended runs precisely because the operator is not in the loop to catch the inference.

The rule I added to the audit skill itself, which now applies to every account it runs against:

Verify metric semantics by sampling raw events before treating counts as evidence. Standard Klaviyo metrics use Title Case ("Subscribed to List", "Placed Order"). Custom and page-tracking events tend to use snake_case ("subscribe_page_submit", "form_view"). The naming convention is a tell. When the metric name is non-standard, pull a few raw events with klaviyo_get_events, check whether profiles are attached, look at event_properties, and confirm the semantics before building a finding on the count.

This applies to any brand running an audit through the new MCP, regardless of account size. It is the kind of thing you only find by running the integration end-to-end against real data. Press-release rewrites and feature lists do not.

The bigger pattern is worth naming. The whole appeal of agentic workflows is that the agent does the work without your supervision. The whole risk of agentic workflows is that the agent can produce confident output built on misread inputs without your supervision. Verifying metric semantics is one specific instance of the broader rule: the agent is only as right as its data layer, and the data layer needs the same skepticism you would bring to a human analyst handing you a chart.

What works today

Here is what the connector does well, ranked by usefulness for a DTC brand.

Flow audits. The skill pulls every active flow, computes per-message gaps against the benchmark table, and writes a prioritized fix-it list with revenue-impact estimates. For most established DTC brands - twenty flows, six months of campaigns, real recipient volume - this is a 30-minute deliverable that used to be a half-day analyst job. It is the use case that earns the integration its weight.

Weekly performance digests. Set this up once. On Monday, Cowork pulls last week's campaign and flow performance, writes a plain-English summary with wins, underperformers, and recommended next steps, and saves the file to a folder you specify. The skill I shipped includes a digest mode with a recurring-run pattern. The first time it runs against a real account, you suddenly stop fighting Klaviyo's reporting UI to assemble the same numbers manually.

Segment-grounded email copy. This is the use case that needed Query Metric Aggregates the most. Pulling a representative sample from a target segment, identifying actual purchase patterns (top product, AOV range, replenishment cycle, engagement decay), and grounding copy in those patterns is the difference between an AI-generated re-engagement email that says "we miss you" and one that opens with "if your last order of [Product] ran out around 60 days ago, you have been overdue for 50." The connector now exposes the data needed to do this without exporting CSVs.

Multi-account agency reporting. This works through the custom-MCP-URL path more cleanly than through the Connector directory, but it works. An agency managing ten Klaviyo accounts can run a Cowork loop, pull flow and campaign metrics per client, write client-specific performance briefs, save them to client-named folders, and produce a half-day's worth of reporting overnight. This is the use case Klaviyo's blog post talks about, and unlike most of the use cases they market, it actually pays for itself the first month.

Light-touch campaign drafting. Cowork plus the connector can pull a segment, propose three subject line variants, draft body copy grounded in segment characteristics, and save it as a markdown file ready for review. It does not push the campaign live, which is the right call for now. It generates the artifact a marketer would otherwise build from scratch and shortens the cycle from segment definition to first draft from hours to minutes.

Native Connector vs Composio: which path for your stack

Both vendors have public pages. Klaviyo wants you on their official connector. Composio wants you on theirs. Neither is wrong, and neither writes the neutral comparison. So here is the decision tree.

Use the native Klaviyo Connector if:

• You are a single brand using Klaviyo as your primary marketing platform.
• You are not technical, or you do not want to be.
• You want OAuth, not API keys.
• You do not need to combine Klaviyo with five other platforms in the same agent run.

Use Composio if:

• You are an agency or technical operator running cross-platform workflows.
• You need Klaviyo plus Shopify plus Meta plus Google Analytics plus a CRM in the same agent context.
• You are already on Composio for other tools.
• You want one router managing tool routing across many integrations rather than connecting each one separately.

The native Connector covers all major Klaviyo endpoints and adds the new Query Metric Aggregates and MCP Apps support directly. Composio wraps the same Klaviyo API but exposes it alongside 1000+ other tools through its router. Tool coverage is nearly equivalent for Klaviyo specifically; the differentiator is multi-platform aggregation.

For a typical DTC brand with a Klaviyo + Shopify + Meta stack, the native Connector for Klaviyo plus Meta's official MCP plus the Shopify dev tools plugin is the right combination today. For an agency working across ten clients on five platforms each, Composio's router is the cleaner architecture even if it costs more to set up.

There is a middle ground worth flagging. If you are already running Polar's analytics MCP for cross-platform attribution, Polar surfaces blended Klaviyo + Shopify + Meta numbers in one query. Polar plus the native Klaviyo Connector lets you ask blended attribution questions through Polar and drill into Klaviyo specifics through the Connector when needed. This is the pattern I have been recommending to brands building their stack from scratch.

Where this fits in the bigger MCP wave

Three official MCP releases in nine days, all aimed at the same DTC creative-and-execution loop:

• April 29: Meta's official Ads MCP and CLI. Pull Meta performance, push campaigns live, run dashboards. (Coverage here.)
• April 30: Higgsfield's hosted MCP. Generate static and video creative across thirty image and video models, up to 4K and 15 seconds. (Same post.)
• May 7: Klaviyo's expanded Anthropic integration. Native Connector, Cowork support, Query Metric Aggregates, MCP Apps. (This post.)

The pattern is not subtle. The platforms DTC brands rely on are racing to expose themselves as MCP-addressable tools. Anthropic's Claude.ai and Cowork are the consumer-facing surfaces; Claude Code is the technical surface; the connectors plug in everywhere. This is not three independent product launches. It is three legs of the same stool.

The DTC implication is structural. A year ago, "AI marketing" meant "I copied a campaign brief into ChatGPT and it gave me a passable email." Now it means "I described an outcome in Cowork and came back to find the audit, the campaign drafts, the new ad creative, and the launch dashboard built and saved to my repo." The plumbing has caught up to the pitch. The thing that does not catch up automatically is the brand context layer that decides whether the output sounds like your brand or sounds like everybody else's.

That is the through-line for the entire wave. The MCPs make the tools addressable. They do not make the output good. Output quality still depends on what the agent reads before it writes - the brand voice file, the customer personas, the objections, the offers, the regulatory guardrails. That is the actual moat.

Compliance: what supplement, health, and CBD brands need to know

This is the part of the integration nobody is writing about, and the part regulated DTC brands need most.

The Klaviyo MCP plus Cowork can now pull a segment, write a re-engagement email grounded in real customer data, and save the draft. If you sell supplements, that draft can include a phrase the FDA considers a disease claim before you have a chance to review it. The structure/function rule that governs every word of supplement marketing copy does not stop applying because Claude wrote the draft instead of a copywriter.

The rules have not changed. The exposure has.

What you cannot say in any AI-generated email going to your subscribers:

• Direct disease claims (treats, cures, prevents, diagnoses any condition)
• Drug-style efficacy phrasing ("clinically proven to reduce inflammation")
• Specific outcome timeframes without citable substantiation ("feel results in seven days")
• Fabricated statistics or testimonials Claude makes up because the prompt was vague

What you do need:

• A guardrails file in your brand context that lists banned phrases, required disclaimers, and category-specific rules
• A pre-publish review step that compares draft copy against the guardrails before it goes to Klaviyo as a draft, let alone live
• The FDA structure/function disclaimer in any email that makes any health-adjacent claim: "These statements have not been evaluated by the Food and Drug Administration. This product is not intended to diagnose, treat, cure, or prevent any disease."

There is also a real tool gap for compliance review I hit during the audit. The native Klaviyo MCP exposes klaviyo_get_email_template for templates, but the existing flow message content is stored as a flow-message-content object that is not retrievable through that tool. When I tried to pull the body of an existing welcome email for an automated compliance pass, I got a 404. The fallback today is either pasting the email content into the conversation manually, or dropping to the REST API directly. This will probably be addressed in a future Klaviyo MCP release. Until then, do not assume the AI can read your existing flow copy. Plan to feed it manually.

The full compliance pattern for AI-generated marketing assets - the same one that applies to the Meta MCP - applies here. The tools changed. The FTC and FDA rules did not.

What is not ready yet

Every other piece of coverage on the May 7 announcement is uniformly positive. Here is the part that should temper your expectations.

Flow message content is not retrievable. As above, the tool gap blocks automated compliance review of existing flow copy. Worth filing as a feature request with Klaviyo. Worth assuming the workaround is manual.

Multi-account switching is friction. Each Connector instance binds to one Klaviyo account. Agencies need either the custom-URL path or a workaround. This will probably ship.

Rate limits are real for big accounts. A single agency pulling reports across ten large Klaviyo accounts in one Cowork run will hit Klaviyo's rate limits before the run completes. The Klaviyo Community has a public thread on this. The mitigation today is paginating runs across multiple sessions or using an intermediary like Porter that handles rate limiting and pagination.

Free Claude users are out. The Connector requires Pro, Max, Team, or Enterprise. If your agency is testing this on personal Claude accounts, plan to upgrade.

Cowork context windows are finite. Long agency runs across many accounts will hit Claude's context limits. The fix is breaking the run into smaller chunks per account or per task type. This applies to any Cowork workflow, not specifically to Klaviyo.

The "step away and come back to finished work" pitch needs supervision. Cowork is good. It is not magic. For high-stakes decisions (a campaign going live, a segment about to receive a re-engagement push, anything compliance-sensitive), keep a human in the loop on the final review step. The right pattern is "Cowork drafts, human approves, Cowork ships." The pure-autonomous version of this is not where the technology sits today and probably should not be where it sits for marketing decisions you cannot easily reverse.

Should you use it

If you are a DTC brand on Shopify using Klaviyo as your primary email and SMS platform, yes. Setup is two minutes. The weekly digest mode alone pays for itself in saved analyst time. The segment-grounded copy mode is the most defensible new use case for AI-generated marketing copy I have seen ship.

If you are an agency, yes, but plan the multi-account architecture deliberately. Pick the custom-URL path or Composio depending on your existing stack. Multi-client reporting is where this pays for itself fastest.

If you are a compliance-regulated brand (supplements, health, CBD, anything FDA-adjacent), yes, but treat the connector like a draft generator, not a publisher. Build the guardrails file. Keep a human review step. Do not let Cowork ship copy unattended for regulated claims.

If you are a technical team already on Composio or a custom MCP setup, the new tool surface (Query Metric Aggregates especially) is the part you want regardless of how you connect. The capability is the same; the path to it is the only variable.

The Sreenivas line - "Why should you ever log into Klaviyo again?" - is provocative on purpose. The honest answer in May 2026 is "you still will, for a while." But the work that used to require logging in - assembling reports, reading flow performance, drafting campaigns from segment data - now happens in a conversation with Claude that ends with a finished file in your repo. That is the part that is real. Not magic, not finished, not without limits. But real, and it shipped two days ago.

If you want the rest of the DTC stack wired this way, that is what the DTC Stack is doing - one Brand Brain plus nineteen execution skills, the Klaviyo skills updated this week to use Live Data Mode through the new Connector. The integration is the easy part. The brand context that decides what the AI says when it has live access to your data is the part that compounds.

Frequently asked questions

What plan do I need to use the Klaviyo Connector in Claude? Claude Pro, Max, Team, or Enterprise. The free tier does not get connectors. You also need to be an Owner, Admin, or Manager on your Klaviyo account.

Can I use the Klaviyo MCP with ChatGPT instead of Claude? Klaviyo has an official ChatGPT app for Klaviyo that exposes a similar but not identical tool surface. ChatGPT is fast for ad-hoc queries; Claude with Cowork is stronger for deeper analysis and unattended document generation. Many teams use both for different jobs.

What is Query Metric Aggregates and why does it matter? It is a new tool in the May 7 release that exposes the raw event and revenue data behind Klaviyo's Metric Reporting. It lets the AI compute things like "campaign vs flow revenue split by segment for the last 30 days" without exporting CSVs or rebuilding dashboards. It is the most important new capability in the update.

Is the Klaviyo MCP safe for compliance-regulated brands like supplement, health, or CBD? Yes, with discipline. Build a guardrails file with banned phrases and required disclaimers. Keep a human review step before any AI-drafted copy goes live. Do not let Cowork ship copy unattended for FDA-regulated claims. The structure/function rule applies to AI-written copy exactly the same as to human-written copy.

Klaviyo MCP vs Composio: which should I pick? Native Connector for single brands using Klaviyo as their main platform. Composio for agencies running cross-platform workflows where Klaviyo is one of many integrations. Tool coverage on Klaviyo is nearly equivalent; the differentiator is whether you need multi-platform routing.

How do I run a flow audit using the Klaviyo MCP? Connect the Klaviyo Connector in Claude. Ask Claude to audit your flows and save the report. With our klaviyo-flow-architect skill in Live Data Mode, the audit pulls 90-day performance per message, compares against benchmarks, generates a prioritized fix-it list, and saves the markdown report. Without the skill, you can ask Claude in plain English; the output will be less structured but still useful.

What is the "metric semantics" gotcha you mentioned? Some Klaviyo metrics have names that read like one thing but track another. subscribe_page_submit sounds like a successful subscription event but is actually a page-level click-tracking event that fires on submit-button activity, including from bots and scrapers. If you trust the metric name without sampling raw events, you can build a finding on a foundation that does not support it. The fix is checking the raw events with klaviyo_get_events before treating any count as evidence, especially for snake_case metric names. Title-case metrics like "Subscribed to List" and "Placed Order" are safer defaults. The risk is highest when running unattended Cowork audits where the operator is not in the loop to catch the wrong inference.