If you need to connect multiple Klaviyo accounts to Claude, custom MCP connectors can turn a frustrating account-switching routine into a single, organized AI workspace. Instead of disconnecting one brand whenever you need to inspect another, you can authorize each Klaviyo account once, name it clearly, and choose the right connection for the job.

The original Klaviyo tutorial behind this guide focuses on the basic mechanics: add a custom connector in Claude, give it a distinct name, add the relevant account as a query parameter, approve permissions, and repeat for every account. That is the correct starting point. But the more useful question for marketers, agencies, and ecommerce operators is what happens after the connectors appear in Claude: how do you prevent client mix-ups, keep permissions sensible, get reliable reports, and turn a collection of integrations into a repeatable workflow?

Klaviyo’s current documentation explicitly recommends a custom connector when you are connecting several Klaviyo accounts, while its listed Claude connector is the simpler option for a single account. (developers.klaviyo.com) This guide explains the setup, the operating model around it, and the decisions that matter once Claude can access more than one store.

Why multiple Klaviyo accounts in Claude matter

Managing one Klaviyo account is usually straightforward. The workflow becomes much more fragmented when a business runs separate regional storefronts, when an operator oversees multiple brands, or when an agency supports several clients. In each case, reporting, flow reviews, campaign planning, and audience analysis can involve repetitive logins, exports, tabs, and handoffs.

A multi-account Claude setup does not merge those accounts. That distinction matters. It gives one Claude user interface access to multiple separately authenticated Klaviyo environments, with each connector pointing to its own account. The goal is convenience and speed, not the creation of one shared customer database.

That makes the setup especially useful for:

Agencies that prepare recurring client performance summaries, audits, and campaign drafts.
Multi-brand operators with separate Klaviyo instances for distinct product lines or storefronts.
International teams running different accounts for regions, currencies, languages, or compliance requirements.
Franchise, marketplace, or portfolio businesses where local teams need separate marketing operations but central stakeholders need a faster reporting layer.
Consultants who have authorized access to client accounts and need to move from analysis to recommendations quickly.

Klaviyo describes its MCP server as a bridge between its APIs and AI clients such as Claude, enabling tasks that range from flow-performance reporting to campaign creation. (developers.klaviyo.com) In plain English, Claude can use the connector to retrieve information and, depending on the permissions and available tools, help prepare or execute work grounded in the selected Klaviyo account.

The productivity gain is not simply that Claude can answer questions in natural language. The larger gain is reduced context switching. A marketer can move from “Which abandoned-cart flow is underperforming?” to “Draft three test concepts for the weakest email” without manually exporting data into a separate AI prompt.

What the Klaviyo Claude integration actually is

The technical foundation is the Model Context Protocol, or MCP. MCP is an open protocol designed to let AI applications connect to external data sources and tools in a more structured way. In this case, Klaviyo runs an MCP server and Claude acts as the client that can use the tools exposed by that server. (developers.klaviyo.com)

This is different from pasting campaign metrics into a chat window. A pasted spreadsheet is static, incomplete, and easy to misinterpret. An MCP connection can provide Claude with access to current account context when it makes a request through the connector.

Listed connector versus custom connector

For one account, the listed Klaviyo connector is the lowest-friction route. Klaviyo’s guide says to find Klaviyo in Claude’s connector directory, connect it, approve Claude access, and then allow the relevant Klaviyo permissions. (developers.klaviyo.com)

For several accounts, use a custom connector for each account. The custom version is important because it lets you create a separate, recognizable entry and identify the intended Klaviyo company in the remote server URL. That means a US store, an EU store, and five client accounts can coexist instead of replacing one another.

Why the query parameter is more than a technical detail

The original tutorial correctly emphasizes adding the account name as a query parameter. Klaviyo’s current developer documentation uses this pattern:

https://mcp.klaviyo.com/mcp?company=example-company

The company value tells the remote MCP server which Klaviyo account the connector is meant to represent. (developers.klaviyo.com) It is not a substitute for authentication: you still need to sign in to the correct Klaviyo account and approve access. Think of it as an account-selection and organizational layer that makes multi-account use feasible.

