Preview
What it is.
It connects to your Klaviyo account through Klaviyo's own MCP server over OAuth, then audits flows, segments, campaigns, deliverability and revenue attribution against live data.
There is no API key to store and no Python to install, which is why the setup is a connector and not a script. Developer work such as event tracking and webhooks goes to a separate skill, which keeps this one an operator audit.
What you get.
- Flow and segment audits against a live account
- Campaign and deliverability review
- Revenue attribution reading per flow
- OAuth connection through the connector directory, with no local key
- A split from the developer skill, so integration work does not muddy the audit
How to set it up.
Clone the repo and copy skills/klaviyo-analyst into ~/.claude/skills.
Connect Klaviyo through Claude's connector directory, under Settings and then Connectors, using Browse Connectors to search for it.
Authenticate over OAuth. The official server means no API key to store and no Python to install.
Start with a flow audit and not a campaign one, since flows carry the recurring revenue and get looked at least.
Check segment definitions for overlap, because overlapping segments are what produce duplicate sends.
Read revenue attribution per flow before improving any of them, so effort goes where money already arrives.
Pricing Plans
Free. MIT license.
A Klaviyo account is a paid prerequisite. Checked against the repo in July 2026.
Use cases
Auditing an inherited account
You've taken over a Klaviyo account with no documentation. Connect it over OAuth and start with the flow audit, which reads the live account instead of the interface your predecessor left behind.
Hunting duplicate sends
Customers complain about getting the same email twice. Ask for the segment audit and it finds the overlapping definitions that produce double sends.
Choosing which flow to improve
Every flow could use work and the quarter is short. Read revenue attribution per flow first, and the effort goes to the automation already producing money.
Deliverability before a big send
A heavy sending period is coming. Run the campaign and deliverability review against the live account before the volume goes up.
Best for
An inherited Klaviyo account
Flows built by someone else with no documentation is the case this is scoped to, and a live audit beats reading the interface.
Overlapping segments and duplicate sends
Segment audit catches this, and it is the failure customers notice fastest.
Ecommerce lifecycle revenue
Revenue attribution per flow tells you which automation is worth improving.