google-data-mcp
Related Servers
Alternatives to google-data-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes Google Trends data via BigQuery, enabling LLMs to query top search terms, rising terms, and compare term interest over time for different countries.-
- AlicenseNot gradedqualityCmaintenanceProvides Google Search trend data as an MCP tool, with historical series, growth percentages, and live trending searches, no scraping or rate limits.1MIT
- AlicenseNot gradedqualityBmaintenanceA hosted remote MCP server that lets agents fetch YouTube transcripts for single videos or whole channels, Google Trends interest data, and Google Play reviews through one endpoint with a single key. Results are shaped to fit a context window, with optional raw output and recoverable error responses.1MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server that exposes Wikipedia page view trends as clean JSON, providing normalized 0-100 trend scores, growth rates over 3M/6M/12M/5Y windows, and live most-viewed article feeds, comparable across 15 sources including Google, YouTube, and TikTok.MIT
- AlicenseAqualityDmaintenanceProvides free Google Trends data (interest over time, term comparison, related queries, trending now, regional breakdown) to MCP-compatible AI clients without needing an API key.5134 npm2MIT

Trends MCPofficial
AlicenseNot gradedqualityCmaintenanceProvides hosted trend data MCP server for querying Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and 30+ trend sources in natural language from any MCP-compatible AI.MIT
TDQS
Scored across 7 tools
Each tool targets a distinct Google service or distinct operation within a service. google_trends_compare and google_trends_interest are clearly differentiated by their normalization semantics, and the ad tools (advertisers vs creatives) have distinct purposes. No two tools could be easily confused.
Tool names follow a consistent service-prefix pattern (google_trends_, google_ads_, youtube_, google_play_), but the second part mixes nouns, verbs, and gerunds (e.g., compare, trending, listing, advertisers, creatives, reviews). While not perfectly uniform, the pattern is predictable and readable.
With 7 tools, the set is well-scoped. It covers multiple Google data services without bloating, and each tool addresses a common use case, making the count feel right for the stated purpose.
The tool surface covers core workflows for Trends (compare, trending, interest), Ads (advertiser search and creatives), YouTube (listing videos), and Play (reviews). Minor gaps exist (e.g., no YouTube channel details, no Play app metadata), but the essential read operations are present. The server explicitly notes limitations like no transcripts, which clarifies its boundaries.