Klaviyo is now a backend for your agents: real examples and four of ours

Klaviyo is turning into a backend that any agent can drive, not just its own. At K:BOS 2026 Klaviyo said it exposes more than 260 MCP tools and 490 APIs, and it introduced its first command-line interface, according to an Info-Tech technology note. The decision for a marketing team shifts from which vendor's agent to buy to who owns the orchestration layer. Examples make that concrete, so here are the ones Klaviyo publishes and four simple ones we would run first.

How you connect today

Klaviyo announced its Claude integration on May 7, 2026, in a community post. In Claude you go to Settings, then Connectors, then Browse Connectors, search for Klaviyo and authenticate. It is available on Claude Pro, Max, Team and Enterprise plans. Teams that want a custom connection can use the Klaviyo MCP server documentation, which recommends the remote-hosted server over a local one and marks each tool as read-only or not.

Examples Klaviyo publishes

From the developer docs, the sample prompts are plain:

• "Show me the performance of my email campaigns from the last 30 days."
• "Which flows are performing the best in terms of conversions?"
• "Create an email campaign promoting our Memorial Day sale."

The Claude launch post adds a Query Metric Aggregates tool, which exposes the data behind Klaviyo's in-app Metric Reporting, and support for MCP Apps so developers can build inline charts and dashboards. Its example prompts include the top five campaigns by open rate last month, active flows with the lowest click-through over 90 days, abandoned-checkout flow performance, and the current makeup of a lapsed-purchaser segment. Its Cowork examples are a weekly performance digest saved as a document, a flow audit with a prioritized fix list, subject lines and copy for a re-engagement flow based on a real segment, and reusable skills for audience mapping and campaign briefs.

Limits to know before you connect

Access is permission-based, and Klaviyo says there is no documented way to expose lists and segments while hiding profile data such as email or address. If profile tools are on, profile attributes may be reachable. Klaviyo's advice is to keep permissions as limited as possible. A community reply also says creating drag-and-drop drafts from existing templates is not fully supported through the current MCP and API flow. And the Info-Tech note is clear that Klaviyo's "autonomous CRM" is a direction rather than a finished capability, with Composer's continuous background operation still in the pipeline.

Four simple examples we would run first

These are Open Target workflow designs, not Klaviyo claims or results. Each is read-heavy, low-risk and tied to an outcome, which is how we start any agent flow.

1. The Monday flow audit

Ask the agent to list every live flow, pull the last 90 days of click and conversion metrics for each message, and flag the bottom five with a one-line reason and a suggested fix. Read-only. Outcome: the number of flagged messages fixed each month, and the revenue per recipient of those flows before and after.

2. The lapsed-customer brief

Have the agent read the makeup of your lapsed-purchaser segment, then write a one-page brief with three angles, three subject lines each and a recommended test split. A human approves before anything is built. Outcome: reactivation rate against a holdout that received nothing new.

3. The weekly digest with a decision

Each Monday, summarize the last seven days of campaigns in a short document and end with the one change worth making. For a restaurant group, that might be which send day drove the most reservations. Outcome: whether the recommended change was made and what it did.

4. The draft-only campaign builder

Give the agent a promotion and a segment and ask for a campaign draft with subject line and copy. Instruct it never to schedule or send. Given the template limits above, test whether the draft lands the way your team expects before relying on it. Outcome: time from brief to approved draft, and edits per draft.

Built-in agent or your own?

Klaviyo's Composer, its marketer agent, now has scheduled and recurring tasks and more than 138,000 users, and it is priced on consumed capacity, so cost varies with task complexity and data volume. Driving Klaviyo from your own agent over MCP gives you portable workflows and more control over cost and permissions. The built-in agent gives you speed. Neither is wrong. Pick based on who on your team can maintain the workflows.

What to do about it

1. Start read-only. Connect with the narrowest permissions that support the audit and digest workflows.
2. Check profile exposure before enabling any tool that can reach email addresses or other personal fields.
3. Attach one outcome to each workflow and keep a holdout where you can.
4. Keep a human on anything that sends. Draft-only until the workflow has a clean record.
5. Decide who owns orchestration before comparing Composer's usage-based cost with your own build.