Google Trends Scraper

io.github.CleanData-LabsPublished by GitHub account CleanData-Labsv1.0.1Updated Oct 30, 2026

Google Trends for agents: interest over time, by region, rising queries, Trending Now. No API key.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that gives an assistant Google Trends data: interest over time, interest by region, rising queries and Trending Now.

What you can do
  • Retrieve Google Trends interest over time for a search term
  • Compare interest across regions
  • Find rising and related queries
  • Read Trending Now searches
  • All of this runs through Apify's hosted endpoint, so no local package is installed.
When to use it
Useful when you want an assistant to pull search-demand signals for market research, content planning or trend comparisons without building your own scraping pipeline.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: either an Apify token sent as a Bearer value in the Authorization header, or an Apify OAuth sign-in with the header left empty.
Before you install
The server is hosted by Apify and requests go through that third party, which may consume Apify account credits or usage. The Authorization header carries an Apify token, so treat it as a secret. Trend figures are scraped estimates, not official Google data.

Installation

In SourceWeft

  1. Open Google Trends Scraper in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.CleanData-Labs%2Fgoogle-trends-explorer/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "google-trends-scraper": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cleandata-labs/google-trends-explorer"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v1.0.1LatestOct 30, 2026
  2. v1.0.0Oct 29, 2026

Score

67% 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 daysRequired25 pts
  • Auth declaredRequired10 pts
  • 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.