Google Trends Mcp
Pull Google Trends interest and related queries through your agent without manual browser scraping or brittle one-off scripts.
Overview
io.github.den-indance/google-trends-mcp is an Idea-phase MCP server that queries Google Trends from your coding agent with proxy rotation and automatic retries when Google blocks traffic.
What is this MCP server?
- stdio MCP server (@den.dance/google-trends-mcp) for agent-driven trend lookups
- Rotating proxy support via PROXY_URL, PROXY_LIST, or PROXY_LIST_FILE with startup validation
- Auto-retry when Google blocks requests; optional PROXIES_ENABLED=false for direct calls
- Residential-proxy-oriented setup documented for sustained automated access
- npm registry package v1.0.0 with secret proxy credentials as env vars
- npm package @den.dance/google-trends-mcp at version 1.0.0
- stdio MCP transport
- 4 documented environment variables for proxy control (PROXY_URL, PROXY_LIST, PROXY_LIST_FILE, PROXIES_ENABLED)
Community signal: 1 GitHub stars.
What problem does it solve?
Agents cannot reliably fetch Google Trends on their own when Google blocks or throttles automated requests, which stalls niche and keyword research.
Who is it for?
Indie builders validating content products, micro-SaaS niches, or ecommerce angles who already have a rotating or residential proxy and want Trends inside Claude Code or Cursor.
Skip if: Teams that need official Google APIs only, cannot use proxies, or want zero third-party network egress for compliance reasons.
What do I get? / Deliverables
Your agent can run trend comparisons and related-query research in a loop, with proxies validated on startup and bad endpoints auto-dropped so research sessions fail less often.
- Agent-callable Google Trends queries with retry behavior
- Validated proxy pool configuration for sustained automated access
- Repeatable trend research workflow without custom scraper maintenance
Recommended MCP Servers
Journey fit
Trend and demand signals belong in the Idea phase before you commit to a niche, feature set, or content calendar. Research is where solo builders compare topics, regions, and rising queries—exactly what Google Trends answers.
How it compares
MCP integration for live Trends pulls—not a static keyword CSV skill or a general web browser automation pack.
Common Questions / FAQ
Who is google-trends-mcp for?
Solo and indie builders who research markets with AI agents and need Google Trends data without hand-running the website or custom scrapers.
When should I use google-trends-mcp?
Use it in the Idea phase when comparing topics, regions, or seasonality before you scope an MVP, write a landing page, or plan SEO content.
How do I add google-trends-mcp to my agent?
Install @den.dance/google-trends-mcp from npm, register the server in your agent’s MCP config with stdio transport, and set PROXY_URL or PROXY_LIST (or PROXY_LIST_FILE) plus optional PROXIES_ENABLED.