Klaviyo MCP Server: What It Can Do, How to Connect It, and What to Lock Down

Klaviyo runs an official MCP server at https://mcp.klaviyo.com/mcp. Connect it to Claude, ChatGPT, Cursor or VS Code and the assistant can pull campaign and flow reports, read segments and profiles, and also create, schedule, send and delete things in your account. Klaviyo's tool list has 309 tools, and 159 of them can change data. If you only want answers, add ?read-only=true to the URL through a custom connector before you ask the first question.

Setup steps, tool counts and settings below come from Klaviyo's developer docs for the MCP server and its agency guide, read on November 12, 2026.

Watch the 4-minute walkthrough

Which Klaviyo MCP server is best?

If you want to work inside a Klaviyo account, use Klaviyo's official server. The remote URL at https://mcp.klaviyo.com/mcp signs in with OAuth, so no private API key sits in a config file. Turn on ?read-only=true through a custom connector unless you actually need to create, send or delete. Klaviyo also ships the same server as a local package, uvx klaviyo-mcp-server, which runs on your machine with a private key and READ_ONLY=true. Use the local package when a client can't reach the hosted URL, not as a second product.

Community and GitHub servers that use the same name are not Klaviyo's. They usually want a private API key, their tool lists don't match Klaviyo's 309-tool catalog, and some third-party hosts route that key through their own infrastructure. A fork can make sense only if you need a tool the official server still doesn't expose and you accept running unvetted code against a key. For client accounts, that tradeoff is rarely worth it.

Finsi's MCP server is a different job. It does not wrap the Klaviyo API and it can't send a campaign or edit a flow. It gives Claude or ChatGPT one read-only set of verified numbers from Shopify, Klaviyo, Meta and GA4, and every call is logged. Use it when the question spans those sources (for example, whether a win-back flow paid for its discount), or when you want an agent to propose a change and wait for approval before anything goes out. Setup is at Finsi MCP.

Remote or local server

Klaviyo offers the same server two ways and recommends the remote one.

Remote server (recommended) Local server
How it runs Hosted by Klaviyo at https://mcp.klaviyo.com/mcp On your machine with uvx klaviyo-mcp-server@latest
Sign-in OAuth in the browser A Klaviyo private API key
Who can connect Klaviyo users with the Owner, Admin or Manager role Anyone holding a private key with the required scopes
Clients Claude, ChatGPT, Cursor, VS Code, any client that supports remote servers Claude Desktop, Cursor, VS Code (Klaviyo points web clients like ChatGPT to the remote server)
Read-only switch read-only=true query parameter READ_ONLY=true environment variable

The remote server uses Streamable HTTP and OAuth with dynamic client registration, so most MCP clients connect with just the URL. The local version needs a private API key, and Klaviyo's full scope list for it includes full access to campaigns, events, profiles, segments, subscriptions and templates. That key sits in a config file on someone's laptop. Klaviyo suggests keeping it in a password manager and launching with uvx --from klaviyo-mcp-server@latest run-claude (or run-cursor) so it's never saved in plaintext; that launcher supports macOS and Windows only.

For a brand team, the remote server is the easier one to manage. Access follows the person's Klaviyo role, and there's no long-lived key to rotate.

Connect it to Claude

For a single Klaviyo account, the listed connector is the quickest route: open Settings > Connectors in Claude, click Browse Connectors, search for Klaviyo and connect. Approve Claude's access. On the Klaviyo screen that follows, review the permissions it asks for and click Allow.

For several accounts, or for any of the settings later in this post, add a custom connector. Click Add custom connector, name it (for example "Klaviyo - Brand name"), enter https://mcp.klaviyo.com/mcp with any query parameters, then Connect, Approve and Allow. Klaviyo says custom connectors need a Claude Pro, Max, Team or Enterprise plan. On Team and Enterprise, someone with permission to add custom connectors adds it for the organization first, and members then connect their own Klaviyo accounts.

The listed connector can't take query parameters, so it always loads the full tool set, write tools included. If you want read-only mode, use the custom connector even for a single account.

Connect it to ChatGPT

ChatGPT also has two routes. The Klaviyo app for ChatGPT is the simple one for a single account. For several accounts, or for query parameters, turn on Developer mode under Settings > Apps > Advanced settings, click Create app, enter https://mcp.klaviyo.com/mcp, choose OAuth, confirm the warning and click Create. Then approve ChatGPT's access and allow the Klaviyo permissions.

Klaviyo sets include-output-schemas to false by default for ChatGPT clients, so you don't need to change anything there.

What the 309 tools cover

The available tools page groups tools by area: accounts, campaigns, catalogs, events, flows, profiles, reporting, templates, coupons, forms, reviews, data privacy, text messaging, custom objects and more. Each tool is marked as read-only or not, and 308 of the 309 run on the remote server.

