Connect a module
Klaviyo
ShopMCP's Klaviyo integration is built from the ground up against Klaviyo's REST API — not a proxy of their official MCP. That means you get full operational capability (send campaigns, build flows, bulk-import profiles, manage coupons, webhooks, custom objects) through one private API key. Setup takes under 3 minutes.
Why the first-party integration
Klaviyo offers its own MCP server at mcp.klaviyo.com, and ShopMCP still supports pointing at it as a fallback. But their MCP is a reporting surface, not an operational one — you cannot send a campaign, modify a flow, create a segment, or manage coupons through it. Our native integration closes all of those gaps and then some.
| Category | Klaviyo's official MCP | ShopMCP Klaviyo | Why it matters |
|---|---|---|---|
| Profiles | 4 tools (read + basic CRUD) | 11 tools inc. merge, bulk import, bulk suppress | Merge dedupes duplicate people; bulk import is the tool you need for migrations from another platform. |
| Lists | 2 read tools | 8 tools — full CRUD + add/remove members | You can build and maintain lists directly from a chat, not just read them. |
| Segments | 2 read tools | 8 tools — full CRUD (create / update / delete) | Create rule-based audiences on the fly — the official MCP is read-only here. |
| Campaigns | 4 tools — draft only, no send | 14 tools inc. send_campaign + cancel_campaign_send | The marquee gap. Their MCP can draft a campaign but cannot actually send it. Ours ships the full lifecycle. |
| Flows | 2 read tools — no writes at all | 9 tools inc. create / update status / delete (PR #5) | Their MCP is read-only on flows. Ours lets an agent build, pause, or ship automated flows end-to-end. |
| Reporting | 2 canned reports | 6 report endpoints + raw metric aggregates | Any metric, any time window, any grouping — no longer limited to campaign and flow canned reports. |
| Coupons | Not available | 9 tools — full CRUD + bulk code minting (PR #7) | Generate single-use discount codes at scale directly from chat-driven workflows. |
| Reviews | Not available | 4 tools — read + moderation (PR #7) | Triage incoming product reviews without opening the Klaviyo UI. |
| Forms | Not available | 5 tools — read + create / delete (PR #8) | Popup, embed, and flyout forms — readable and deletable via MCP. |
| Webhooks | Not available | 5 tools — full CRUD (PR #8) | Wire Klaviyo event streams into your own systems programmatically. |
| Custom Objects | Not available | 10 tools — schema + records CRUD + bulk upsert (PR #8) | Model off-platform data (subscriptions, loyalty tiers, SKU catalogues) and personalise on it. |
| Bulk imports | Not available | Up to 10,000 profiles or 1,000 events per job | Onboard from another platform or backfill historical events without custom ETL. |
| Composite playbooks | Not available | 9 multi-step playbooks (morning dashboard, flow health, deliverability snapshot…) (PR #9) | One prompt, one response — instead of chaining 5–10 calls yourself. |
| Total tools | ≈ 25 | 142 (shipping PR-by-PR) | 6× the coverage. Every row above is accessible via a single API key. |
1. Create a private API key in Klaviyo
Log in to Klaviyo and go to Account → Settings → API keys → Create private API key. Give the key a name (ShopMCP works) and pick the scope recipe that matches how you intend to use the integration:
- Read-only recipe — grant
Readon every resource (Accounts, Campaigns, Catalogs, Coupons, Events, Flows, Forms, Images, Lists, Metrics, Profiles, Reviews, Segments, Subscriptions, Tags, Templates, Webhooks). Registers every read tool plus the composite playbooks. Writes stay off regardless of this key’s scope — that’s gated by a separate toggle (step 3 below). - Operational recipe — grant
Fullon every resource above. This is what the write tools need to work once you turn them on in the ShopMCP dashboard. You can always rotate the key to widen or narrow scope later.
Scope ≠ access
2. Paste the key into ShopMCP
Open Settings → Integrations → Klaviyo and paste the key (it starts with pk_). We validate it with a single round-trip to GET /api/accounts, populate the connection label from your account’s company name, and stash the key in encrypted storage — it never leaves your workspace and never gets logged.
3. (Optional) Enable writes
Flip Allow writes on the same settings page when you want the write tools active. Defaults to off — even an operational-recipe key cannot modify Klaviyo data until this toggle is on. Each write tool also asks the assistant to confirm with you before firing.
Sending campaigns hits real people
klaviyo_send_campaign ships real emails or SMS to real recipients. Use klaviyo_get_campaign_recipient_estimation first to see the audience size, and verify the subject line + send time on the draft before confirming the send. ShopMCP is not responsible for over-sends, bounced deliverability, or billing from SMS segments.4. Multi-account setups (agencies)
Klaviyo API keys are scoped to a single account — there’s no MCA equivalent. If you manage multiple Klaviyo accounts (typical for agencies on our Team / Agency tiers), mint one private API key per account and connect each as its own ShopMCP connection. When two or more are active, every klaviyo_* tool gets a store parameter that targets a specific account — primary is the default.
5. Keeping the legacy integration
If you already OAuthed into Klaviyo’s official MCP server (mcp.klaviyo.com/mcp) and prefer to keep that path, you can still do so via the external-MCP wizard — we’ll record the URL, probe its tool list, and route playbook steps through it. But every capability listed in the comparison table above is unavailable on that path. We recommend switching to the native integration for any workflow beyond reporting.
Our coverage pledge
revision header in @shopmcp/klaviyo-mcpon a quarterly cadence. If a capability you need is still on Klaviyo’s API but not yet wrapped in a ShopMCP tool, email us — it’s on the roadmap already.