{
  "markdown": "# Klaviyo MCP\n\nKlaviyo MCP server. 24 read-only tools cover campaigns, flows, segments, metrics, reports, and profiles across many accounts.\n\n<!-- mcp-name: io.scalably/klaviyo-mcp -->\n\n## Install\n\nClaude Code:\n\n```bash\nclaude mcp add klaviyo -e KLAVIYO_KEY_MAIN=pk_your_key -- npx -y @scalably-io/klaviyo-mcp\n```\n\nCodex:\n\n```bash\ncodex mcp add klaviyo --env KLAVIYO_KEY_MAIN=pk_your_key -- npx -y @scalably-io/klaviyo-mcp\n```\n\nClaude Desktop: download `klaviyo-mcp.mcpb` from the latest GitHub release and open it. Claude Desktop's install form only accepts one account (`KLAVIYO_KEY_MAIN`).\n\n## Setup\n\n1. Create a private API key in Klaviyo under Settings > API Keys.\n2. Set one `KLAVIYO_KEY_<name>=pk_xxx` environment variable per account, for example `KLAVIYO_KEY_MAIN` or `KLAVIYO_KEY_STOREONE`. The server auto-discovers every `KLAVIYO_KEY_*` variable at startup; `list_accounts` shows what it found.\n3. Multiple Klaviyo accounts (agencies, multi-brand portfolios) work only through Claude Code or Codex, since both let you pass arbitrary extra environment variables. Add as many `KLAVIYO_KEY_<name>` variables as you have accounts, then call tools with the matching `account` argument (the name after `KLAVIYO_KEY_`, lowercased).\n4. All 24 tools are read-only.\n\n## Tools (24)\n\n| Tool | What it does |\n|---|---|\n| `list_accounts` | List all configured Klaviyo accounts. Use this first to see which brands are available. |\n| `list_campaigns` | List recent email campaigns for a specific Klaviyo account. Returns campaign IDs, names, status, and send dates. |\n| `campaign_report` | Get email campaign performance metrics for a Klaviyo account. Returns opens, clicks, revenue, bounce rate, unsubscribes for the specified time period. |\n| `list_metrics` | List available metrics for a Klaviyo account. Use this to find the 'Placed Order' metric ID needed for revenue reporting. |\n| `multi_account_summary` | Pull campaign performance summary from ALL configured Klaviyo accounts. Returns a unified cross-brand report. |\n| `flow_report` | Get email flow (automation) performance for a Klaviyo account. Returns metrics for welcome series, abandoned cart, post-purchase, etc. |\n| `campaign_ab_report` | Get per-variation (A/B arm) email/SMS campaign metrics for a Klaviyo account. Splits results by variation so you can compare arms. |\n| `flow_series_report` | Time-series flow (automation) metrics for a Klaviyo account. Buckets by interval. |\n| `segment_report` | Segment performance metrics for a Klaviyo account: member counts, additions, removals. |\n| `form_report` | Sign-up form performance for a Klaviyo account: views, submissions, submit rate. |\n| `list_segments` | List all segments in a Klaviyo account with name, member count, and creation date. |\n| `list_lists` | List all email lists in a Klaviyo account with name, opt-in process, and creation date. |\n| `list_flows` | List all flows (automations) in a Klaviyo account with name, status, trigger type, and last updated. |\n| `get_campaign_detail` | Get full details for a single campaign by ID: name, status, send_time, subject, preview text, channel, and message IDs. |\n| `list_suppressed_profiles` | List profiles suppressed from email marketing for a single reason. Klaviyo only allows `equals` (not `any`) for suppression.reason, so call once per reason for a full picture. |\n| `metric_aggregate` | Aggregate values for any Klaviyo metric (e.g. opens, clicks, revenue) over a custom timeframe and interval. |\n| `get_template` | Fetch an email template by ID, including HTML/text content. Use for audit/preview. |\n| `list_recent_events` | List recent events for a Klaviyo account, optionally filtered by metric_id (e.g. Placed Order). Returns up to 100 most recent. |\n| `account_info` | Get Klaviyo account metadata: org name, timezone, currency, contact email, industry. |\n| `list_tags` | List all tags in a Klaviyo account (used to label campaigns, flows, segments, lists). |\n| `list_templates` | List email templates in a Klaviyo account (name, editor type, dates). Use `get_template` for the HTML of one. |\n| `get_profile` | Look up a customer profile by email or profile ID: name, location, and email-marketing consent/suppression status. |\n| `get_flow_detail` | Get a flow's structure by ID: status, trigger, and its actions/steps (type, message channel). Use `list_flows` for IDs. |\n| `custom_report` | Expert escape hatch: run any Klaviyo values or series report with full control over statistics, group_by, filter, interval, and timeframe. |\n\n## Configuration\n\n| Variable | Required | Purpose |\n|---|---|---|\n| `KLAVIYO_KEY_MAIN` (or any `KLAVIYO_KEY_<name>`) | yes | Private API key for one Klaviyo account. One variable per account; the name after `KLAVIYO_KEY_` becomes the `account` argument. |\n| `KLAVIYO_API_BASE` | no | Override the Klaviyo API base URL (default `https://a.klaviyo.com/api`) |\n| `KLAVIYO_RETRY_BASE_MS` | no | Base delay in milliseconds for the retry backoff (default 1000) |\n\n## Reply shape\n\nEvery tool returns plain JSON with `status` (`succeeded`, `partial`, `no_op`), `operation`, `summary`, `target`, `result`, `proof`, `warnings`, `recovery`. Failures throw a plain error string: `<code>: <message> <hint>`.\n\n## Limits\n\nReporting endpoints (`campaign_report`, `flow_report`, `campaign_ab_report`, `flow_series_report`, `segment_report`, `form_report`, `custom_report` for values/series reports) are rate limited by Klaviyo to 2 requests per minute per account. Reporting data is only available from 2023-06-01 onward; a custom range starting earlier is clamped to that floor. A single reporting request cannot span more than one calendar year, so a longer custom range is auto-windowed into consecutive yearly chunks with a spacing delay between them.\n\n## Verify\n\nEach release lists the package version, the `.mcpb` sha256 and the production commit it was derived from in CHANGELOG.md. CI runs the tests and a clean install of the packed tarball on every push.\n\n## Privacy Policy\n\nThis server runs locally, on your machine, under your own credentials. It collects no personal data, contains no telemetry, stores nothing persistently, and talks only to the vendor API it wraps. No third party, including Scalably, receives your data. Contact: hello@scalably.io. Canonical copy: https://scalably.io/connector-privacy.html\n\n## License\n\nMIT. Copyright Scalably.\n",
  "bytes": 6364,
  "sha": "9992c3930fc9c8102a5f6af6f40f9c374ea5834019eac47a4db66862a6e1d57f",
  "repo_slug": "scalably-io/klaviyo-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_io_scalably_klaviyo_mcp_984cdb19/readme"
}