Can AI agents automate Klaviyo?

Klaviyo is automatable today through a date-versioned REST API on https://a.klaviyo.com and a first-party MCP server. Server-side /api calls authenticate with a private API key (Authorization: Klaviyo-API-Key) or OAuth 2.0 authorization-code with PKCE. Client-side /client calls use a public company ID. The API uses JSON:API relationships, filter, sort, sparse fieldsets, and cursor pagination. Official server SDKs exist for Python, PHP, Ruby, and Node. Campaigns API covers create, update, send, and clone for email, SMS, and push; campaign opens, clicks, and conversions are on the Reporting API, not Campaigns. System webhooks exist, but the Webhooks API is limited to Advanced KDP customers and app partners. Remote MCP is at https://mcp.klaviyo.com/mcp with OAuth and Streamable HTTP. A local server is published as uvx klaviyo-mcp-server@latest and uses a private API key. Remote MCP is documented only for Owner, Admin, or Manager roles. The opened tool table includes accounts, campaigns, catalogs, events, flows, lists, segments, profiles, reporting, templates, coupons, tags, webhooks, and forms; several groups are marked Beta, and ChatGPT defaults to about 40 core tools. The official Headless Klaviyo CLI (pipx install headless-klaviyo) manages campaigns, flows, segments, and universal content blocks as JSON:API files, with --api-key or KLAVIYO_API_KEY. This record excludes HubSpot and Intercom. Zapier, Make, Power Automate, and n8n listings were not opened. Computer-use viability is unassessed. API scores 8 and is the best path because it is the full JSON:API surface; MCP is official and useful but role-gated and client-limited.

Best path today: api · Overall automatability: 8/10