Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Klaviyo to Claude Code

Make Claude draft campaigns and build segments in Klaviyo. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Klaviyo to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Klaviyo, you add a Klaviyo MCP server: a small hosted service that exposes Klaviyo's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Klaviyo account. No API keys pasted into config files.

claude mcp add --transport http klaviyo https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Klaviyo once connected?

Full read-write Klaviyo access lets Claude draft a campaign, set the content, choose the list or segment, and queue it for your approval before sending. It can create or update profiles, add them to lists, apply or remove tags, and define segment conditions, so audience prep and campaign setup happen where your customer data already lives.

  • Draft an email or SMS campaign with subject line and content, set the audience, and leave it for review
  • Create or update a profile, including custom properties and consent fields
  • Add or remove profiles from a list to build a target audience
  • Create or update a segment from a described set of conditions
  • Apply or remove tags to organize campaigns, flows, or lists
  • Schedule or send a prepared campaign after you approve it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Klaviyo access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Klaviyo API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Klaviyo changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Klaviyo connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Klaviyo connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Klaviyo account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Klaviyo's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Klaviyo?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Klaviyo account it signs in with. Revoking access is one click in Klaviyo.

More on the Klaviyo connector

Klaviyo connector for claude.aiMailchimp + Claude CodeActiveCampaign + Claude CodeMarketo + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us