Trends API for JavaScript: Multi-Source Trend Data via HTTP

Trends API for JavaScript

JavaScript has no equivalent of pytrends - there is no widely-used unofficial Google Trends library for Node.js that has maintained community trust. Trends MCP fills the gap directly: it is accessible via standard fetch from any JavaScript environment (Node.js, browser, edge runtime, serverless function) and returns structured JSON with normalized values and absolute volume estimates from 15+ sources.

Python developers have pytrends. JavaScript developers have a gap. The few npm packages that attempt Google Trends scraping have poor maintenance records and no community consensus around reliability. The standard approach for JavaScript projects that need trend data has been to either use a Python microservice for data collection or to accept Google Trends' manual interface and not automate it.

Trends MCP is a managed HTTP API that works from any JavaScript environment via fetch. The response is structured JSON with a consistent schema, which makes it straightforward to use in web apps, API routes, serverless functions, or AI agent tools.

Calling Trends MCP from Node.js

The API accepts standard HTTPS POST requests with JSON-RPC bodies. Node.js v18+ includes native fetch, so no additional HTTP library is required:

const API_KEY = process.env.TRENDS_MCP_API_KEY;
const ENDPOINT = "https://api.trendsmcp.ai/mcp";

async function callTrendsMCP(toolName, params) {
  const response = await fetch(ENDPOINT, {
    method: "POST",
    headers: {
      "Content-Type": "application/json",
      "Authorization": `Bearer ${API_KEY}`,
    },
    body: JSON.stringify({
      jsonrpc: "2.0",
      method: "tools/call",
      params: {
        name: toolName,
        arguments: params,
      },
      id: 1,
    }),
  });

  const data = await response.json();
  // The trend data is in the MCP response content
  return JSON.parse(data.result.content[0].text);
}

// Get weekly Google Search trend for any keyword
const trendData = await callTrendsMCP("get_trends", {
  keyword: "electric vehicles",
  source: "google",
  data_mode: "weekly",
});

The returned trendData object contains the time series array with date, normalized_value, absolute_volume_estimate, and data_quality_score per data point. Pipe it directly into a chart library.

Next.js API route pattern

For Next.js applications, the cleanest pattern is a route handler that proxies requests to Trends MCP, keeping the API key server-side:

// app/api/trends/route.js
export async function POST(request) {
  const { keyword, source } = await request.json();

  const trendData = await callTrendsMCP("get_growth", {
    keyword,
    source: source || "google, tiktok, reddit",
    percent_growth: ["1M", "3M", "1Y"],
  });

  return Response.json(trendData);
}

Your frontend components then call /api/trends and never touch the Trends MCP API key directly.

Building a trend feed with get_top_trends

For apps that surface what is trending right now, get_top_trends requires no keyword and returns a live list of trending topics on any platform:

const trendingNow = await callTrendsMCP("get_top_trends", {
  type: "TikTok Trending Hashtags",
  limit: 20,
});

// Map the results directly to UI components
const feed = trendingNow.trends.map((item) => ({
  name: item.name,
  value: item.normalized_value,
  growth: item.growth_rate,
}));

This works in serverless functions that run on a cron schedule to populate a cached trending feed, or in real-time API routes that serve a live feed component.

For AI agent tools in JavaScript

JavaScript AI frameworks can use Trends MCP as a tool definition. For Vercel AI SDK:

import { tool } from "ai";
import { z } from "zod";

const getTrends = tool({
  description: "Get trend data for a keyword across multiple platforms",
  parameters: z.object({
    keyword: z.string(),
    source: z.string().optional().default("google"),
    data_mode: z.enum(["weekly", "daily"]).optional().default("weekly"),
  }),
  execute: async ({ keyword, source, data_mode }) => {
    return await callTrendsMCP("get_trends", { keyword, source, data_mode });
  },
});

The tool is then passed to the AI model alongside other tools, and the model calls it automatically when a user asks about trends.

For direct MCP protocol support in Node.js, the MCP TypeScript SDK (@modelcontextprotocol/sdk) can connect to Trends MCP via HTTP transport at https://api.trendsmcp.ai/mcp. This is the most direct integration path for custom MCP clients built in TypeScript.

Edge runtime compatibility

Trends MCP works in edge runtimes (Cloudflare Workers, Vercel Edge Functions) with no modifications. The API uses standard HTTPS and JSON - no Node.js-specific APIs, no streaming that requires special handling. Call it with the standard fetch API and parse the response.

One edge consideration: API key management. Environment variables on Cloudflare Workers and Vercel Edge Functions work the same way as in Node.js. Store the key as a secret, reference it in the handler.

Common questions

Is there a JavaScript library for Google Trends like pytrends?

No reliable equivalent of pytrends exists for JavaScript. There are a few npm packages that attempt to scrape Google Trends, but none have the adoption, maintenance, or community support that pytrends has in Python - and pytrends itself has reliability problems. Most JavaScript developers who need programmatic trend data either call a managed API (like Trends MCP) or use a Python backend for the data collection layer.

