niche-google-trends-mcp

MCP server for Google Trends keyword validation and demand analysis. No API key needed.

v0.2.0 — Replaces broken pytrends backend with real Chrome browser + RSS feed.

How it works

Browser tools launch a real Chrome via CDP (port 9223), navigate to trends.google.com/trends/explore, and intercept the API responses from:

• /trends/api/widgetdata/multiline → timeline data
• /trends/api/widgetdata/relatedsearches → related queries
• /trends/api/widgetdata/comparedgeo → geographic data

This bypasses pytrends 429 issues entirely by routing through a real browser session.

RSS fetches from the public Google Trends RSS feed (trends.google.com/trending/rss). Always available.

Setup

# Install
pip install niche-google-trends-mcp
# or
uvx niche-google-trends-mcp

# First-time setup: open Chrome and accept Google cookies
niche-google-trends-mcp --login

MCP Config

{
  "mcpServers": {
    "niche-google-trends-mcp": {
      "command": "uvx",
      "args": ["niche-google-trends-mcp"]
    }
  }
}

Architecture

src/google_trends_mcp/
├── server.py          # FastMCP with 4 tools + CLI
├── tools.py           # Pydantic params + async routing
├── rss.py             # Google Trends RSS fetcher  
└── browser/
    ├── __init__.py
    ├── client.py      # TrendsBrowser via Patchright/CDP
    └── scraper.py     # API response interception + parsing

Key differences from v0.1.0 (pytrends)

Rate limiting

Google rate-limits the widgetdata/multiline and relatedsearches endpoints. The code handles this with:

• 2 retries with 10s/20s exponential backoff
• parse_jsonp() returns None for non-JSON responses (HTML error pages)
• RSS trending_searches is never rate-limited

Testing

# Unit tests (no Chrome needed)
uv run pytest tests/ -v

# Integration test (requires Chrome on port 9223)
uv run python scripts/integration_test.py