Server data from the Official MCP Registry
Google Trends MCP server: interest over time, comparisons, related queries, trending searches
Google Trends MCP server: interest over time, comparisons, related queries, trending searches
This is a well-structured Google Trends MCP server with proper input validation, reasonable error handling, and permissions aligned to its purpose. The codebase uses unofficial Google endpoints transparently disclosed in documentation. No authentication is required (as documented), and network access is limited to trends.google.com. Minor code quality observations exist but do not present security concerns. Supply chain analysis found 5 known vulnerabilities in dependencies (2 critical, 3 high severity). Package verification found 1 issue.
6 files analyzed · 10 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-purahmanian-google-trends-mcp": {
"args": [
"-y",
"google-trends-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Free Google Trends data inside any MCP-compatible AI client. No API key required.
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.
| Tool | Description | Example prompt |
|---|---|---|
interest_over_time | Weekly interest scores (0-100) for up to 5 terms | "Show me interest in 'matcha latte' over the past year in the US" |
compare_terms | Normalized comparison of 2-5 terms with winner callout | "Compare 'coffee', 'tea', and 'matcha' in Canada" |
related_queries | Top and rising related search queries for a term | "What related queries are rising for 'cold plunge'?" |
trending_now | Today's daily trending searches for a country | "What's trending on Google in the UK right now?" |
interest_by_region | Regional breakdown of interest (country or sub-region) | "Which US states search for 'pickleball' most?" |
No API key is needed. Install and run via npx.
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"google-trends": {
"command": "npx",
"args": ["-y", "google-trends-mcp"]
}
}
}
claude mcp add google-trends -- npx -y google-trends-mcp
Add to ~/.codex/config.toml:
[mcp_servers.google-trends]
command = "npx"
args = ["-y", "google-trends-mcp"]
Spotting seasonality:
"Use Google Trends to show me interest in 'pumpkin spice' over the past 5 years worldwide."
The model calls
interest_over_timewithterms=["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_queriesand surfaces the rising queries, often revealing adjacent niches and trending subtopics.
# Clone and install
git clone https://github.com/purahmanian/google-trends-mcp.git
cd google-trends-mcp
npm 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
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 Puya Ventures LLC. I build custom MCP servers and AI integrations for product teams and researchers. Get in touch: purahmanian@gmail.com | Portfolio: puyarahmanian.com
Part of the Product-Research MCP Suite: keepa-mcp · google-trends-mcp · junglescout-mcp
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
MIT. See LICENSE.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.