Skip to main content
Glama
google-trends
by yzafar2003

Related Servers

Alternatives to google-trends

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Enables Claude, Cursor, and other MCP clients to retrieve and analyze Google Trends data, including trending searches, interest over time and by region, related queries, seasonality, momentum, and share of search, without requiring an API key.
      32
      48 PyPI
      4
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables Claude to query Google Trends data such as keyword interest, related queries, and regional popularity, with robust proxy rotation to bypass Google's anti-bot measures.
      5
      108 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Real-time trend data from Google Trends (Search, Images, News, Shopping), YouTube, TikTok, Reddit, Amazon, Wikipedia, npm, Steam, Spotify, X (Twitter), App Store, Google Play, web traffic, and news sentiment via one MCP connection. Works with Claude, Cursor, VS Code, Windsurf, ChatGPT, and any MCP-compatible AI.
      28
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to query Google Trends for search-interest signals, returning stable JSON envelopes with calibrated searches/day estimates, relative comparisons across keywords, related and rising queries, regional interest, and country-level Trending Now data. It also surfaces explicit status and error codes so agents can distinguish partial or failed results from real numbers.
      MIT

    TDQS

    A3.6/5.0

    Scored across 4 tools

    Disambiguation3/5

    The three core tools (trending_now, interest_over_time, related_queries) target clearly distinct Google Trends views. However, add_trends_to_question is a composite that re-fetches trending searches plus interest-over-time and related queries, so an agent faces a real choice between the granular tools and the wrapper, and the instruction to call it 'before answering any question that depends on current searches' actively overlaps with the other three.

    Naming Consistency3/5

    All names use snake_case, which is consistent, but the structural convention is mixed: trending_now and interest_over_time are adverb/noun phrases, related_queries is adjective+noun, and add_trends_to_question is a verb_noun_to_noun pattern. The result is readable but not a predictable verb_noun scheme.

    Tool Count4/5

    Four tools is a tight, well-scoped surface for a Google Trends server, and each of the three core tools maps to a real Trends capability. The only waste is the composite add_trends_to_question, which largely duplicates the others rather than adding a new operation.

    Completeness3/5

    The surface covers the three most common Trends workflows (current trending, time-series interest, related queries), but notable gaps remain: no interest-by-region/subregion breakdown, no keyword suggestion or category filters, and no way to get trending by category. Agents needing geographic comparison will hit a dead end.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues