Klaviyo MCP Server: How to Connect Claude or ChatGPT and What to Ask First
By Trayan Hristov · Thrivelia · 10 November 2026

The Klaviyo MCP server lets an AI assistant such as Claude or ChatGPT read your Klaviyo account and, if you allow it, change it. You ask in plain language. The assistant calls Klaviyo through a defined set of tools and reports what it found.
Connecting takes a few minutes. The decisions around the connection deserve more care: who authorises it, which account it reaches, whether the assistant can write, and how you check its answers. This guide covers setup for both clients, the settings I would change first and eight prompts with answers you can verify.
What the Klaviyo MCP server gives an assistant
MCP stands for Model Context Protocol, an open standard for connecting AI assistants to software. Klaviyo hosts a remote server at https://mcp.klaviyo.com/mcp. You authorise it with your Klaviyo login through OAuth, so the remote setup needs no API key. Klaviyo's connection guide lists the supported clients and settings.
The tools cover campaigns, flows, lists, segments, profiles, metrics, reports and templates. Some only read. Others create or change things. Klaviyo's guide for agencies says an assistant can schedule and send campaigns when the connector allows write actions and the user has permission. Treat the connection as account access with a chat window in front of it.
Check these requirements before you connect
Requirement | What Klaviyo documents | What to decide |
Klaviyo role | Owner, Admin or Manager on the account | Who authorises the connection, and for which accounts |
Claude | The listed Klaviyo connector, or a custom connector on a Pro, Max, Team or Enterprise plan | Whether you need the settings that only a custom connector accepts |
ChatGPT | The listed Klaviyo app, or a custom MCP server with Developer mode switched on | Who is allowed to turn Developer mode on |
Server URL | https://mcp.klaviyo.com/mcp with no trailing slash | Where the approved URL and its settings are written down |
On Claude Team and Enterprise plans, someone with permission to add custom connectors has to add the connector to the organisation first. Each person then connects their own Klaviyo login.
Connect Claude to Klaviyo
For one account with default settings, use the listed connector.
Open Settings, then Connectors, and choose Browse Connectors.
Search for Klaviyo and select Connect.
Approve Claude's access, then allow permissions for the Klaviyo account you are logged in to.
Start a new chat and ask the assistant to confirm the account name before anything else.
For several accounts, or to restrict what the assistant can do, choose Add custom connector. Give it a clear name that includes the brand and the access level. Paste the server URL with the settings from the section below, then connect and approve. In each chat, switch on only the connector you need. Menu names change, so follow Klaviyo's current steps if yours look different.
Connect ChatGPT to Klaviyo
ChatGPT has a listed Klaviyo app for a single account. For a custom setup, Klaviyo documents these steps.
Open Settings, then Apps, and switch on Developer mode under Advanced settings.
Choose Create app and enter a name.
Set the MCP Server URL to https://mcp.klaviyo.com/mcp and Authentication to OAuth.
Accept the acknowledgement and choose Create.
Approve ChatGPT's access, pick the account and allow permissions.
In a new chat, open the plus menu, choose More and select the server. Then ask it to confirm the account name.
Change these settings before the first real task
The custom URL accepts settings as query parameters. The listed Claude connector and the listed ChatGPT app do not accept them, which is the main reason to use a custom connector.
Setting | Effect |
read-only=true | Removes every tool that writes to the account |
core-tools-only=true | Limits the assistant to a smaller core set of tools |
disable-tools-with-user-generated-content=true | Removes tools that read text customers can write, such as profile and event data |
toolsets=profiles:read,campaigns:read | Grants access by resource, and by read or write |
company=example-brand | Labels the connector so several accounts stay separate |
A read-only connector uses this URL: https://mcp.klaviyo.com/mcp?read-only=true. Join further settings with an ampersand.
I would start every account read-only. Analysis needs no write access, and most of the early value is analysis. Add a second connector with write access when there is a defined job for it, such as drafting templates for review.
The user-generated content setting matters more than it sounds. Profiles and events can hold text a customer typed. An assistant reading that text can mistake it for an instruction. Klaviyo advises reviewing each tool call for this reason. If you do not need profile-level detail, switch those tools off.
Eight prompts to run first
Run these in order on a read-only connector. Each one has an answer you can check inside Klaviyo.
Prompt | Check it against |
Confirm which Klaviyo account you are connected to. Give the account name, time zone and currency. Do nothing else. | Account settings |
List every live flow with its trigger and number of messages. Flag any flows that share a trigger. | The Flows list, filtered to live |
For each live flow, report recipients, click rate and revenue for the last 30 days. State the conversion metric and the exact dates you used. | Flow analytics for the same dates |
Compare email campaigns sent in the last 90 days by click rate and revenue per recipient. Show the five weakest and what they have in common. | Campaign reports |
Which lists and segments trigger a flow? Which trigger none? | The trigger on each flow |
Render the first email in the welcome flow. List every link, discount code and personalisation tag in it. | The email preview |
Using the three best campaigns from the comparison, draft a brief for next week's campaign. Do not create anything in the account. | Your own judgement of the brief |
Tell me which of my requests you could not complete, and which answers rely on incomplete data. | The tool calls shown in the chat |
Three habits improve every prompt. Name the metric and the dates. Ask the assistant to say when data is unavailable so it does not estimate. Ask what it left out. For drafting inside Klaviyo's own assistant, see our Klaviyo Composer prompts.
Check the answer before you act on it
An assistant can read the right report and still describe it wrongly. Start with revenue. Flow and campaign reports show attributed revenue, which depends on the conversion metric and the attribution settings in the account. Our guide to attributed versus incremental revenue explains why that figure is not proof of extra sales.
Then check completeness. Long lists can come back in pages, and an assistant may summarise the first page as if it were everything. Ask how many items it read and compare that with the count in Klaviyo. Check the dates and the time zone too.
Klaviyo's own guide tells agencies to treat the output as a first draft and keep a person involved, especially for anything customers will see. I agree. Use the assistant to find where to look. Confirm the finding in the account before you change a flow. An audit checklist helps you confirm it the same way each time.
Decide who can let the assistant write
Write access changes the risk. According to Klaviyo's agency guide, a sent message cannot be undone, and campaigns that use A/B tests or Smart Send Time cannot be sent through the server at all. That still leaves ordinary campaigns within reach.
Keep analysis and building on separate connectors, one read-only and one with write access.
Name the person who approves each write action.
Set send and delete tools to require approval every time. Do not choose always allow for them.
Ask for drafts and templates, then review them in Klaviyo before anything is scheduled.
Record what was changed, by whom and when.
This is the same discipline as any release. A saved draft, an approved draft and a live message are three different states, and somebody has to own each step. I cover that in who owns the outcome when AI does the drafting.
Keep several Klaviyo accounts apart
Agencies and groups with more than one store need one connector per account. Klaviyo's guide suggests naming each connector after the account, adding the company setting to the URL and logging in to the right Klaviyo account before you connect. It also suggests one project per client.
At Thrivelia we keep a separate connector for each client account and name it after the client. Make the first prompt in any session a request to confirm the account. A report about the wrong brand is embarrassing. A draft created in the wrong account is worse.
Where Thrivelia fits
The server makes account analysis faster. It does not decide what a welcome flow should say to a first-time buyer, or whether a segment rule matches how your customers actually buy. That work needs product understanding, a clear brief and checks after launch.
We use AI assistants in audits and reporting, and we keep strategy, creative judgement and release checks with named people. If you want a second opinion on what your account data is telling you, start with the 30-minute revenue leak audit, look at our Klaviyo agency work or see the engagement options.
Questions about the Klaviyo MCP server
Do I need a Klaviyo API key?
Not for the remote server. It uses OAuth with your Klaviyo login. Klaviyo also publishes a local server that runs on your computer and uses a private API key. Web clients such as ChatGPT use the remote server.
Can the assistant send a campaign by mistake?
Only if the connector allows write actions and the action is approved. A read-only connector removes the tools that create, change or send. With write access, require approval for every send.
Should we use Claude or ChatGPT with Klaviyo?
Klaviyo documents both. Use the client your team already works in. If you are unsure, run the same three prompts in each and compare the answers with the figures in Klaviyo.

.png)



Comments