Abency
Run a marketing agency's social, SEO, ads, WordPress and email from an AI agent.
Report on campaigns and flows, query profiles and events, and create campaigns and templates.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Klaviyo MCP server connects Klaviyo email and SMS marketing to Claude, ChatGPT, Cursor and any MCP-compatible agent. It reports on campaign and flow performance, queries profiles, segments and events, and drafts campaigns and email templates — so reporting and content work happen in the conversation. Sign-in is OAuth, and a read-only mode is available.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
read-only is false. Eight of the 27 directory-named tools create campaigns, create and update profiles, upload images, create templates, and change marketing subscription status. Set read-only=true before you let an assistant loose on a live account.beta=true parameter Klaviyo describes as enabling "new, potentially unstable tools". Among the remote-available tools Klaviyo documents but the snapshot omits is send_campaign — sending a campaign to its configured audience — plus cancel_campaign_send and request_profile_deletion. Do not size the risk of this connector from the 27-name listing.include-mcp-app=true is undocumented by Klaviyo. Anthropic's directory publishes the endpoint with that parameter and its entry sets has_mcp_app: true, but Klaviyo's MCP page never mentions it and lists five other parameters without it. We could not list resources to check for a widget, because the server requires OAuth. Treat an interactive widget as plausible but unconfirmed. The Klaviyo ChatGPT App that Klaviyo does document is a separate, ChatGPT-specific product.Owner, Admin or Manager. Klaviyo's documentation states the remote-hosted server is only available to users holding one of those three roles, and lists the wrong role as a cause of failed connections. Klaviyo's roles article adds that only Owner and Admin can manage integrations, so a Manager may still hit narrower limits.
Yes. Klaviyo's tool table documents send_campaign, described as sending a campaign to its configured audience, as a write tool available on the remote server, alongside a tool to cancel a send. That name is absent from Anthropic's 27-name directory snapshot, so the connector reaches further than that listing implies. Use read-only mode to prevent it.
Add read-only=true to the server URL. Klaviyo documents that this query parameter disables every tool capable of a write action on your account. On the local server the same control is the READ_ONLY environment variable. Klaviyo notes the parameter cannot be set through the listed Claude connector, so use a custom connector.
The default surface is large. Klaviyo documents a core-tools-only=true parameter that limits the server to roughly 40 core tools, and says it helps clients with smaller context windows and improves tool-selection accuracy. Klaviyo defaults this parameter to true for ChatGPT clients and false everywhere else.
Klaviyo says yes, and ships a switch for it. Its documentation flags specific tools as reading user-generated content that your model could interpret, and warns you to review each tool call so your client does not act on malicious instructions. Setting disable-tools-with-user-generated-content=true turns those tools off.
Usually a stale client process. Klaviyo's troubleshooting tells you to terminate all processes and relaunch the app to refresh the client, and to re-check the configuration first. For the remote server it also says to confirm the URL has no trailing slash and that your account role is Owner, Admin or Manager.
Yes, through custom connectors rather than the listed one. Klaviyo documents adding one custom connector per account, distinguishing them by name and by a company query parameter on the URL. It advises enabling only the relevant connector in each new chat so the assistant does not query the wrong account.
.md variant this ReadMe-hosted site serves; ~6,700 words). Source for setup, query parameters, troubleshooting, the per-tool Read Only table and the role requirement. · retrieved 2026-08-18initialize against https://mcp.klaviyo.com/mcp?include-mcp-app=true — HTTP 401 with WWW-Authenticate: Bearer realm="OAuth", retrieved 2026-08-18. This is the authentication challenge that establishes the OAuth posture. · retrieved 2026-08-18scopes_supported field, so we make no claim about OAuth scopes. The matching authorization-server metadata confirms dynamic client registration. · retrieved 2026-08-18partner tier, endpoint and categories above are read from our committed directory snapshot dated 2026-08-16; the directory page itself blocks automated fetches, so we did not retrieve it directly. · retrieved 2026-08-16developers.klaviyo.com/robots.txt permits this path and carries no Content-Signal directive (retrieved 2026-08-18). No llms.txt is published; the .md suffix on page URLs is the machine-readable route. · retrieved 2026-08-18Connect Klaviyo once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.