This design also explains why each connection must be authorized independently. Claude should not silently inherit access from one client or storefront to another. Every separate Klaviyo account has its own permissions, users, data, and operational consequences.

Requirements before you connect multiple Klaviyo accounts to Claude

The workflow is simple, but access requirements are not optional. Before setting up connectors, make sure you have the right plan, the right role in every Klaviyo account, and a naming plan that will still make sense after the tenth connection.

Klaviyo’s current documentation says multi-account custom connectors are available in Claude and Claude Desktop for Pro, Max, Team, and Enterprise users. (developers.klaviyo.com) Its agency guide also notes that users need an Owner, Admin, or Manager role in each Klaviyo account they intend to connect. (help.klaviyo.com)

Plan and workspace considerations

The tutorial notes an important governance distinction: on Team and Enterprise workspaces, owners or primary owners may need to add connectors before other users can use them, whereas individual paid users can generally manage their own custom connectors. Workspace controls can evolve, so teams should treat the current Claude admin settings and their organization’s connector policy as the source of truth before rolling the setup out broadly.

The practical point is simple: do not promise your team that everyone can self-connect every client account until an owner has confirmed the workspace rules. Connector governance is a feature, not needless friction. It helps prevent staff from adding unreviewed data connections to a shared AI environment.

Access checklist

Before starting, verify the following for every account:

You have a compatible paid Claude plan or an organization-managed Claude workspace with connector access.
You are an Owner, Admin, or Manager in the target Klaviyo account.
You can sign in to the exact Klaviyo account during authorization.
You know the correct company identifier to use in the connector URL.
You have decided whether the connector should have read-only access or whether it needs supported write capabilities.
You have a clear connector name that identifies the brand, market, or client.
You know who is responsible for reviewing AI-generated customer-facing work before it is sent.

Skipping the last two steps is where many otherwise successful implementations fail. A connector that technically works but is ambiguously named or loosely governed creates a new source of error rather than eliminating one.

Step-by-step: connect multiple Klaviyo accounts to Claude

The original video’s workflow is short. The best way to follow it is to set up one account first, test it, then duplicate the process with a consistent naming format.

1. Start in Claude’s connector settings

In Claude, open Customize, then choose Connectors. Select Add, followed by Add custom connector. Klaviyo’s agency help guide documents the same overall sequence for connecting client accounts. (help.klaviyo.com)

If you are using Claude Desktop rather than the browser interface, the layout may vary slightly, but the purpose is the same: create a new remote MCP connection that Claude can later invoke.

2. Name the connector for a human, not a database

Do not name every connection “Klaviyo.” That is workable for one account and unworkable for several.

Use a format that tells you, at a glance, which store and operating context you are about to query. For example:

Klaviyo — Northstar US
Klaviyo — Northstar EU
Klaviyo — Acme Client — Retention
Klaviyo — Harbor Coffee — Production
Klaviyo — Harbor Coffee — Sandbox

The original tutorial uses the pattern Klaviyo-Beantown; Klaviyo’s current documentation similarly recommends including the account name, such as Klaviyo - Example Company. (developers.klaviyo.com)

A good connector name performs three jobs. It reduces the odds of querying the wrong account, makes prompts easier to write, and creates an audit-friendly record for future teammates. Add a market or environment label when it is relevant. “Northstar” is not enough if Northstar has US, UK, and development accounts.

3. Add the remote MCP server URL with the account parameter

Enter the Klaviyo remote MCP server URL, including the account-specific company query parameter:

https://mcp.klaviyo.com/mcp?company=example-company

Replace example-company with the relevant company value for that account. Klaviyo notes that spaces in names should be encoded properly, and its help guide specifically advises confirming that you are logged in to the correct Klaviyo account before continuing. (help.klaviyo.com)

This is the point where a deliberate setup pace pays off. If you manage several similar brands, open the intended Klaviyo account in a separate browser tab first. Check its account identity, then return to Claude and complete authorization. Do not rely on memory or whichever account happened to be active from an earlier session.

4. Add, connect, and review permissions

Select Add, then Connect. Claude will show the permissions associated with the connection, and Klaviyo will prompt you to authorize access to the target account.