What JavaScript environments does Trends MCP work in?

Any environment with fetch or an HTTP client. This includes Node.js (v18+ has native fetch), browser (standard fetch API), edge runtimes (Cloudflare Workers, Vercel Edge, Deno Deploy), serverless functions (AWS Lambda, Google Cloud Functions, Vercel Functions), and any JavaScript framework (Next.js API routes, Remix loaders, Express endpoints). The API is standard HTTPS with no JavaScript-specific dependencies.

Does Trends MCP work in the browser without a backend?

Technically yes - the API accepts CORS requests - but calling it from a browser exposes your API key to anyone viewing the page source. For browser applications, the recommended pattern is to proxy the request through a backend API route that holds the API key server-side. In Next.js, this is a route handler in /app/api/. In a standard Node.js server, it is a simple Express endpoint. The actual call to Trends MCP happens server-side; the frontend calls your proxy.

How do I use Trends MCP in an AI agent built with JavaScript?

JavaScript AI frameworks that support MCP tools (Vercel AI SDK, LangChain.js, the Anthropic SDK with tool use) can call Trends MCP tools directly via the MCP protocol or via standard HTTP tool definitions. For Vercel AI SDK, define a tool that POSTs to the Trends MCP endpoint and returns the structured JSON result. For direct MCP protocol support in Node.js, use the MCP TypeScript SDK and point it at https://api.trendsmcp.ai/mcp with HTTP transport.

Start building with live trend data

No credit card Instant delivery 100 free requests/mo

By continuing you agree to our Terms & Privacy Policy.

API calls served

MR AK JL TS +

Loved by developers

@jamie.l

seo, small agency

Keyword trend reports for clients. Free tier forces us to batch for weekly digests, which turned out fine. Upgrade path exists when we outgrow it.

3 weeks ago

Stella R.

Product Designer

3 weeks ago

aisha_k

Full-stack Developer

~20 min to a working mcp hook. json shape is sane, docs match what ships

5 days ago

Daniel P.

Data Engineer @ Fintech

We pipe weekly series into BigQuery for a few brand cohorts. The old Selenium path was mostly babysitting selectors when Google moved something. This is boring in the best way. Uptime's been solid.

Yesterday

Nina S.

Product Manager, B2B SaaS

When leadership asks why we're shipping something, these screenshots land. Wish the dashboard had saved views; API's the strong half.

4 days ago

Miguel A.

Frontend Developer

4 days ago

tomw

solo / niche saas

Cursor + MCP, one try. Not a trends person; my side project emails me when a niche term spikes week over week and that's all I wanted.

1 week ago

Laura

ML Engineer

Multi-source ranked lists into a notebook, straightforward. When I typo a param the error payload is readable. Sounds small. It isn't.

10 days ago

Keiko N.

Graduate Student

10 days ago

Ben H.

Freelance DevOps

Does what it says. I knocked a star because onboarding assumed I already knew MCP wiring; a copy-paste block for Claude Desktop would have saved me 15 minutes.

2 months ago

Elena

growth, b2b saas

tiktok momentum vs paid spend in one looker sheet. unglamorous tbh — first rollout we didn't fight over about halfway through…

12 days ago

Jordan F.

Backend Developer

