Google Trends Mcp

io.github.purahmanianPublished by GitHub account purahmanianv0.1.1Updated Oct 24, 2026

Google Trends MCP server: interest over time, comparisons, related queries, trending searches

VerifiedSTDIODesktop onlyWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Lets an assistant pull Google Trends data: interest over time, term comparisons, related queries, trending searches, and regional interest.

What you can do
This local MCP server exposes five tools backed by Google Trends: interest_over_time returns weekly 0-100 scores for up to five terms; compare_terms normalizes two to five terms and names a winner; related_queries lists top and rising related searches; trending_now returns a country's daily trending searches; and interest_by_region breaks interest down by country or sub-region. It runs over stdio and needs no API key.
When to use it
Use it when you want search-demand signals inside an AI client: checking seasonality, comparing keyword or brand interest, finding rising related queries, or seeing what is trending in a country. It suits marketing, product research, and content planning rather than precise market measurement.
Requirements
A local Node.js runtime with npx, since it is installed and run as the npm package google-trends-mcp over stdio. No API key, account, or environment variables are declared. It needs outbound network access to Google Trends endpoints.
Before you install
It calls undocumented internal Google Trends endpoints, which Google may change, rate-limit, or remove without notice; HTTP 429 or blocking can occur, and a few requests per minute is the practical limit. The search terms and region codes you ask about are sent to Google. It is unofficial and not affiliated with Google.

Installation

In SourceWeft

  1. Open Google Trends Mcp 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-mcp

Free Google Trends data inside any MCP-compatible AI client. No API key required.

[CI] [npm]


UNOFFICIAL ENDPOINT DISCLAIMER

This server communicates with the same internal endpoints that the trends.google.com frontend uses. These endpoints are undocumented and unofficial. Google can change, rate-limit, or remove them at any time without notice. This project is not affiliated with, endorsed by, or sponsored by Google LLC. "Google Trends" is a trademark of Google LLC.

If requests start failing, open an issue. The fix is usually a URL or parameter tweak.


What it does

ToolDescriptionExample prompt
interest_over_timeWeekly interest scores (0-100) for up to 5 terms"Show me interest in 'matcha latte' over the past year in the US"
compare_termsNormalized comparison of 2-5 terms with winner callout"Compare 'coffee', 'tea', and 'matcha' in Canada"
related_queriesTop and rising related search queries for a term"What related queries are rising for 'cold plunge'?"
trending_nowToday's daily trending searches for a country"What's trending on Google in the UK right now?"
interest_by_regionRegional breakdown of interest (country or sub-region)"Which US states search for 'pickleball' most?"

Quick start

No API key is needed. Install and run via npx.

Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

json
{  "mcpServers": {    "google-trends": {      "command": "npx",      "args": ["-y", "google-trends-mcp"]    }  }}

Claude Code

bash
claude mcp add google-trends -- npx -y google-trends-mcp

OpenAI Codex CLI

Add to ~/.codex/config.toml:

toml
[mcp_servers.google-trends]command = "npx"args = ["-y", "google-trends-mcp"]

Example conversations

Spotting seasonality:

"Use Google Trends to show me interest in 'pumpkin spice' over the past 5 years worldwide."

The model calls interest_over_time with terms=["pumpkin spice"], timeframe="today 5-y" and narrates the clear September-October spikes each year.

Keyword competition:

"Compare search interest in 'Notion', 'Obsidian', and 'Roam Research' in the US this year."

The model calls compare_terms, reads the averages, and identifies the winner with supporting time-series data.

Opportunity discovery:

"What are the fastest-rising related queries for 'sourdough bread' right now?"

The model calls related_queries and surfaces the rising queries, often revealing adjacent niches and trending subtopics.


Development

bash
# Clone and installgit clone https://github.com/purahmanian/google-trends-mcp.gitcd google-trends-mcpnpm install
# Run tests (no network calls; all HTTP is mocked)npm test
# Build TypeScript to dist/npm run build
# Run the server locally (stdio mode)node dist/index.js

Rate limits and blocking

Google does not publish a rate limit for these endpoints. In practice, a few requests per minute works reliably. If you hit HTTP 429 or get blocked, the server returns a descriptive error message. Waiting 2-5 minutes usually resolves it.


Built by

Built by Puya Ventures LLC. I build custom MCP servers and AI integrations for product teams and researchers. Get in touch: [email protected] | Portfolio: puyarahmanian.com

Part of the Product-Research MCP Suite: keepa-mcp · google-trends-mcp · junglescout-mcp


Privacy

This server runs entirely on your machine. It collects no telemetry and stores no data. The only network calls it makes are to Google Trends endpoints (trends.google.com), sending the search terms and region codes you ask about. No account or API key is involved. See Google's privacy policy: https://policies.google.com/privacy

License

MIT. See LICENSE.

Source: README.md at commit a505da1

Tools

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

Version history

1
  1. v0.1.1LatestSep 16, 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