MCP100 Assessment

Editorial verdict

Official Klaviyo MCP server for marketing/reporting and supported campaign/content workflows, with dedicated controls for writes and user-generated content. Capabilities: Query supported Klaviyo reporting/account data; Use supported campaign/template and marketing workflows; Restrict hosted server to read-only; Disable tools that can expose user-generated content

Reviewed October 21, 2026

Task Fit

Mapped

Team productivity

Trust

Status warning

maintenance_source_health; client_coverage; tool_contract; install_supply_chain; advisory_freshness; adoption_evidence_presence

Maintenance

Date unavailable

No dated repository or package update is currently stored.

Popularity

Signals available

Visible usage signals are shown for discovery only, not as proof of safety.

Best for

Klaviyo teams that need analytics/marketing workflows in an AI client and can use read-only/user-content restrictions where appropriate.

Not ideal for

Teams handling sensitive marketing/customer data without clear API scopes or prompt-injection controls.

Avoid if

For exploratory use, prefer `read-only=true` and disable tools that expose user-generated content unless those features are specifically needed.

Trade-offs

Promoted after strict re-audit: canonical identity and MCP-native/publisher-backed implementation are sufficiently evidenced, with real workflow value, usable documentation, understandable permissions, plausible maintenance, and no unresolved security veto. Still not strong enough for Recommended.

Evidence scope

Evidence

Current source snapshot

Popularity

No MCP-specific repository metric is stored

9,300 package downloads · PyPI Stats last_month · Third-party

Package identity: klaviyo-mcp-server · version 0.4.2

PyPI Stats last_month · third-party estimate
Package evidence: exact. Exact current MCP implementation/distribution. Do not substitute Klaviyo SDK repos or community repos as MCP implementation repos. Preserve read-only/user-generated-content safety controls.
Observed 2026-10-21; source: https://pypi.org/project/klaviyo-mcp-server/

Stars observed October 21, 2026 · Downloads observed October 21, 2026

Repository evidence: none_current_public_implementation. Not MCP-specific/comparable for MCP-server adoption. No attributable public stars metric was verified. Do not substitute Klaviyo SDK repos or community repos as MCP implementation repos. Preserve read-only/user-generated-content safety controls.

Package evidence: exact. Exact current MCP implementation/distribution. Do not substitute Klaviyo SDK repos or community repos as MCP implementation repos. Preserve read-only/user-generated-content safety controls.

Maintenance

Publisher activity observed October 21, 2026

Current source snapshot

Trust review

Source relationship: First-party MCP

Reviewed October 21, 2026

Sources

Official setup docs — developers.klaviyo.com/en/docs/klaviyo_mcp_server ↗Package registry ↗

Supporting evidence (2)

Official setup docs — developers.klaviyo.com/en/docs/connect_to_the_klaviyo_mcp_server ↗Evidence source ↗

Evidence-backed setup

Install & Agents

Choose your MCP client. A client connects to the MCP server; the language model is selected inside that client. Only stored, source-backed configurations are shown.

Claude Code

Transport not recorded

Publisher documented

Connect via Streamable HTTP to `https://mcp.klaviyo.com/mcp`; complete Klaviyo OAuth / dynamic client registration and apply documented read-only/query restrictions when needed.

The publisher provides client-specific setup instructions.

Verify safely: Claude Code: `claude mcp list` and/or `/mcp` to confirm Connected; use any stronger vendor-documented smoke test where listed.

Uninstall and revoke

Claude Code: `claude mcp remove <name>`; also revoke OAuth/device/API credentials in the vendor account when the vendor provides such a control.

Evidence & methodology

Publisher-documented setup is not the same as MCP100 execution testing. “MCP100 logic checked” means the stored configuration shape was reviewed, not that third-party MCP software was run.

Evidence checked 2026-09-20T00:00:00.000Z

Evidence 1 ↗

Reviewed setup

