← Explore all mcp servers

MARKETING AUTOMATION / Klaviyo

Klaviyo MCP Server

Klaviyo's official remote MCP server at mcp.klaviyo.com wraps Klaviyo's APIs for campaign reporting, flow comparison, profile inspection and campaign creation, connecting over Streamable HTTP with OAuth and dynamic client registration. Custom connections can disable write tools, restrict tools by API scope, exclude tools that read user-generated content and opt into beta tools through query parameters before connecting.

“The Klaviyo MCP server connects compatible AI clients to Klaviyo APIs through Model Context Protocol (MCP).”

01 / THE REASONING

Why this made the selection.

  • Klaviyo hosts and documents its own remote MCP server and recommends it over its local server, which takes a private API key in the client configuration file.
  • Access control is first-class: connections require an Owner, Admin or Manager role, and query parameters can disable write tools, restrict API scopes and exclude user-generated-content tools before the client connects.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • Klaviyo MCP solutions page: the server connects AI clients to Klaviyo APIs; Klaviyo recommends the remote-hosted server; documented connection options for Claude, ChatGPT, Cursor and VS Code; custom connections support query parameters that disable write tools, restrict tools by API scope, load the core toolset, exclude user-generated-content tools or opt into beta tools.
  • Klaviyo help-center agencies guide: the remote MCP server URL is https://mcp.klaviyo.com/mcp; connecting requires an Owner, Admin or Manager role on each account; agencies add one custom connector per client account.
  • Klaviyo developer guide "Connect to the Klaviyo MCP server": per-client setup for the remote server (Claude, ChatGPT, Cursor, VS Code, other clients: OAuth with dynamic client registration, Streamable HTTP), the query-parameter table, and the local uvx server with its private API key scopes and READ_ONLY / ALLOW_USER_GENERATED_CONTENT environment variables.

Our findings

  • The remote server has no repository or revision to pin. The local server Klaviyo documents is the uvx package klaviyo-mcp-server, configured with a PRIVATE_API_KEY environment variable; the guide recommends keeping that key in a password manager rather than in plaintext config.
  • Tool categories documented include campaigns, flows, profiles, reporting, catalogs and events.
  • The guide's query parameters default to read-only=false, disable-tools-with-user-generated-content=false and beta=false; core-tools-only=true limits the server to a core set the guide puts at "~40" tools (it publishes no exact count), and toolsets limits it to tools whose API scopes fall within a given list.
  • configExample is the guide's Cursor block for the remote server. Corrected 2026-10-13: the earlier example added a "type": "http" key that no Klaviyo page shows, and was attributed to the help-center article, which has no JSON block.

Not established by this review

  • No Klaviyo account was connected and no campaign or report was requested.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗
  1. Confirm an Owner, Admin or Manager role on the Klaviyo account to connect.
  2. Add a custom connector in the MCP client pointing at https://mcp.klaviyo.com/mcp.
  3. Approve the requested scopes, optionally adding query parameters to disable write tools or restrict scopes before connecting.

Before you start

  • A Klaviyo account with an Owner, Admin or Manager role.
  • An MCP client that supports remote servers with OAuth and dynamic client registration.

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "mcpServers": {
    "klaviyo": {
      "url": "https://mcp.klaviyo.com/mcp"
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://www.klaviyo.com/solutions/ai/klaviyo-mcp-server

    Supports: summary, upstreamDescription, homepage, descriptionSourceUrl, compatibility, whySelected, access

  2. https://help.klaviyo.com/hc/en-us/articles/52833598880923

    Supports: install, limitations

  3. https://developers.klaviyo.com/en/docs/connect_to_the_klaviyo_mcp_server

    Supports: configExample, transports, access, limitations, whySelected, review

Evidence & Ask