Read the permission screen. It is tempting to approve quickly because you have already decided to use the integration, but permissions are the actual boundary between a useful assistant and an overly broad one. If your immediate objective is reporting and audit work, assess whether a read-only configuration can accomplish it.

Klaviyo’s agency guidance specifically recommends controlling write access with read-only settings and keeping a human in the loop for customer-facing output. (help.klaviyo.com) That is sound operational advice even when the team trusts Claude and the connector. Drafts, audience logic, campaign content, and final sends should not all carry the same review threshold.

5. Test the connector with a low-risk prompt

Do not begin by asking Claude to create or modify anything. First, test whether it can retrieve a small, easily verified fact.

Try prompts such as:

“Using Klaviyo — Northstar US, list the three most recent campaigns and their send dates.”
“Using Klaviyo — Acme Client — Retention, summarize last month’s email revenue and click rate. State the date range you used.”
“Which flows in Klaviyo — Harbor Coffee — Production have had the highest conversion rate in the last 30 days?”

Klaviyo itself gives examples including campaign performance over the last 30 days, top conversion flows, and drafting a campaign for a sale. (developers.klaviyo.com) The difference is that your first prompt should be easy to compare against the Klaviyo interface manually. Validation builds confidence and exposes account-selection mistakes early.

6. Repeat the process, one account at a time

Repeat the steps for every additional Klaviyo account. Never assume that the next connector is using the correct active login. Confirm the account, authorize it, then test it before moving on.

Once complete, you should see a connector list that is readable without opening any settings. If it looks like a wall of identical “Klaviyo” entries, rename them before doing real work.

Build an account architecture, not a connector pile

Adding connectors is easy. Operating them safely requires a small amount of information architecture.

Klaviyo recommends creating a separate connector and a separate Claude project per client, so client data and context remain clearly separated. (help.klaviyo.com) That recommendation is especially valuable for agencies, but it is just as useful for internal teams with multiple brands or regions.

Use one Claude project per account or brand

A Claude project can hold the instructions, reference files, voice guidance, reporting definitions, and conversation context relevant to one account. Pairing projects with connectors reduces the chance that a prompt about one brand gets mixed with style guidance or historical analysis from another.

For example, an agency could create:

Project: Acme Outdoor — US with only the Acme US connector, brand voice guidance, promotion calendar, and approved reporting definitions.
Project: Harbor Coffee — UK with the UK connector, local compliance notes, product catalog summaries, and regional campaign history.
Project: Agency Operations with no client connector at all, used for generic process documentation, proposal drafting, and template creation.

This is not merely tidiness. It limits the amount of irrelevant context Claude has to reason over and makes it more obvious when a user is working in the wrong place.

Establish a connector naming convention

A useful convention is:

Klaviyo — [Client or Brand] — [Region] — [Environment]

Examples:

Klaviyo — Atlas Skin — US — Production
Klaviyo — Atlas Skin — EU — Production
Klaviyo — Atlas Skin — US — Sandbox

The format is intentionally repetitive. Consistency beats cleverness in a list that will be used during busy reporting cycles. If your organization manages clients, place the client name first. If teams usually think by geography, put the region first. What matters is that the pattern is predictable.

Keep a simple authorization register

For high-value accounts, create a lightweight internal register containing the connector name, account owner, authorization date, intended permissions, and review date. This does not need to be a complex security system. A shared internal document is enough for many teams.

The register becomes useful when a contractor leaves, a client revokes agency access, an account is renamed, or a new team member asks which connector is safe to use. It also prevents “orphaned” connections that continue to exist because nobody remembers why they were created.

The best workflows after the connection is live

The central benefit of multi-account access is not the ability to ask the same question repeatedly. It is the ability to standardize repeatable marketing operations while keeping each account’s context separate.

Klaviyo says its enhanced MCP server supports real-time interaction with Klaviyo data through its APIs and can be used for creating, reading, and updating data, subject to the available tools and permissions. (klaviyo.com) That opens useful workflows, but the highest-return use cases tend to begin with analysis and drafting rather than autonomous execution.

1. Weekly performance digests

Create a standard prompt for each account that asks for:

