# HasData Google Trends [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/HasData/google-trends-mcp  
**GitHub Stars:** 5  
**npm Downloads (last month):** 1150  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/hasdata-google-trends

## Description
Google Trends interest over time, by region, and related queries and topics, as JSON.

## Tools
Capabilities this server exposes over MCP:

- **hasdata_google_trends_search_getTrendsData** — Interest-over-time series, geo-level breakdowns, and rising/top related topics/queries with relative scores. 10 credits a call

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "hasdata-google-trends": {
    "command": "npx",
    "args": ["-y","@hasdata/google-trends-mcp"],
    "env": {
      "HASDATA_API_KEY": ""
    }
  }
}
```

**Requires environment variables:** `HASDATA_API_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What HasData Google Trends MCP server does

The HasData Google Trends MCP server gives MCP clients access to Google Trends data through one read-only tool: `hasdata_google_trends_search_getTrendsData`. The tool can return search interest over time, interest by geographic area, and related queries or topics. Responses are provided as structured JSON through the MCP call result.

Time-series requests return values from 0 to 100 for each point. Geographic requests can provide country, subregion, metro, or city-level results, depending on the selected location and granularity. Related-query and related-topic requests return both rising and top results with relative scores.

Reach for this server when an agent needs trend data for a specified term, date range, location, category, or Google property. It can also compare up to five terms in a time-series or geographic request. Related queries and topics accept one term at a time.

## How it works

The server runs remotely at `https://mcp.hasdata.com/mcp?apis=google_trends` and uses streamable HTTP. Clients send the `x-api-key` header with a HasData API key. No local container or Google account is required when connecting directly to the hosted endpoint.

The tool defaults to a time series and accepts a `dataType` value of `timeseries`, `geoMap`, `relatedTopics`, or `relatedQueries`. Date windows can use presets such as `now 7-d`, `today 12-m`, or `today 5-y`, the value `all`, or a custom date range. An empty `geo` value represents worldwide data. Google properties include web search by default, along with Images, News, Shopping, and YouTube options.

## Setup and configuration

Create a HasData API key from the HasData dashboard, then configure the remote URL and authentication header in an MCP client. The README documents direct configurations for Claude Code, Cursor, Windsurf, and VS Code. Claude Desktop can connect through its connector interface, or use a local stdio launcher.

For Claude Desktop’s configuration-file method, the npm package `@hasdata/google-trends-mcp` reads `HASDATA_API_KEY` from the environment. A Python launcher is also available as `hasdata-google-trends-mcp` through PyPI and can be run with `uvx`.

The free tier provides 1,000 credits per month according to the README. At the listed rate of 5 credits per call, that covers about 200 calls. A direct tool call costs credits even when an agent is making the request on the user’s behalf.

## Tools and capabilities

`hasdata_google_trends_search_getTrendsData` supports:

- Interest-over-time timelines with configurable date ranges.
- Comparisons of up to five comma-separated terms for `timeseries` and `geoMap` requests.
- Geographic interest at country, region, DMA, or city granularity.
- Rising and top related queries or topics with relative scores.
- Category filtering and Google property selection.
- Time-zone offsets for hourly date ranges.

## Limitations and notes

The tool is read-only and exposes one Google Trends operation. Related queries and related topics require a single term, while a sixth term in a comparison request is rejected. Geographic granularity applies only to `geoMap` requests.

A recent time-series point may be marked `isPartial: true` while that period is still filling. Code that calls the MCP endpoint directly should unwrap the JSON from the returned text block; chat clients generally handle that response structure automatically.

_Full upstream README: https://allmcps.com/mcp/hasdata-google-trends/readme_