
Klaviyo
Manage Klaviyo lists, campaigns, and automation from your agent while you ship product-led email flows.
Overview
com.mcparmory/klaviyo is a MCP server for the Grow phase that creates and manages Klaviyo email campaigns, lists, and marketing automation.
What is this MCP server?
- Create and manage Klaviyo email campaigns from MCP tools
- Manage lists and marketing automation without dashboard context switching
- Stdio server via mcparmory-klaviyo uvx or Docker at version 1.0.3
- Suited to indie ecommerce and SaaS onboarding sequences
- Registry-hosted package from mcparmory on GitHub
- Server version 1.0.3
- 2 packages: PyPI uvx and OCI Docker
- Stdio MCP transport
Community signal: 25 GitHub stars.
What problem does it solve?
You run lifecycle email in Klaviyo but constantly context-switch between your IDE and the marketing UI for simple campaign and list changes.
Who is it for?
Indie ecommerce and SaaS builders who already use Klaviyo and want agent-driven campaign and list operations.
Skip if: Founders on other ESPs only, or teams that need full visual flow design and A/B reporting entirely inside Klaviyo with no API automation.
What do I get? / Deliverables
Your agent can operate Klaviyo objects through MCP so you ship email updates alongside product work in one workflow.
- Agent-triggered Klaviyo campaign and list changes
- Reduced context switching between code and marketing admin
- Documentable automation steps the agent can repeat
Recommended MCP Servers
Journey fit
How it compares
Klaviyo API bridge via MCP, not an email copywriting agent skill.
Common Questions / FAQ
Who is com.mcparmory/klaviyo for?
Solo builders and small teams who use Klaviyo for email and want their AI coding agent to manage campaigns, lists, and automation programmatically.
When should I use com.mcparmory/klaviyo?
Use it during grow and launch when you need to create campaigns, update segments, or adjust automation without leaving your agent-first dev environment.
How do I add com.mcparmory/klaviyo to my agent?
Add the stdio MCP entry for mcparmory-klaviyo (uvx) or ghcr.io/mcparmory/klaviyo:1.0.3 (Docker) in your client config with valid Klaviyo API keys, then reload MCP tools.