the date range used;
sends and revenue by campaign;
top and bottom campaigns by a defined metric;
key flow changes or anomalies;
a short list of recommended next actions;
any assumptions or missing data.

A standard structure matters because it makes outputs comparable. If one report uses click rate and another uses conversion rate, an agency director cannot meaningfully compare the two without revisiting the data definitions.

A stronger prompt is: “Using the selected account only, create a weekly email performance summary for August 1–7. Separate campaign and flow metrics. Flag results that materially changed versus the prior seven days. Do not infer causes unless the data supports them; label recommendations as hypotheses.”

That last instruction is important. Claude can summarize data rapidly, but it can also make plausible-sounding causal claims. A lower open rate might reflect subject lines, audience changes, deliverability, a seasonal event, send timing, or incomplete data. Treat recommendations as informed hypotheses until validated.

2. Flow audits across a portfolio

For agencies, flow audits are a natural multi-account workflow. Use a fixed audit rubric across clients: welcome series, abandoned cart, browse abandonment, post-purchase, winback, consent capture, suppression logic, content freshness, and measurable conversion performance.

Claude can help produce a first-pass checklist and organize findings. The human operator should then verify the actual configuration and decide what changes are appropriate. The point is not to let AI “grade” every client without scrutiny; it is to eliminate the repetitive initial inspection that consumes strategist time.

A practical prompt: “Review the active flows in this account and produce an audit table with flow name, trigger, number of messages, last meaningful update, primary conversion goal, potential issue, and recommended next review. Do not make changes.”

3. Cross-account benchmarking—with careful definitions

Multi-account access makes cross-client or cross-store comparisons tempting. It can also make them misleading.

Compare only accounts with compatible definitions and business conditions. A skincare brand with a 45-day consideration cycle should not be judged against a low-priced consumable brand purely on 30-day email revenue. Likewise, regions may have different list ages, consent practices, promotional calendars, currencies, and attribution settings.

Use cross-account reviews to surface questions, not to announce universal winners. For instance: “Which accounts saw a decline in repeat-purchase email revenue quarter over quarter, using each account’s native currency and the same reporting period?” Then ask follow-up questions inside each account rather than assuming all differences have one cause.

4. Campaign and experiment briefs

When a connector supplies current performance context, Claude can produce better briefs than a generic AI chat. It can be instructed to use the best-performing themes from the selected account, identify engagement patterns, and draft testable campaign concepts.

Keep the workflow staged:

Ask for analysis of prior performance.
Ask for three hypotheses based on that analysis.
Ask for campaign concepts and variants.
Have a marketer verify claims, product details, discounts, compliance language, and brand voice.
Only then create or schedule work through approved processes.

This sequence protects against a common mistake: jumping directly from an AI-generated observation to customer-facing output without an editorial or commercial review.

Permissions, privacy, and the human review layer

Connecting an AI assistant to marketing data is consequential. Klaviyo accounts can contain customer profiles, behavioral events, campaign performance, segmentation logic, and operational details. Convenience must be matched with least-privilege access and clear ownership.

Klaviyo’s documentation says the remote MCP server is available only to users with Owner, Admin, or Manager roles, and its agency guide encourages read-only controls and human review for customer-facing content. (developers.klaviyo.com) These are useful guardrails, but every company should add its own policies.

Start read-first whenever possible

If the immediate need is reporting, analysis, or audit preparation, do not give the workflow broader capabilities than it needs. Start with read-oriented usage, prove the process, then decide whether approved users need to create or update objects through the connector.

This approach has several benefits:

It limits the blast radius of a misunderstanding or prompt mistake.
It lets the team learn how the connector represents data before acting on it.
It clarifies which tasks truly benefit from direct write access.
It makes client and stakeholder approval easier for agencies.

Avoid placing sensitive data in prompts unnecessarily

A connector may already be able to retrieve relevant account information. There is rarely a good reason to paste raw customer exports, personal details, or unrelated credentials into a chat prompt as well.

Ask for aggregate analysis where possible. Use role-based access in Klaviyo. Remove connectors when a contractor or agency relationship ends. And remember that an account-level authorization should be reviewed with the same seriousness as any other vendor or automation integration.

Require approval before external action

