Growth teams validate angles faster when demand curves, social spikes, and commerce interest arrive in the same assistant thread instead of scattered exports.
Someone running paid social, lifecycle email, and landing tests still has to explain why a spike matters. Copy-paste screenshots age within hours. Spreadsheets with mismatched date ranges invite arguments in Slack.
Trends MCP sends JSON that assistants can cite. A growth lead can ask for the same keyword on google search, youtube, and tiktok, then ask for percent_growth on 30D and 12M without opening five vendor tabs. The marketing MCP workflows page covers the wider pattern; this page stays on the growth function: prioritizing bets, defending budget, and spotting false alarms.
Marketers type queries such as “best MCP servers for marketers” because they want live reads inside Claude, ChatGPT, Cursor, or VS Code. Roundup articles rank when they name categories, show read-only versus read-write limits, and link to official docs. Trends MCP belongs in those stacks as the read-only demand layer: it does not change bids, yet it supplies the attention data that tells you whether a narrative is widening or shrinking.
Agency posts also rank for “SEO workflow automation” by listing tools with crisp job-to-be-done blurbs. Borrow that clarity here. Growth owns the intersection of acquisition and retention metrics; trend pulls answer whether public curiosity supports a campaign story before performance dashboards move.
Monday planning benefits from three pulls. First, Get Growth on the hero keyword across google search and amazon with ["YTD","3M","30D"]. Second, Get Trends on the same keyword for youtube and tiktok to see whether video and hashtag curves diverge from search. Third, Get Top Trends on Google Trends and TikTok Trending Hashtags for ambient culture checks.
When the curves disagree, the team documents the gap instead of forcing a single story. That behavior matches how strong research pages earn snippets: lead with the decision the data supports, then show the limits.
Zapier, Make, and n8n pages already describe HTTP posts to https://api.trendsmcp.ai/api. Growth operations teams reuse those patterns to drop formatted summaries into Slack trend alerts from REST or Airtable bases synced from pulls. The API counts one request per source plus keyword for series work, and counts leaderboard pages per feed type and offset, so planners should batch keywords instead of firing ad hoc prompts all morning.
Trends MCP normalizes scores for comparability, which means the numbers are pipeline-consistent rather than a pixel-perfect mirror of every consumer UI. Reddit calls require a subreddit name without the r/ prefix. App download estimates expect an Android package id. When a feed returns data_unavailable, retry later rather than treating silence as proof.
Read demand gen trend data inside MCP clients for pipeline reporting, SaaS GTM trend research inside an assistant for tighter ICP narratives, and the docs for exact JSON fields. Grab a key at trendsmcp.ai/account when the team is ready to test prompts against production responses.
FAQ