Type-appropriate, source-backed setup for this mcp server profile.

Endpoint: https://mcp.klaviyo.com/mcp
Setup notes: Source rechecked October 21, 2026: Official Klaviyo MCP; hosted OAuth service plus local Python package. Lifecycle: current beta active. Do not substitute Klaviyo SDK repos or community repos as MCP implementation repos. Preserve read-only/user-generated-content safety controls.

Show source-catalog configuration

Connect via Streamable HTTP to `https://mcp.klaviyo.com/mcp`; complete Klaviyo OAuth / dynamic client registration and apply documented read-only/query restrictions when needed.

Capability

What it does

Official Klaviyo MCP server for marketing/reporting and supported campaign/content workflows, with dedicated controls for writes and user-generated content. Capabilities: Query supported Klaviyo reporting/account data; Use supported campaign/template and marketing workflows; Restrict hosted server to read-only; Disable tools that can expose user-generated content

Productivity & CollaborationMedia & MarketingRetail & E-commerce

Representative uses

Klaviyo teams that need analytics/marketing workflows in an AI client and can use read-only/user-content restrictions where appropriate.

Important limits

Teams handling sensitive marketing/customer data without clear API scopes or prompt-injection controls.

Context Footprint

Not measured yet

Estimated token footprint of the MCP tool schemas exposed to the agent.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Hosted service uses OAuth/dynamic client registration; local server can use a scoped Klaviyo private API key.
Permissions: Permissions follow OAuth/API scopes. Hosted read-only mode disables write tools; UGC-related tools can also be disabled.
Data handling: Marketing/customer/account data and potentially user-generated content can be exposed to the AI client/provider. Klaviyo explicitly provides a control to disable UGC tools.
Cost: Klaviyo plan/API and model/provider costs apply.
Risk and cautions: Sensitive customer/marketing data, mutating campaign operations and prompt-injection risk from user-generated content require explicit controls.

Related reviewed MCPs

Other options

HubSpot MCP

MCP100 Recommended

Connect OAuth-capable AI tools to HubSpot CRM data and supported read/write workflows.

Choose this instead if

Choose HubSpot MCP instead if querying CRM records, activities, marketing content, and organizational context.

Connect OAuth-capable AI tools to HubSpot CRM data and supported read/write workflows.

Compare with Klaviyo View HubSpot MCP details

Apify MCP Server

MCP100 Recommended

Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡

Choose this instead if

Choose Apify MCP Server instead if running Apify Store Actors and retrieving their datasets through a hosted or local MCP connection.

Recommended when a team already uses Apify and wants an assistant to discover and run Actors for web extraction and automation.

Compare with Klaviyo View Apify MCP Server details

Notion MCP

MCP100 Recommended

Connect AI tools to Notion workspaces through Notion's MCP server.

Choose this instead if

Choose Notion MCP instead if reading and updating explicitly shared Notion pages.

Connect AI tools to Notion workspaces through Notion's MCP server.

Compare with Klaviyo View Notion MCP details

Read publisher documentation

Publisher documentation

MCP100 source-backed summary

A concise MCP100 summary built from the reviewed publisher sources. It is not a publisher README; use the original link for the latest full documentation.

View original documentation ↗

Klaviyo

Official Klaviyo MCP server for marketing/reporting and supported campaign/content workflows, with dedicated controls for writes and user-generated content. Capabilities: Query supported Klaviyo reporting/account data; Use supported campaign/template and marketing workflows; Restrict hosted server to read-only; Disable tools that can expose user-generated content

What it can help with

Klaviyo teams that need analytics/marketing workflows in an AI client and can use read-only/user-content restrictions where appropriate.

Important limits

Teams handling sensitive marketing/customer data without clear API scopes or prompt-injection controls.

Loading optional publisher documentation…

FAQ

Is this an official MCP?

endpoint:https: is listed as First-party MCP in MCP100’s current evidence.

Current official resources:

Publisher documentation ↗