Google Trends MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROXY_URL | No | Single rotating proxy endpoint. Provider handles IP rotation internally. No validation, no fallback. | |
| PROXY_LIST | No | Comma-separated list of proxies (http://user:pass@host:port,...). Validated on startup, bad ones auto-dropped. | |
| PROXIES_ENABLED | No | Set to 'false' to disable all proxy logic (direct requests). Default: enabled. | true |
| PROXY_LIST_FILE | No | Path to a file with one proxy per line (# comments and blank lines allowed). Validated on startup. Re-read on proxy_refresh. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| compare_keywordsB | Compare search interest over time for up to 5 keywords |
| get_related_queriesC | Get top and rising related queries for a keyword |
| get_interest_by_regionC | Get search interest by region/country for a keyword |
| proxy_statusA | Show proxy pool status: source, working count, age, freshness, and validation progress |
| proxy_refreshA | Re-validate the current proxy source (PROXY_LIST or PROXY_LIST_FILE). Blocks until done. No-op for PROXY_URL single-proxy mode. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: proxy_status and proxy_refresh handle proxy pool management, while compare_keywords, get_related_queries, and get_interest_by_region each perform a different Google Trends data retrieval operation. There is no overlap.
All tool names follow a consistent verb_noun pattern in snake_case (proxy_status, proxy_refresh, compare_keywords, get_related_queries, get_interest_by_region), making them predictable.
With 5 tools, the server is compact but reasonable. The proxy tools are necessary for maintenance, and the three trends tools cover common queries, though more could be added for a full-featured Trends API.
The trends surface lacks a basic single-keyword interest-over-time tool and missing features like time range or category filtering. Proxy tools are complete for their purpose, but the overall domain coverage has notable gaps.