Klaviyo
Drive Klaviyo (e-commerce email + SMS) from any AI agent: profiles, lists, segments, events tracking, flows, campaigns, catalogs. 14 tools targeting the modern 2024+ API.
7 天免费 · 无需信用卡 · EU 托管
问 Klaviyo 任何事
通过 AnythingMCP 对 Klaviyo 试一个真实提示 — Claude 调用工具并返回答案。在你的消息上按 Enter 即可在 Cloud 安装。
在 Cloud 上安装 KlaviyoClaude 是 AI，可能会出错。请核对回答。
2 分钟设置
- 1在 cloud.anythingmcp.com 开始免费试用。
- 2在连接器商店点击 Klaviyo。提示时粘贴凭据。
- 3生成 MCP API 密钥，将 AI 客户端指向生成的 MCP URL。
Klaviyo 指南
面向主流 AI 客户端的逐步设置。
配置 Klaviyo
直接来自连接器定义：在哪里获取凭据、需要哪些权限，以及该适配器调用的是哪个 API。 由连接器作者以英文提供。
This connector uses the Klaviyo REST API revision 2024-10-15 (current stable).
Setup:
- Sign in to Klaviyo → bottom-left avatar → Settings → API Keys → Create Private API Key.
- Set scopes — at minimum: Profiles (Full), Lists (Full), Segments (Read), Events (Full), Catalogs (Read), Campaigns (Read), Flows (Read).
- Copy the key. It's prefixed with
pk_. SetKLAVIYO_PRIVATE_API_KEY.
Authentication: Authorization: Klaviyo-API-Key ${KLAVIYO_PRIVATE_API_KEY} (the literal prefix is Klaviyo-API-Key, NOT Bearer). The adapter sets this via API_KEY + custom apiKey value.
Revision header: every request MUST include revision: 2024-10-15. The adapter pins this in connector.headers. If you upgrade revision, expect breaking changes — read https://developers.klaviyo.com/en/docs/api_versioning_and_deprecation_policy.
JSON:API spec: Klaviyo follows JSON:API for resource shape. Every response: {data: {id, type, attributes, relationships}, links, meta}. Use ?include= (comma-separated) to side-load related resources in one call.
Filtering syntax: Klaviyo uses a custom filter DSL on most list endpoints. Example: ?filter=equals(properties,{'$source':'newsletter'}) or ?filter=greater-than(created,2025-01-01T00:00:00Z). The adapter exposes common filters as explicit query params.
Profile model: Klaviyo's central object. Each profile has email, phone_number, external_id, plus arbitrary properties (custom fields). Profiles are upserted by email/phone/external_id — you cannot have duplicates on the same identifier.
Events: the heart of Klaviyo's behavioral targeting. Send events via klaviyo_create_event with a profile identifier + a metric name (e.g. 'Placed Order') + properties. Klaviyo automatically creates the metric if it doesn't exist. Events drive flows (triggered automations) — sending the right events at the right time is 80% of Klaviyo work.
Pagination: cursor-based via page[cursor] (response includes links.next with the cursor). page[size] is typically 20 default, 100 max.
Lists vs Segments: lists are static (manually-managed subscribers). Segments are dynamic queries (recompute every few minutes). Use lists for opt-in newsletters, segments for behavioral cohorts ('opened a campaign in last 30 days').
Rate limits: vary per endpoint. Profile reads: 75/sec burst, 700/min steady. Profile writes: 150/min. Klaviyo returns 429 with Retry-After — honor it.
Webhooks out of scope (use Klaviyo's UI to configure event webhooks to your hosted endpoint).
Out of scope here: sending individual emails via the legacy track/identify endpoints (use the Events API + flows instead), template editing, image library, reviews, the older v1/v2 REST API.