How to connect multiple Klaviyo accounts to Claude
Klaviyo shipped an official MCP server for Claude, and it's genuinely useful. Ask Claude how a campaign did, pull flow metrics, dig into segments, all in plain language.
Then you hit the wall: each connector binds to one Klaviyo account. There's no account switcher inside Claude. If you manage one store, that's fine. If you manage three stores or ten clients, you're stuck editing config files and juggling API keys every time you want to look at a different account.
We manage multiple Klaviyo accounts at our agency, so we hit this wall in week one. Here's every way around it.
Option 1: Multiple connector entries (the config-file route)
If you use Claude Code or another MCP client with a config file, you can duplicate the Klaviyo MCP entry once per account, each with its own name and API key. It works. It's also tedious to set up, tedious to maintain, and Claude treats each account as a separate tool, so "compare my accounts" questions don't work well. You ask about accounts one at a time.
In the Claude apps (desktop and web), you can add the Klaviyo connector more than once, but the experience is the same: separate connectors, separate conversations in practice, no cross-account view.
Option 2: Blend the data upstream (BI tools)
Reporting tools like Porter can blend several Klaviyo accounts into one data source, and some of them expose that to Claude. This solves the comparison problem but adds a paid tool, a modeling step, and another place where numbers can drift from what Klaviyo shows.
Option 3: Aggregate the accounts behind one connector (what we built)
This is the approach we took with RaziCo Dash AI, and yes, we built it, so read accordingly.
Dash is a free Klaviyo dashboard. You connect each of your Klaviyo accounts to it with read-only API keys. Dash then exposes one MCP endpoint to Claude. Add that single connector and Claude can see every account at once:
- In Dash, connect your Klaviyo accounts (Settings → Klaviyo accounts). Read-only keys, so nothing can be sent or changed.
- In Claude, go to Settings → Connectors → Add custom connector and paste the Dash MCP URL. One paste, done.
- Ask away: "compare my Klaviyo accounts by revenue this month," "which account has the worst deliverability," "which client is missing a win-back flow."
It works in Claude chat, Claude Code, and Cowork. Everything is read-only and scoped to your own accounts, so Claude can read your metrics but can never touch a campaign.
Dash is free while it's in beta: dash.razico.co
Which route should you take?
One Klaviyo account: just use Klaviyo's official connector. It's good.
Two or more accounts and you live in config files: multiple MCP entries will limp along.
Two or more accounts and you want cross-account questions to actually work: aggregate behind one connector. Ours is free, takes about two minutes, and if it saves you one config-file edit it's paid for itself.
FAQ
Does this give Claude write access to Klaviyo? No. Dash connects to Klaviyo with read-only keys, and the MCP itself is read-only. Claude can look, it can't touch.
Do rate limits still apply? Klaviyo's API rate limits always apply. Dash syncs your data on its own schedule in the background, so most Claude questions are answered from already-synced data instead of hammering the Klaviyo API live.
Can my team use the same connector? Yes. Invite them to your Dash account (editor or viewer) and they can set up the same connector against their own login.