How to
How to connect Claude to Klaviyo
Klaviyo ships an official Claude connector with a standard tool set across campaigns, profiles, lists, and reporting. The question is what happens when your workflow depends on custom properties, real segment logic, and an approval gate before anything sends.
Connect Claude to Klaviyo either with the official connector, which covers a standard tool set across campaigns, profiles, lists, and reporting, or with a custom MCP connector when you need more. A custom build adds your custom properties, segment logic, list management, and gated sends, authenticated as your own Klaviyo account.
Key takeaways
- Klaviyo has an official Claude connector in the directory with a standard tool set across campaigns, profiles, lists, and reporting.
- The gaps are deeper actions, custom properties, segment logic, and the approval gates a real sending workflow needs.
- A custom connector covers those gaps with write tools like `create_campaign`, `update_profile`, and `create_segment`, shaped to how your team works.
- It authenticates as your Klaviyo account through OAuth with the narrowest scopes, and sends and deletes always wait for your confirmation.
Does Klaviyo have an official Claude connector?
Yes. Klaviyo offers an official Claude connector in the directory, and it covers a standard tool set across campaigns, profiles, lists, and reporting. That set is general by design, so custom properties, segment logic, and the approval gates a real workflow needs are not always shaped the way your team works.
Start with the honest version: if your team mostly needs to look up campaign metrics, check profiles, and run routine actions across standard fields, the official connector may carry you. Connect it and try it first.
The friction shows up where ecommerce teams actually live: custom properties on profiles, segment conditions that encode your business logic, and a hard rule that nothing reaches subscribers without a human sign-off. A generic tool set is not built around any of that. A custom Klaviyo connector is.
The wider pattern holds beyond this one tool: in our June 2026 review of 264 business tools, 77 percent had no Claude connector at all, and none shipped full read-write out of the box.
How do I set up a custom Klaviyo connector for Claude?
A custom Klaviyo connector is built for you as a small MCP server that authenticates with OAuth using the narrowest scopes the work needs. Read tools and write tools are separated, Claude acts as your own Klaviyo account, and outbound actions like sending a campaign wait for your confirmation.
The path from request to working connector:
- 1Describe the Klaviyo work Claude should handle, including the custom properties, segment logic, and approval rules your sending workflow relies on.
- 2We build a small MCP server with read tools (metrics, profile and segment lookups) separated from write tools (create campaign, update profile, manage list membership).
- 3You authenticate through OAuth as your own Klaviyo account, so Claude inherits your existing access and never exceeds it.
- 4Claude starts prepping audiences and drafting campaigns in conversation, and outbound or destructive actions like send and delete run only after you confirm them.
Access is revocable at any time, and the connector never holds broader scopes than the work requires.
What can Claude do in Klaviyo with write access?
With full read-write access, Claude drafts an email or SMS campaign with subject line and content, sets the audience, creates or updates profiles including custom properties and consent fields, manages list membership, builds segments from described conditions, and applies tags, then queues sends for your approval.
The tool set maps to the campaign-prep routine most marketers do by hand:
create_campaignto draft the email or SMS with subject line and content, set the audience, and leave it for review.update_profileto create or update a profile, including custom properties and consent fields.manage_list_membershipto add or remove profiles from a list and build a target audience.create_segmentto define or update a segment from a set of conditions you describe.apply_tagsto organize campaigns, flows, and lists.
Audience prep and campaign setup happen where your customer data already lives, and a prepared campaign can be scheduled or sent once you approve it.
Will Claude send a Klaviyo campaign without my approval?
No. Sending and scheduling are separate, gated write actions. Claude can draft the campaign, set the content, and choose the list or segment, but nothing goes out until you approve it. You decide which actions run automatically and which require a confirmation step before anything reaches your subscribers.
In practice, most teams let metric lookups and segment reads flow freely, keep profile updates fast, and reserve confirmations for sends, deletions, and consent changes. The line is yours to draw.
Claude only has your access
The connector authenticates as your account through OAuth with the narrowest scopes the work needs. It never grants Claude more access to your subscribers, lists, or flows than you already have, and you can revoke it at any time.
When is the official Klaviyo connector enough, and when is it not?
The official connector is enough when your work stays inside a standard tool set across campaigns, profiles, lists, and reporting. It stops being enough when you need custom properties, your own segment logic, deeper list management, or an approval gate shaped to your sending rules. Those are custom-connector territory.
A quick self-test: write down the last five things you wished Claude had done in Klaviyo. If they are all standard lookups and routine actions, connect the official connector today. If any involve a custom property, a segment built from your own conditions, or 'draft it, but nothing sends until I sign off,' the standard tool set will not carry them, and a purpose-built connector will.