Klaviyo MCP + Claude AI: The Official Connector Setup Guide for Dubai E-commerce Brands

On 7 May 2026 Klaviyo announced an expanded integration with Anthropic that puts Klaviyo's data and tools inside Claude. Klaviyo says its MCP connector is available in Claude's connector directory, and the update adds a reporting tool called Query Metric Aggregates and support for interactive charts inside Claude. For a Dubai e-commerce brand, the practical meaning is that you can ask Claude about your flows and campaigns and get answers from your live account instead of exporting a spreadsheet first.

I have rewritten this post since it was first published, and the main correction is important. The first version described the connector as read access for reporting. Klaviyo's own documentation says otherwise: the permissions Claude asks for include read and write access, and the tool list includes tools that create, edit, delete and send. This version explains what that means, how to set the connector up, and how to limit it. I built it from Klaviyo's and Anthropic's documentation and did not run it on your account, so treat every setting below as something to test on a small question first.

Klaviyo MCP with Claude: Setup, Permissions and Safe Use

What the Connector Is

MCP is the Model Context Protocol, an open standard that lets an AI assistant call tools in another system. Klaviyo's MCP server gives an assistant such as Claude access to your Klaviyo account, for tasks that range from campaign creation to flow performance reports. Klaviyo hosts a remote server at https://mcp.klaviyo.com/mcp and recommends it over the local option. It signs you in with OAuth, so you approve access on Klaviyo's own login screen. It also works with other MCP clients, and Klaviyo's connection guide covers ChatGPT, Cursor and VS Code as well as Claude.

Klaviyo's available tools page lists more than 200 tools grouped by area: campaigns, flows, profiles, lists and segments, templates, catalogs, coupons, tags, webhooks, forms, reviews, reporting and more. Some categories are marked beta. That breadth is the reason the permissions section below matters.

The Correction: It Is Not Read-Only

Klaviyo's FAQ for the Klaviyo app for Claude says the OAuth scopes cover a broad set of resources with both read and write access, including "campaigns read and write" and "profiles read and write". The tools page backs that up. Besides the reading tools, it lists tools that:

• create, update, clone and delete campaigns, and send or cancel a campaign send;
• create, update and delete flows, including changing a flow's status;
• create, update, merge and subscribe or unsubscribe profiles, and request a profile deletion;
• create and change lists, segments, templates and catalog items.

One inconsistency is worth knowing about. Klaviyo's guide for agencies says campaign creation is supported now and that scheduling and sending campaigns end to end was expected to roll out in the third quarter of 2026. The tools page already lists a send tool. I cannot tell from the documents which is current, so look at the tools your own connector actually exposes rather than assuming, and treat sending as live until you have confirmed it is not.

The point of all this is simple. A connector that can change your account deserves the same care as giving a new team member admin access. Set it up so Claude can do what you need and no more.

Who Can Connect, and What You Need

Two requirements are documented. The Klaviyo user must have an Owner, Admin or Manager role, and the customer must have a Claude plan. On the Claude side, Anthropic's help article says custom connectors work on Free (limited to one), Pro, Max, Team and Enterprise plans. On Team and Enterprise plans, an organisation owner adds the connector first and members then connect individually. I found no separate Klaviyo plan requirement in the documents I opened, so ask Klaviyo if you have doubts about your tier.

Setting It Up

1. Log in to the right Klaviyo account first. Klaviyo's guide for agencies tells you to confirm that you are logged in under the account you want to connect before you approve anything. If you manage more than one account, this step decides which one Claude sees.

2. Add the connector in Claude. Open the connectors area, browse the directory and choose Klaviyo. Anthropic's connector help page places this under Customize, then Connectors, while Klaviyo's page says Settings, then Connectors, so look for Connectors in either place. Klaviyo calls the listed connector "the simplest way" to use Klaviyo in Claude, and it suits a single account.

3. Read the permissions screen. This is the step people click through. Anthropic advises reviewing the scopes requested and denying access you do not need, and it warns that you should only connect to servers built by organisations you trust. Klaviyo is the vendor here, but the read and write scopes above are what you are approving.

4. Turn the connector on in the conversation. In a chat, use the plus button or type a slash and switch Klaviyo on. Connectors are chosen per chat, so a conversation without it switched on cannot reach your account.

5. Set tool permissions. Anthropic lets you set each tool to Always allow, Needs approval or Blocked, and its custom connector guide describes a Search and tools menu where you can disable tools you do not want. Klaviyo's agencies guide recommends blocking, or always requiring approval for, every tool that writes or deletes data. I would do that before your first real question. Anthropic does not say whether write actions ask for approval by default, so do not assume they do.

6. Test with three questions you can check. Ask how many flows are live, what your list growth was over the last 30 days, and what one campaign's open rate was. Then compare each answer with the Klaviyo dashboard. It takes five minutes, and it tells you whether the connector is on the right account and reading the right dates.

How to Make It Read-Only

The listed connector in the directory takes no options. Klaviyo's connection guide says query parameters are not available with listed connectors, so limiting the tools means adding a custom connector with the same server address plus parameters. The documented ones are:

