Skip to main content
Glama
Sign In
google-trends-mcp-server

google-trends-mcp-server

by dataxplore19
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to google-trends-mcp-server

No user-submitted related servers found.

    Related Servers

    • google-news-mcp-server

      dataxplore19
      A
      license
      A
      quality
      C
      maintenance
      Google News search for AI assistants: articles by keyword, date range, country or topic, with real publisher URLs and optional full article text. Powered by an Apify Actor.
      2
      MIT

    • google-trends-mcp

      Vicshock
      A
      license
      Not graded
      quality
      B
      maintenance
      Google Trends for AI agents: interest over time with growth %, rising and breakout queries, Trending Now with search volume, and ranking of any number of keywords on one 0-100 scale.
      MIT

    • Google Trends MCP

      den-indance
      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

    • google-trends-mcp

      purahmanian
      A
      license
      A
      quality
      D
      maintenance
      Provides 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.
      5
      143 npm
      2
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools target clearly different things: current trending searches in a country versus historical interest for a specific keyword. An agent can pick correctly from the names and descriptions alone, with no overlap in shape of output.

    Naming Consistency5/5

    Both tools follow the same predictable get_<resource> pattern (get_trending_searches, get_interest_over_time), using snake_case throughout. No mixed conventions.

    Tool Count3/5

    Two tools is thin for a Google Trends server, which naturally exposes several distinct query modes. It's a defensible minimal surface, but it sits at the borderline of feeling under-scoped.

    Completeness3/5

    Core read paths are covered (trending now, interest over time with optional regional breakdown), but there is no multi-keyword comparison, no dedicated related-queries/related-topics tool, and no trending-topics variant. The description explicitly says to call once per keyword, confirming comparison is a gap agents must work around.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources