Klaviyo MCP

Live

API KEY

EMAIL MARKETING

Every email campaign, flow, and subscriber list your team runs lives in Klaviyo. Klaviyo MCP gives your agent authenticated access to marketing automation data scoped to the user who authorized it.

  • Acts as the user: Access and write actions stay tied to the Klaviyo MCP account that authorized the agent.
  • Credentials stay vaulted: AES-256, resolved at request time, never in LLM context.
  • Scoped before every call: User permissions enforced. 90-day audit trail.
Klaviyo MCP
agent · Acme Q3
Run
Which flows have the highest click-through rates this month and what triggers them?
S
klaviyo_flows_list
81ms
Marketing automation agent
Top 3 flows by CTR this month. Welcome Series (CTR 18.4%, trigger: list join), Abandoned Cart (14.2%, trigger: checkout abandoned), Post-Purchase (11.8%, trigger: order placed). All above 10% benchmark.
Sources: 3 flows, this month
klaviyomcpmcp
3 flows
18:29
Message Claude...

Tools your marketing automation agent reaches for on Klaviyo MCP, scoped per user.

CALL ANY TOOL
List campaigns, flows, and subscriber lists. Retrieve metrics, profiles, and campaign performance.
klaviyo_campaigns_list
List campaigns
List Klaviyo email and SMS campaigns with status filter.
Parameters
Name
Type
Required
Description
status
string
Optional
Status: draft, scheduled, sent, cancelled
channel
string
Optional
Channel: email or sms
limit
integer
Optional
Max campaigns
klaviyo_campaign_get
Get campaign
klaviyo_lists_list
List lists
klaviyo_metrics_list
List metrics
klaviyo_flows_list
List flows
klaviyo_profile_get
Get profile
Build your Agent
Drop the toolkit in, point it at the user, and your marketing automation agent can use Klaviyo MCP from the first run.
import { ScalekitClient } from "@scalekit-sdk/node";
import { DynamicStructuredTool } from "@langchain/core/tools";
import { createReactAgent } from "@langchain/langgraph/prebuilt";
import { z } from "zod";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["klaviyomcp"], toolNames: ["klaviyo_campaigns_list", "klaviyo_campaign_get", "klaviyo_lists_list"] },
pageSize: 100,
});

const lcTools = tools.map((t) => new DynamicStructuredTool({
name: t.tool.definition.name,
description: t.tool.definition.description,
schema: z.object({}).passthrough(),
func: async (args) => {
const { data } = await sk.tools.executeTool({
toolName: t.tool.definition.name,
identifier: "user_123",
params: args,
});
return JSON.stringify(data);
},
}));

const agent = createReactAgent({ llm, tools: lcTools });
import { ScalekitClient } from "@scalekit-sdk/node";
import OpenAI from "openai";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const openai = new OpenAI();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["klaviyomcp"], toolNames: ["klaviyo_campaigns_list", "klaviyo_campaign_get", "klaviyo_lists_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
type: "function",
function: {
name: t.tool.definition.name,
description: t.tool.definition.description,
parameters: t.tool.definition.input_schema,
},
}));

const resp = await openai.responses.create({
model: "gpt-4o", input: prompt, tools: llmTools,
});
import { ScalekitClient } from "@scalekit-sdk/node";
import Anthropic from "@anthropic-ai/sdk";

const sk = new ScalekitClient(envUrl, clientId, clientSecret);
const anthropic = new Anthropic();

const { tools } = await sk.tools.listScopedTools("user_123", {
filter: { connectionNames: ["klaviyomcp"], toolNames: ["klaviyo_campaigns_list", "klaviyo_campaign_get", "klaviyo_lists_list"] },
pageSize: 100,
});

const llmTools = tools.map((t) => ({
name: t.tool.definition.name,
description: t.tool.definition.description,
input_schema: t.tool.definition.input_schema,
}));

const msg = await anthropic.messages.create({
model: "claude-sonnet-4-6", max_tokens: 1024,
tools: llmTools,
messages: [{ role: "user", content: prompt }],
});
import { Agent } from "@google/adk/agents";
import {
MCPToolset, StreamableHTTPConnectionParams,
} from "@google/adk/tools/mcp";

const toolset = new MCPToolset({
connectionParams: new StreamableHTTPConnectionParams({
url: "https://mcp.scalekit.com/klaviyomcp",
headers: { Authorization: `Bearer ${userScopedToken}` },
}),
});

const agent = new Agent({
name: "agent", model: "gemini-2.0-flash",
tools: await toolset.getTools(),
});
Try these prompts
Paste any prompt into your agent to start using Klaviyo MCP.
Campaigns & flows
Copy the prompt
Copied
List all active flows.
Copy the prompt
Copied
Which campaigns were sent this week?
Copy the prompt
Copied
Get stats for [campaign name].
Copy the prompt
Copied
List flows with CTR above 10%.
Lists & profiles
Copy the prompt
Copied
List all subscriber segments.
Copy the prompt
Copied
Get size of [list name].
Copy the prompt
Copied
Find profile for [email].
Copy the prompt
Copied
Which lists have the most unsubscribes this month?
Reporting
Copy the prompt
Copied
Top 3 flows by revenue attributed.
Copy the prompt
Copied
Open rate trend for [campaign series].
Copy the prompt
Copied
Unsubscribe rate by segment.
Copy the prompt
Copied
Compare [campaign A] vs [campaign B] performance.
SEE HOW AUTH WORKS
Users authorize Klaviyo MCP once. Their credentials stay vaulted, every call is checked, and every action is logged.
1
Authorize
Your user connects
Klaviyo MCP
once. We tie it to their identity and the meetings they approved — no shared bot account, no org-wide access
Who:
user ‘A’
when:
Once per user
access:
Limited to user
2
Store
Their
Klaviyo MCP
token lives in a vault scoped to them. User A's meetings are never reachable by an agent acting for user B, even on the same connection
vault:
encrypted
scope:
per-user
tokens:
auto-refreshed
3
Resolve
When your agent calls a
Klaviyo MCP
tool, we fetch the right token server-side. It never touches your agent, never appears in the LLM context, never shows up in your logs
speed:
~40ms
check:
before every call
seen by:
nobody
4
Audit
Every
Klaviyo MCP
tool call is logged — who triggered it, which meeting was fetched, what came back. 90 days of history, tied to the user who authorized it
history:
90 days
export:
SIEM-ready
logged:
every call
Test other agents
Same per-user auth pattern across other marketing automation agents and MCP connectors. Working code, live demos, fork what fits.
SALES
Outbound prospecting agent
Build targeted prospect lists with Apollo, enrich with firmographic data, and draft personalised outreach. Runs on a schedule.
GTM
HubSpot to Slack updates agent
Watch HubSpot deal stage changes and post structured updates to the right Slack channel. Reps stop checking the CRM all day.
Why Scalekit
Secure your agent's access. Connectors ship in minutes
Other connector libraries treat auth as a demo afterthought. Scalekit starts with user identity, scope enforcement, and audit.
01.
Shared tokens break per-user analytics
A shared token looks fine in a demo. In production every call looks like a service account. Scalekit resolves the real user credential so attribution, audit, and scope stay accurate.
// shared token
 audit → bot_service_account
 user_filter → broken

 // scalekit
 audit → user_abc
 scope → enforced ✓
02.
Authentication is not authorization
03.
Multi-tenancy is architectural
04.
Klaviyo MCP today. Others tomorrow.
“Our agents act across Salesforce, Gong, Google Drive, and more, on behalf of every customer. Scalekit behind the scenes meant we can keep adding tools without ever rebuilding how credentials or tool calling work.”
Venu Madhav Kattagoni
Head of Engineering / Von
FAQs
Frequently Asked Questions
Does the agent access Klaviyo MCP as the user or as a shared key?
As the user. Each workspace member authorizes once and Scalekit resolves their credential at request time. Audit logs attribute every action to that user, not a shared service account.
Where is the Klaviyo MCP api key stored?
In Scalekit's managed AES-256 token vault, namespaced per tenant. Refresh is automatic. Revocation is a single dashboard action. Tokens never appear in prompts, logs, or LLM context.
Can I limit what the agent is allowed to do in Klaviyo MCP?
Yes. Pass a tool name filter to listScopedTools so the marketing automation agent only sees the subset you authorize. Pre-API-call scope checks block out-of-policy actions before the request reaches Klaviyo MCP.
What happens when a user revokes Klaviyo MCP access?
The connection is invalidated on the next tool call. Subsequent requests for that user fail closed with a clear error. Other users in the tenant remain unaffected. The event is logged for audit.
Can the agent see suppressed or unsubscribed profiles?
Yes, if the authorizing user's API key has the profiles scope. Suppressed profiles are returned with their suppression reason. The agent cannot re-subscribe a suppressed profile — that action requires manual review in Klaviyo.
Start in your coding agent
Up and running in one command
Install the Scalekit skill in your editor of choice. Connector, auth, tools, prompt, all wired up
Claude Code REPL
/plugin marketplace add scalekit-inc/claude-code-authstack
/plugin install agentkit@scalekit-auth-stack
Cursor Code REPL
# ~/.cursor/mcp.json
{
""mcpServers"": {
""klaviyomcp"": {
""url"": ""https://mcp.scalekit.com/klaviyomcp"",
""headers"": { ""Authorization"": ""Bearer $SCALEKIT_TOKEN"" }
}
}
}
Codex Code REPL
# ~/.codex/config.toml
[mcp_servers.klaviyomcp]
url = ""https://mcp.scalekit.com/klaviyomcp""
auth_env = ""SCALEKIT_TOKEN""
Copilot Code REPL
# .vscode/mcp.json
{
""servers"": {
""klaviyomcp"": {
""url"": ""https://mcp.scalekit.com/klaviyomcp"",
""type"": ""http""
}
}
}