A useful internal rule is: Claude may analyze, summarize, structure, and draft; a designated human approves changes that affect customers, audiences, subscriptions, offers, or sending activity.

That rule does not slow a mature workflow down. It focuses human time where judgment matters: factual accuracy, positioning, legal requirements, brand safety, audience selection, and commercial intent.

How to write prompts that avoid account confusion

The connector list is only one safeguard. Your prompts should also make account selection explicit.

Instead of asking, “How did our campaigns do last month?” ask, “Using Klaviyo — Atlas Skin — EU — Production only, summarize email campaign performance for May 2026.” Account names are a cheap but effective guardrail.

A reliable prompt template

Use this structure for recurring work:

Account: [exact connector name]
Task: [analysis, audit, draft, comparison]
Date range: [absolute dates]
Metrics: [define the metrics that matter]
Output format: [table, bullets, executive summary]
Constraints: [do not modify anything / flag uncertainty / use account data only]
Review request: [what a human should verify]

For example:

Account: Klaviyo — Harbor Coffee — US — Production
Task: Analyze welcome-flow performance.
Date range: April 1, 2026 through June 30, 2026.
Metrics: Delivered, open rate, click rate, placed-order conversion rate, and attributed revenue.
Output format: A table by message plus five prioritized recommendations.
Constraints: Do not change flow settings. Distinguish observed facts from hypotheses.
Review request: Identify any recommendation that requires deliverability, legal, or merchandising approval.

Absolute dates reduce ambiguity. So do defined metrics. “Last month” can be interpreted differently around month boundaries, while “April 1, 2026 through April 30, 2026” is unambiguous.

Ask Claude to state its sources and assumptions

When working with performance data, ask Claude to identify the account, date range, metrics, and filters it used. This makes it easier to catch a wrong connector, a partial data pull, or an apples-to-oranges comparison.

You should also ask it to label unknowns rather than fill them in. The useful behavior is not “always give an answer.” It is “give a useful answer, explain what it is based on, and surface what needs human verification.”

Common problems and how to fix them

Most multi-account connection issues are operational, not deeply technical. They usually come down to a wrong active login, a vague connector name, insufficient account permissions, or a mismatch between what the user expects and what the connector can access.

“I connected the wrong Klaviyo account”

This is the most important failure to catch early. Remove or reauthorize the connector, then begin again while logged in to the intended Klaviyo account. Rename the corrected connector clearly and run a low-risk verification prompt that confirms recognizable account details.

Do not simply rename a questionable connector and assume the authorization follows the new label. The name is for humans; the underlying connection and authentication determine which account Claude can access.

“The connector is there, but Claude cannot answer my question”

First, test with a narrow, documented type of request: recent campaigns, a defined flow, or performance over a specific period. Klaviyo documents examples around campaigns, flows, and campaign creation, so start there rather than with a vague strategic question. (developers.klaviyo.com)

If retrieval still fails, verify your Klaviyo role, the connector authorization, the active account session, and whether the task requires access or a tool that is not available in your configuration. A concise reproducible prompt is far easier to troubleshoot than a long conversation containing several unrelated tasks.

“Claude’s answer does not match our dashboard”

Do not assume either system is automatically wrong. Compare date ranges, time zones, attribution settings, filters, campaign status, currency, and the precise metric definition. Ask Claude to restate those inputs before treating the output as a decision-ready number.

This is why a verification step belongs in every serious reporting workflow. AI can accelerate analysis, but it should not become an unexamined second source of truth. For executive reporting, reconcile important totals against the native Klaviyo view or your established BI reporting source.

“We have too many connectors now”

Archive or remove connections that are no longer needed, standardize the names of active ones, and group work into separate Claude projects. If an agency has dozens of clients, resist the urge to use one giant general-purpose project. The current Klaviyo agency guidance specifically recommends a separate project per client for clearer context isolation. (help.klaviyo.com)

What this means for agencies and multi-brand teams

The tutorial’s message is deceptively simple: you no longer need to disconnect and reconnect whenever you move between accounts. For an individual consultant, that is a welcome convenience. For an agency, it can become a capacity multiplier—if the workflow is standardized.

