Klaviyo MCP Server: What It Does and How to Connect Klaviyo to AI in 2026
Yes — Klaviyo has an official MCP server, and it’s in general availability. The remote-hosted server at mcp.klaviyo.com/mcp lets any MCP-compatible AI tool read your campaigns, flows, profiles, segments, and reporting data, and write changes back — draft a campaign, update a profile, log an event. So if you’re searching “Klaviyo MCP,” the connection you want already exists and works today.
The thing worth knowing before you set it up: an MCP server hands your Klaviyo account to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches your flows for you, nothing fires when a customer abandons a cart, and nothing runs while the chat is closed. Here’s exactly what the Klaviyo MCP does, how to turn it on, where it stops — and what to use when you want Klaviyo work that runs on its own.
What the Klaviyo MCP server does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, VS Code, Windsurf, and others — talk to an outside app through a shared interface. Klaviyo maintains one official server, offered two ways:
- Remote-hosted MCP (
mcp.klaviyo.com/mcp) — the recommended path. No install, no hosting. You authorize it with OAuth and connect straight from a client like Claude or ChatGPT. - Local MCP — runs on your machine, authenticated with a private Klaviyo API key and scoped permissions, aimed more at developers who want it wired into an editor.
With it connected, an AI client can:
- Create and manage campaigns — draft an email campaign, assign a template, and refine subject lines from a prompt.
- Read flows — pull the structure and performance of an existing flow (welcome series, abandoned cart, win-back).
- Create and update profiles — add a profile, update properties, subscribe or unsubscribe someone from email or SMS.
- Query segments and lists — see who’s in a segment without opening Klaviyo.
- Log and query events — record a custom event or check whether one already happened.
- Pull reporting — campaign and flow performance without building a report by hand.
You’ll need an Owner, Admin, or Manager role on the account for the server to do anything — it inherits your permissions, not a separate set.
How to set up the Klaviyo MCP server
The remote server is the quick path — no code, no hosting:
- In your AI client’s connector settings, add a remote MCP server pointing at
mcp.klaviyo.com/mcp(or use the listed Klaviyo connector if your client — like Claude — already has one built in). - Authorize it through the OAuth prompt against your Klaviyo account. Dynamic client registration means most clients complete this in a couple of clicks.
- Confirm the tools show up, then start a chat and ask it to look up a flow or draft a campaign.
If your context window is small or you only need the basics, Klaviyo supports a core-tools-only=true parameter that trims the tool list for accuracy. The local option is there too, using a private API key with scopes you set, but most people never need it — the hosted server covers the same ground with nothing to run.
Where the Klaviyo MCP stops
None of this is a knock on MCP — it’s just the shape of the protocol. Four limits show up the moment you want more than a conversation:
- It only works inside a chat you start. Close the window and nothing happens. The AI doesn’t watch Klaviyo; it waits for you to ask.
- No triggers. A cart getting abandoned, a customer hitting a spend threshold, a flow finishing — none of these can start anything through MCP. There’s no “when this happens in Klaviyo, do that.”
- It’s one app at a time. The Klaviyo MCP knows Klaviyo. Getting a new VIP segment into your CRM, a Slack alert, and a spreadsheet means wiring up (and authing) a separate MCP server for each, then hoping your client can juggle them in one turn.
- You own the plumbing and the scopes. OAuth tokens, refresh, and the blast radius of read/write access to campaigns and customer data are all on you.
So the Klaviyo MCP is a great way to ask Klaviyo things and draft a campaign on the spot. It is not a way to make Klaviyo run — to have work happen on a schedule or in reaction to an event, across the other tools a customer touches.
Running Klaviyo work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Klaviyo natively — no MCP server to host, no OAuth plumbing to maintain — and to the ~260 other apps it supports, plus anything with a public API through your own key. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Klaviyo work happens whether or not anyone has a chat window open.
A few things that MCP can’t do but a Carly workflow can:
- When a customer abandons a cart → wait two hours, check if they’ve since purchased, and if not, add them to a win-back segment and notify the merchandising Slack channel.
- Every Monday → pull last week’s campaign performance from Klaviyo, summarize the winners and losers, and email the summary to the marketing lead.
- When a new VIP segment forms → sync the list to your CRM, tag the contacts, and draft a personalized offer for review.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Klaviyo connection and everything downstream.
If you just want to draft a campaign or check a flow from a chat, Klaviyo’s official MCP server is the right tool and it’s free to connect. If you want Klaviyo to actually do things — on a trigger, on a schedule, across every app a customer relationship touches — that’s the job MCP wasn’t built for, and it’s the one Carly was.
FAQ
Does Klaviyo have an official MCP server?
Yes. Klaviyo’s remote-hosted MCP server at mcp.klaviyo.com/mcp is officially maintained by Klaviyo and available to all customers in general availability, not a beta or community project.
Is the Klaviyo MCP server free? Connecting it is free — you’re authorizing an AI client against your existing Klaviyo account and role. You still need whatever Klaviyo plan your data lives on.
Can the Klaviyo MCP trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Klaviyo work across apps, you need a workflow tool like Carly rather than an MCP server.
What AI tools can connect to Klaviyo over MCP? Any MCP-compatible client — Claude, ChatGPT, Cursor, VS Code, Windsurf, and others — can connect to the Klaviyo MCP server, either through a listed connector or by adding the remote endpoint directly.
Can I connect Klaviyo to AI without coding or hosting a server? Yes. You don’t have to touch MCP at all. Carly connects to Klaviyo for you and lets you build the automation in plain language — describe what you want to happen and it wires up Klaviyo and the other apps involved, with no server to host and no code to write.
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
