Operators who live in Retool, Bubble, or Make still need trustworthy trend JSON. POST the same body the docs show to https://api.trendsmcp.ai/api and map fields into tables without running a scraper or juggling one key per vendor.
No code teams win when data arrives as predictable JSON and auth stays boring. Trends MCP exposes exactly that: one HTTPS API, one bearer token, and response shapes that map cleanly to tables, repeaters, and time series charts.
This page is for builders who think in Retool apps, Bubble pages, or stack glue such as Make and Zapier. The mental model matches what Dataslayer and other marketing ops writers describe about fragmented exports, except here the consolidation is on the trend side before the row hits a sheet.
Documentation at https://www.trendsmcp.ai/docs lists required fields for each operation. Get Trends needs source and keyword. Get Growth adds percent_growth arrays. Get Top Trends sets mode to top_trends and passes a feed type string for MCP; REST can batch feeds when the integration allows.
Responses return arrays of dated points with normalized values where the pipeline supports them, plus optional absolute volume fields depending on source coverage. Top trend calls return ranked rows with positions suitable for simple tables.
Create a REST query resource pointed at https://api.trendsmcp.ai/api. Method POST. Headers include Authorization: Bearer <<token>> and Content-Type: application/json. Body can be JSON with bound text inputs for keyword and source.
Bind the response array to a chart component after a small transformer that casts date strings to dates. Add a second resource for Get Growth when stakeholders ask for explicit percent change labels instead of reading the slope by eye.
Security note: keep tokens in Retool secrets or server side resources. Public apps should never embed a bearer key in client bundles.
Bubble workflows can call the API Connector or a plugin that wraps arbitrary HTTPS. The same JSON bodies apply. Map response fields into custom states, then drive repeating groups for top trends or line charts for series.
Because Bubble pages often face end users, prefer server side scheduling or admin only pages for anything that touches paid tiers. The free tier allowance is published on https://www.trendsmcp.ai/pricing and should be read before automating wide keyword lists.
Make and Zapier guides already live on site for teams that want scheduled pulls instead of interactive dashboards. Start from https://www.trendsmcp.ai/make-com-trend-automation or https://www.trendsmcp.ai/zapier-trend-workflows, then promote stable outputs into Airtable or Sheets if that is where approvals happen. https://www.trendsmcp.ai/airtable-trends-automation covers the database angle.
Operators who later adopt Cursor or Claude do not need a second vendor. The MCP endpoint and REST endpoint share the documented auth model described in https://www.trendsmcp.ai/llms.txt. That continuity matters when a dashboard prototype graduates into an assistant led workflow owned by engineering.
Trends MCP answers public demand and ranked feed questions. It does not replace finance systems, warehouse inventory, or private ad network reporting. The right dashboard combines internal metrics from those systems with external interest curves from here.
Pick one keyword the business already argues about weekly. Ship a single chart sourced from google search weekly pulls. When that chart matches intuition, add a second panel from TikTok or Amazon for the same phrase so the table tells a fuller story.
FAQ