Klaviyo

Klaviyo

Included because its first-party MCP combines lifecycle reporting and campaign work with hosted OAuth, a read-only mode, user-content isolation, and a smaller core-tool option for constrained agent interfaces.

Marketing automation, lifecycle & CDPSystem of engagementBYO-UI-ready platform
An illustration of access surfaces surrounding a governed system.
System roleSystem of engagement
Access maturityBYO-UI-ready platform
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Accounts, campaigns, catalogs, events, flows, images, lists, metrics, profiles, segments, subscriptions, tags, templates, and translations exposed through Klaviyo API-backed tools.

02 · Data you can retrieve

Inspect authorized account and lifecycle objects, including campaign and flow performance, without loading write tools when the connection uses read-only mode.

03 · Actions and write paths

Use enabled write tools for lifecycle operations such as campaign creation and permitted profile, segment, subscription, image, template, translation, and event changes; read-only mode removes all modifying tools.

04 · Authentication and permissions

The recommended hosted server uses OAuth with dynamic client registration and is limited to Owner, Admin, or Manager users. The local server instead uses a private API key with resource-specific read or full scopes.

05 · Monitoring, approval, and recovery

Prefer read-only connections for analysis, disable tools that return user-generated content when prompt injection is a concern, use the core tool set for tighter selection, and keep beta tools off unless explicitly tested.

06 · Limits and caveats

The full server exposes many tools and can exceed smaller client context windows or reduce tool-selection accuracy. Listed Claude and ChatGPT connectors cannot set the query parameters available to custom connectors.

Agent access

MCP support

Official MCP serverKlaviyo-hosted remote MCP plus official local serverCurrent documented service

Support: Official MCP server

Read scope: Read authorized Klaviyo account, audience, content, event, catalog, and performance data through the full or approximately 40-tool core catalog.

Write scope: Write through enabled Klaviyo API-backed tools, including campaign creation and permitted audience, subscription, content, image, translation, and event operations; read-only mode disables them.

Authentication: Hosted remote MCP uses OAuth with dynamic client registration over Streamable HTTP; local MCP uses a Klaviyo private API key.

Approval boundary: Show the Klaviyo account, audience or profile scope, channel, content, schedule, and proposed subscription or campaign change before invoking any write tool.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility3
Portability4
Observability3
Documentation5

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that Klaviyo ships them.

Single-platform patterns

  • Commerce lifecycle and audience cockpit
  • Lifecycle journey debugger
  • Audience activation workbench
  • Campaign QA and approval room
Use in the brief builder →

Multi-platform compositions

  • Klaviyo + CRM or commerce system: lifecycle journey debugger
  • Klaviyo + warehouse or CDP + content-production platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

5 recorded sources
MCPRepresentative source
https://developers.klaviyo.com/en/docs/klaviyo_mcp_server ↗

Official Klaviyo docs recommend the hosted server, use account authorization and restrict access to Owner, Admin or Manager roles. Multiple-account connectors, tool-volume/context limits, API rate limits and…

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Targeted first-party MCP/agent-role review; broader API inventory retained

APISource inventory
https://developers.klaviyo.com/en/reference/api_overview ↗

First-party API reference or API overview recorded for this platform.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 12, 2026

Full-profile first-party re-verification on 2026-07-12; see the private audit ledger.

Developer docsSource inventory
https://developers.klaviyo.com/ ↗

First-party developer documentation or platform overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.klaviyo.com/ ↗

First-party product homepage used to confirm product identity and current positioning.

Publisher updated
Jul 1, 2026
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Webhooks / extensionsSource inventory
https://developers.klaviyo.com/en/docs/webhooks ↗

First-party webhook, event, SDK, embedded-app, or extension documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.