Most teams start with the read-only tools:

  • get_campaign_report and get_flow_report for performance by campaign or flow.
  • query_metric_aggregates for event totals over time, such as Placed Order by day.
  • get_segments, get_flows, get_campaigns and the profile lookups.

The other 159 tools write. A few that deserve a second look before you let an assistant near them:

  • send_campaign sends a campaign to its configured audience. Klaviyo's agency guide says plainly that a sent message can't be undone.
  • delete_flow, delete_campaign, delete_list and delete_segment.
  • subscribe_profile_to_marketing, unsubscribe_profile_from_marketing, bulk_suppress_profiles and bulk_import_profiles, which change who receives your email and SMS.
  • request_profile_deletion, which asks Klaviyo to delete a person's data.
  • update_flow, which changes a flow's status, so a live flow can be switched off.

Campaigns that use A/B tests or Smart Send Time can't be sent through the MCP server, so you schedule those in Klaviyo. With core-tools-only=true the server loads about 30 core tools, and that set leaves out campaign sending.

Lock it down before the first prompt

These settings come from Klaviyo's query parameter table. They only work through a custom connector or the developer-mode app, which is one more reason to set one up.

Setting What it does When to use it
read-only=true Hides and blocks every tool that writes or deletes Reporting and audits, and anyone new to the connector
disable-tools-with-user-generated-content=true Turns off the 14 tools that read user-generated content such as profile properties, event data and reviews When you don't need profile-level detail and want to reduce prompt-injection risk
toolsets=campaigns:read,flows:read Loads only tools whose API scopes fall inside the list A narrow reporting connector
core-tools-only=true Loads about 30 core tools Clients with small context windows, or to cut down tool choice
company=brand-name Labels the connector so you can tell accounts apart Agencies and multi-brand teams

A review, a form answer or a custom profile property is text a customer wrote, and the assistant reads it as part of its context. Klaviyo's docs warn that this content "could be interpreted by your LLM" and ask you to review each tool call. The 14 tools it disables include get_profiles, get_profile, get_events, get_reviews and the profile updates. Reports and metric aggregates keep working, so a reporting-only connector loses very little.

A reporting connector for a brand team could use this URL:

https://mcp.klaviyo.com/mcp?company=brand-name&read-only=true&disable-tools-with-user-generated-content=true

If someone on the team does need write access, keep it on a separate connector and set Claude's connector permissions so write and delete tools ask for approval. Klaviyo's guide notes that approval still lets the action through once you click it, so whoever approves should check the account, audience, content and send time first. In each chat, enable only the connector you mean to use.

Prompts that work for a Shopify brand

Try these on a read-only connector first.

  • "Show revenue, click rate and placed order rate for every flow over the last 30 days, sorted by revenue. Flag any flow whose revenue fell more than 20% against the 30 days before."
  • "List campaigns sent in the last 90 days with recipients, open rate, click rate and attributed revenue. Which subject line patterns show up in the top 10?"
  • "Which segments exist, how are they defined, and which ones haven't been used in a campaign in 60 days?"
  • "Audit the welcome, abandoned checkout and win-back flows for overlapping triggers or branches that never fire."

Ask the assistant to name the connected account before anything else. Klaviyo's agency guide recommends the same check, because a connector authorized against the wrong account answers confidently about the wrong brand.

If you want a template for the segment work, our guide to RFM segments in Klaviyo has the definitions, and the win-back email guide covers the flow side.

Where Klaviyo data runs out

The Klaviyo MCP server answers questions about Klaviyo. Revenue in those reports is Klaviyo's attributed revenue, based on its own attribution settings. It isn't the same number as Shopify net sales, and it knows nothing about margin, ad spend, refunds after the attribution window or the subscription billing system. "Did the win-back flow pay for its discount?" needs Shopify orders and product costs next to Klaviyo's numbers.

You can connect more servers to the same assistant; our overview of Shopify's MCP servers lists the ones Shopify runs. We also have guides to the official Meta Ads MCP server and Google Ads MCP server. Each server reports in its own definitions, though. The assistant then reconciles Klaviyo revenue against Shopify sales against ad platform conversions in the middle of a chat, and nobody can see afterwards how it matched them.

Finsi MCP gives Claude or ChatGPT one set of numbers built from Shopify, ads and Klaviyo instead. It's read-only and every call is logged. When you want an agent to act on those numbers, for example pausing a flow or drafting a campaign, Finsi's AI agents ask for approval before each change. Our post on approval-gated agents explains how that works, and bring your own AI agents covers running Claude or ChatGPT against your store data.

Sources