Mcp Google Trends Scraper

com.mambabuiltPublished by mambabuilt.comv1.0.0Updated Nov 7, 2026

Google Trends interest, regions, and related queries per term, with no Google login or key

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Fetches Google Trends interest, regional breakdowns and related queries for search terms through an Apify actor, returning summary and detail rows.

What you can do
  • Retrieve Google Trends data for one or more search terms, with optional geo, timeframe, category and search property
  • Get a summary row per term: average, latest and peak interest, recent change, top region, top and rising queries
  • Get flat detail rows for interest over time, interest by region, related queries and related topics
  • Compare terms in groups of five on one shared scale, or chart each term separately
When to use it
Useful when you want an assistant to answer questions about search interest trends, compare terms across countries or US metro areas, or surface rising queries, without logging into Google Trends manually.
Requirements
Runs locally as an npm package via npx, needing Node.js 18 or newer. Requires an Apify account and an Apify API token supplied in the APIFY_TOKEN environment variable; the tool is listed without a token but calls need one. Network access to Apify is required.
Before you install
Calls run a paid Apify actor billed per event to your Apify account (per term report, extra rows and run start), so repeated or large term lists cost money; an optional max_charge_usd argument caps a run. The APIFY_TOKEN secret is passed in the client config. Search terms and settings are sent to Apify and Google Trends via Apify proxies.

Installation

In SourceWeft

  1. Open Mcp Google Trends Scraper in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Google Trends Scraper MCP Server

[npm version] [license]

An MCP server for the Mamba Labs Google Trends Scraper actor on Apify. Read Google Trends for your search terms and get a summary row per term plus flat detail rows.

What's Inside

What it does

Give search terms, with a geo, timeframe, category, or search property if you want them. For each term you get one summary row (average, latest, and peak interest, recent change, top region, top and rising queries) and flat rows for interest over time, regions, and related queries. Terms can be compared in groups of 5 on one scale. Values are relative to the chart, not search counts.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (claude_desktop_config.json), Cursor, or any MCP client:

json
{  "mcpServers": {    "mamba-google-trends-scraper": {      "command": "npx",      "args": [        "-y",        "@mambalabsdev/mcp-google-trends-scraper"      ],      "env": {        "APIFY_TOKEN": "your-apify-token"      }    }  }}

Restart the client. The get_google_trends tool appears.

Prerequisites

Example prompts

  • "How has interest in matcha changed in the US over the last 12 months?"
  • "Compare coffee and tea by US metro area."
  • "What are the rising search queries around ozempic?"

Tool

get_google_trends. One tool. Example arguments:

json
{  "terms": [    "coffee",    "matcha"  ],  "geo": "US",  "timeframe": "today 12-m"}

Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

InputTypeRequiredDescription
termsarraynoSearch terms, up to 200 per run. A Google topic ID such as /m/0j6n6s8 also works.
geostringnoEmpty for worldwide, or a Google geo code such as US, DE, or US-CA.
timeframestringnonow 1-H, now 4-H, now 1-d, now 7-d, today 1-m, today 3-m, today 12-m, today 5-y, all, or two dates as YYYY-MM-DD YYYY-MM-DD.
categorystringnoGoogle Trends category number. 0 is all categories. The number is in the cat= part of a Trends URL.
propertystringnoWhich Google search to read: web, news, images, youtube, or shopping.
comparebooleannotrue: terms are charted together in groups of 5, on one shared scale. false: each term gets its own chart. Each term is charged either way.
outputsarraynoAny of interest_over_time, interest_by_region, related_queries, related_topics. Default is the first three. See Limitations for related_topics.
region_resolutionstringnoauto: countries worldwide, regions inside a country. DMA is US metro areas. CITY needs a geo. COUNTRY needs an empty geo.
max_charge_usdstringnoOptional. The run stops before a charge that would pass this amount. Summary rows are always returned.
proxy_modestringnoauto (default): requests go through the Apify proxy pool, and a request the pool cannot get through is retried on residential addresses. residential: every request uses residential addresses. A reliability setting only; it does not change what you pay.

Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

EventFree planBronzeSilverGold
term-report, one search term with data, summary row plus up to 170 detail rows$0.0065$0.006175$0.00585$0.005525
extra-rows, each further 100 detail rows on one term past the first 170$0.0035$0.003325$0.00315$0.002975
apify-actor-start, per run start$0.002$0.002$0.002$0.002

A term with no data, a term Google refused, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

Full actor documentation

apify.com/mambalabs/google-trends-scraper

License

MIT. See LICENSE.

Source: README.md at commit 213be9c

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts