Lifecycle teams love Klaviyo for segmentation and sends, yet subject lines still guess at what shoppers are curious about. Trends MCP adds Google Search, Shopping, Amazon, and news signals that an assistant can query before a campaign is cloned.
Email operators in Klaviyo already know who receives each flow. The harder question is why a message should land this week instead of next. Trends MCP gives those reasons as structured data: get_trends for long running curves, get_growth for concise momentum, and optional news volume when a send should react to coverage.
Queries like email marketing trend research API, Klaviyo campaign ideas data, and newsletter topic demand rarely surface tooling that sits inside the same AI session as a copy draft. Trends MCP fits that gap because it exposes the sources listed on the public docs without a separate scraper stack.
Pick the hero product phrase or category name. Pull get_trends on google shopping and amazon to see whether demand is climbing ahead of a promo window. Add google search when the story is broader than a single SKU. If the brand newsletter includes a culture section, wikipedia or youtube can indicate curiosity outside commerce. Summarize with get_growth using explicit percent_growth presets so leadership sees 30 day and quarter views in one response.
Deliverability, list hygiene, and revenue attribution stay inside Klaviyo and its integrations. Trends MCP does not send mail or change segments. It informs the creative and scheduling conversation before builders click Publish.
Newsletter first teams can continue on newsletter growth trend research. Demand gen programs pair well with demand gen trend data inside MCP clients. Commerce heavy copy should also read ecommerce listing trend data.
FAQ