Retries: predictable. No random HTML in responses (scrapers, I'm looking at you). Team key rotation would be nice; we rotate keys manually for now.

18 days ago

Victor L.

IT Support

3 weeks ago

Greta V.

Content Strategist

Meme or real trend? One call usually tells me. Still spot-check Search Console when it matters.

9 days ago

Yuki

DevRel Contractor

Workshops: how do you ground LLMs in something fresher than training data? I show this. Engineers who hate glue code actually nod at the MCP bit.

1 month ago

Chris D.

Agency Tech Lead

Client reporting. Finance finally stopped asking which line item this maps to. Peak hours can drag a little. Acceptable.

22 days ago

@amirm

maintainer — ~3 repos

I wired this behind a small CLI for contributors who want trend context in issues. Keeping the surface area tiny matters for OSS, and the schema has not churned on me yet.

16 days ago

Kendra L.

BI Analyst

30-day window, daily pull, internal scoreboard. The screenshot-from-Trends fight in Slack basically ended.

8 days ago

Brooke T.

Demand Gen

8 days ago

Priya

pre-revenue founder

We are pre-revenue, so free tier discipline matters. I hit the cap once during a brainstorm where everyone wanted to try random keywords. Learned to batch smarter.

11 days ago

Henrik W.

Solutions Architect

Security review: HTTPS, scoped keys, no sketchy redirect hops we could find. Sounds basic. It isn't, in this category.

27 days ago

Isaac Z.

Mobile Developer

I do not need this daily, but when App Store rank shifts look weird, having Reddit and news context in one place saves me from context switching across six apps.

19 days ago

Vera

Journalist / Newsletter Writer

Blowing up for real vs loud on one platform. Doesn't replace reporting. Keeps my ledes from lying.

14 days ago

quinn.b

Staff Engineer

playwright job died every time google sneezed. same shape every week now.

3 days ago

Alan C.

Hobbyist Developer

3 days ago

Fatima

E-commerce Director

Seasonal demand spikes line up with what we see in Amazon search interest here. Merch team stopped sending me screenshots from random tools that never matched.

5 days ago

Owen R.

Analytics Consultant

Decks: fine. I still export to Sheets by hand so minus one star. Direct connector someday maybe.

7 days ago

Marcus J.

Game Studio Producer

Steam concurrents plus Reddit chatter in one workflow beats our old spreadsheet ritual before milestone reviews.

13 days ago

Leah

UX Researcher

Quick pulse on whether a feature name is confusing people in search before we ship copy. Cheap sanity check compared to a full survey.

17 days ago

@diegow

SRE

Monitored from Grafana via a thin wrapper. p95 stayed under our SLO budget last month. One noisy day during a holiday but nothing alarming.

24 days ago

Tessa C.

Brand Strategist

Narrative fights in meetings got shorter once we could point at the same trend line everyone agreed on. Sounds silly until you have lived through it.

20 days ago

Uma H.

PhD Candidate, CS

Using normalized series as a weak prior in a forecasting experiment. Citation-friendly timestamps in the payload made reproducing runs less painful.

29 days ago

Xavier E.

IT Manager

Approved for our pilot group after a quick vendor review. Would love SAML, not a blocker for our size.

33 days ago

Daria K.

Operations Consultant

33 days ago

Nina P.

Creator Economy Analyst

YouTube interest + TikTok hashtags in one view. Makes sponsor conversations less hand-wavy. I can point at something.

15 days ago

Gabe K.

Automation Engineer

Cron before standup, Slack gets a blurb. Afternoon to wire. Two quarters without drama.

41 days ago

Sofia Y.

Policy Researcher

Public-interest stuff: search interest is a rough attention proxy. I still hit primary sources. One signal among several, not the whole story.

26 days ago

Raj B.

Cloud Architect

Runs in a VPC egress-only subnet with allowlisted domains. Fewer exceptions to explain to auditors than our last vendor.

35 days ago

Clara

Community Manager

Spotting when a topic is about to flood Discord saves my team from reactive moderation fires. Not perfect, but directionally right often enough.

21 days ago

Mei Z.

Research Associate

21 days ago

Wes L.

Fractional CMO

Lean team. ROI isn't subtle. I wouldn't rebuild our old scraper unless legal made us.

31 days ago

ingrid.k

Technical Writer

Examples in the docs match what the MCP actually returns. You would be surprised how rare that is in this category.

6 days ago

Jon V.

Night-shift NOC Tech

Pager stayed quiet. When something upstream flaked once, the error string told me which parameter to fix without opening logs first.

45 days ago

Avery

University Lab Manager

Students use it for coursework demos. Budget is tight so free tier matters; we coach them to cache aggressively.

38 days ago

@calebw

Engineering Manager

Rolled into our internal CLI. On-call hasn't paged for this integration once.

2 days ago

Paul L.

Technical SEO

claude reads the json, i fix the content. split workflow that actually works

1 week ago

Nadia

Amazon brand manager

Mostly lines up with what we hear on weekly sales calls. I still check inventory before I trust it for a buy.

3 days ago

Felix S.

Performance marketing lead

Pulled a trend summary into ChatGPT for ad copy angles. Corny but it saved a two-hour brainstorm.

Yesterday

Wes T.

Independent consultant

Client asked for a trend slide Thursday 5pm. This existed so I didn't have to fake it.

1 day ago

Lena Y.

Systems developer

Windsurf picked up the MCP manifest without me hand-editing JSON. Small win, I'll take it.

4 days ago

Milo K.

Head of growth

We stopped exporting from five different tools. One chart now goes in the Monday deck and nobody argues about whose export is newer.

10 days ago

Rosa T.

Shopify app developer

Webhook → trend pull → Slack. Boring pipeline. That's the whole compliment.

2 days ago

Soren B.

.NET contractor

Copilot suggested a call pattern that matched your error schema. Saved me a round trip to the docs.

18 days ago

Gabe C.

Lifecycle marketer

Solid API. Dinged for dashboard polish. I'm not an engineer, I live in the UI half the day.

20 days ago

Jon K.

Rust backend developer

Serde-friendly enough I didn't write a custom deserializer. High praise from a grumpy systems person.

15 days ago

Quinn Z.

Data intern

19 days ago

Hassan T.

Web Performance Lead

Response sizes stay small enough for mobile hotspots. I hate APIs that dump megabytes for a sparkline.

4 days ago

Preparing your key…

Almost there. Two quick questions so we can optimize your setup.

What are you working on?

How will you connect?

Trends API for JavaScript

Calling Trends MCP from Node.js

Next.js API route pattern

Building a trend feed with get_top_trends

For AI agent tools in JavaScript

Edge runtime compatibility

`get_trends`

`get_growth`

`get_ranked_trends`

`get_top_trends`

Common questions

Start building with live trend data