• read-only=true disables any tools that can perform write actions on your Klaviyo account;
• toolsets filters by API scope, for example profiles:read,campaigns:read;
• core-tools-only=true limits the server to about 40 core tools;
• disable-tools-with-user-generated-content=true stops the model interpreting user-generated content (more on that below);
• beta=true switches on experimental tools, which I would leave off.

For a reporting-only connector, the address would look like https://mcp.klaviyo.com/mcp?read-only=true. Klaviyo does not show several parameters combined in one address, and I have not tested it, so if you combine them, open the tool list afterwards and confirm that the write tools are gone. If you prefer the local server, Klaviyo documents a READ_ONLY setting, which needs a private API key. Keep that key in a password manager, as Klaviyo advises, not in a plain text file.

One practical note from Klaviyo: free Claude Desktop users may run into context window problems with a large set of tools, and switching tools off selectively helps. A smaller toolset is also easier to review.

If You Manage Client Accounts

Klaviyo's guide for agencies is specific. Create a custom connector for each client account, name it clearly, for example "Klaviyo - [Account Name]", and use the address with the company parameter, in the form https://mcp.klaviyo.com/mcp?company=example-company. You need an Owner, Admin or Manager role on each account. The guide also suggests a separate Claude project for each client, with standing instructions that name the account. The mistake to guard against is asking about "my flows" while the wrong client is connected, so make the account name part of every report you save.

Reporting Questions That Work Well

The reporting tools are the safest place to start. The reading tools include campaign and flow reports, segment and form queries, and Query Metric Aggregates. Klaviyo's documentation for that endpoint says it aggregates event data grouped by flows, campaigns, lists and similar objects, supports count, sum and unique measurements, and groups by hour, day, week or month. It also sets some limits that shape your questions:

Name the time zone. A time zone must be specified for the query. For a UAE store, say which one you report in so that a day means the same in Claude as it does on your dashboard.

Keep each question within a year. The maximum date range is one year, so a comparison across two Ramadan seasons needs two separate queries that you compare yourself.

Keep filters simple. Only one filter can be used in addition to the date range. Ask for the breakdown you want, then filter the result in conversation.

Klaviyo's own example prompts give a good sense of the intended use: a weekly digest of campaign and flow performance with wins, underperformers and next steps, an audit of active flows that flags any with open rates under 20% or clear drop-off points, and a ranking of the top revenue-driving flows and campaigns over 60 days. Klaviyo describes the weekly digest as a Claude Cowork task, and says Cowork can run tasks like these in one unattended session. The same page describes MCP Apps, which lets partners build interactive charts and dashboards that render inside Claude.

For a Dubai brand, these are the uses I would try first, as suggestions rather than results I have measured. Compare your abandoned cart flow with a browse abandonment flow, step by step. Check flow performance before and after a Ramadan or Eid campaign, with the two periods queried separately. Draft a plain-language monthly summary of email performance, and check every figure in it against the dashboard before it goes to anyone else.

Data and Security

Three points are worth raising with whoever owns your customer data.

Customer details can be reachable. Klaviyo's FAQ says PII such as email addresses and phone numbers may be accessible depending on how your account is configured, and that data processing is governed by your existing agreements with Anthropic. Anthropic's connector guide adds that connector providers may process data on their own infrastructure under their own terms, possibly outside the US. If you work under UAE data protection rules, my PDPL guide for marketers explains what the law says and what I could not verify. Whether sending customer data through an AI assistant fits your obligations is a question for your lawyer.

Customer-written text is a risk. Some tools return user-generated content, for example profiles, events and reviews, and Klaviyo flags them. Anthropic warns that a malicious source can include hidden instructions that try to make Claude do something unintended. Text written by customers is exactly the kind of content that could carry such instructions. If you do not need those tools, use disable-tools-with-user-generated-content on a custom connector, and keep write tools on Needs approval.

Keep a person in the loop. Klaviyo's own guidance is to treat the output as a strong first draft and keep a human in the loop for anything customer-facing. Send nothing from an AI draft that no one on your team has read.

What to Do This Week

1. Check your role. You need Owner, Admin or Manager on each Klaviyo account you plan to connect.

2. Decide what you need. If the goal is reporting, plan a read-only custom connector from the start.

3. Connect and limit. Add the connector, then set every write and delete tool to Needs approval or Blocked.

4. Run the three check questions and compare with the dashboard.

5. Write down one reporting question you ask every month, and save the wording so the answer is comparable next time.

Frequently Asked Questions

Next Step

If you want a second opinion on how your email reporting connects to your ad spend, start from my Google Ads management service page and tell me you want the email side included in the review. Bring the questions you would ask Claude about your Klaviyo account, and I can check whether the answers would change what you do.

Related reading:

• Meta Ads MCP + Claude AI: Official Connector Setup Guide for Dubai (2026)
• 15 Practical Ways to Use Ahrefs MCP for Smarter, Faster SEO (Dubai Edition)
• UAE PDPL Compliance for Marketers: What Your Tracking Pixels Actually Need in 2026