Klaviyo’s agency guide frames multi-account MCP use around faster reporting, audits, content creation, and cross-client work, while emphasizing separate connectors and projects to keep data distinct. (help.klaviyo.com) The opportunity is to transform recurring work into reusable operating procedures rather than asking every strategist to reinvent prompts and reports for each client.

Build reusable internal playbooks

An agency can maintain approved prompt templates for:

weekly performance summaries;
monthly executive reports;
flow audit scorecards;
campaign postmortems;
seasonal launch briefs;
churn and reactivation reviews;
localization checks for regional accounts.

Each playbook should include the expected connector name, metric definitions, output structure, review owner, and escalation path. This keeps AI use closer to a documented process than an improvised experiment.

Separate analysis velocity from execution authority

The best near-term use of a multi-account Claude setup is not necessarily autonomous marketing. It is faster movement from data to an informed human decision.

Klaviyo has expanded its Claude-related MCP capabilities to support richer reporting and agentic workflows, including direct metric aggregation and interactive app experiences in Claude. (klaviyo.com) That direction makes governance more important, not less. As tools become more capable of moving from insight to action, teams need clearer rules for what is automatic, what is suggested, and what always requires approval.

The bigger shift: from dashboards to conversational marketing operations

Klaviyo made its enhanced MCP server generally available in August 2025 and positioned the remote server as a way to give AI tools access to Klaviyo data without adding a complicated new layer to the marketing stack. (klaviyo.com) In May 2026, the company described broader Claude integration that extends into Claude Chat and Cowork-style workflows, with use cases such as reports, insights, and campaign-ready assets. (klaviyo.com)

The key word is not “chat.” It is “operations.” A chat interface is valuable when it helps someone retrieve a number faster. It becomes strategically valuable when it supports a consistent process from performance review to prioritized recommendation to approved execution.

For creators and founders, that can mean less time navigating dashboards and more time deciding what to test. For marketers, it can mean a faster first draft of an audit or campaign brief. For agencies, it can mean reclaiming low-value reporting hours without pretending that client strategy can be fully automated.

The teams that benefit most will be the ones that combine three things: clean account structure, precise prompts, and human review. The connector is the access layer. The operating system around it is where the real advantage comes from.

Conclusion

To connect multiple Klaviyo accounts to Claude, create one clearly named custom connector per account, use the account-specific company query parameter, authorize each account separately, and test every connection with a low-risk reporting prompt. That is the technical setup.

The higher-value setup is organizational: use separate Claude projects for clients or brands, keep permissions as narrow as practical, standardize prompts, reconcile important metrics, and require human approval before customer-facing or account-changing actions. Done this way, multi-account Claude access is not just a shortcut between dashboards. It becomes a durable workflow for faster, better-governed marketing operations.

FAQ

Can I connect more than one Klaviyo account to Claude?

Yes. Klaviyo recommends a custom Claude connector for each account when you need to work with several Klaviyo accounts. Give every connector a unique name and use the appropriate company query parameter in the remote MCP server URL. (developers.klaviyo.com)

Which Claude plans support multiple custom Klaviyo connectors?

Klaviyo’s current documentation lists Pro, Max, Team, and Enterprise plans for custom connector use in Claude and Claude Desktop. Team and Enterprise users should also check their workspace owner and admin policies before attempting setup. (developers.klaviyo.com)

Do I need to log in and approve access for every Klaviyo account?

Yes. Each Klaviyo account requires its own authorization. You should confirm that you are signed in to the intended account before approving permissions, then test the connector with a simple request to verify it points to the correct store or client.

Should agencies create one Claude project for all clients?

No. A separate Claude project per client or account is the safer and more organized approach because it keeps connector use, account context, instructions, and conversations distinct. Klaviyo’s agency guidance specifically recommends separate connectors and projects for client work. (help.klaviyo.com)

Is it safe to let Claude make changes in Klaviyo?

It can be useful, but it should be governed. Start with analysis and read-oriented workflows where possible, review permissions carefully, and require human approval for customer-facing content, audience changes, campaign actions, or anything with commercial, legal, or deliverability impact. (help.klaviyo.com)

How to Connect Multiple Klaviyo Accounts to Claude