Skip to main content
Glama
Sign In
Google Trends Scraper MCP Server

Google Trends Scraper MCP Server

by mambalabsdev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Google Trends Scraper MCP Server

No user-submitted related servers found.

    Related Servers

    • Google Trends MCP

      lhitches
      A
      license
      Not graded
      quality
      C
      maintenance
      Queries Google Trends for interest over time, related and rising queries, regional interest, and trending topics without requiring an API key or account.
      2
      MIT

    • gtfa-mcp

      meka-im
      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

    • Google Trends MCP Server

      ainightshift
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables retrieval and analysis of Google Trends data for any search term over the last 12 months. Provides structured timeline data with relative interest scores that can be filtered by geography and category.
      -

    • google-search-trends-mcp

      trendsmcp-ai
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides Google Search trend data as an MCP tool, with historical series, growth percentages, and live trending searches, no scraping or rate limits.
      1
      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 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of misselection between tools. Its purpose (reading Google Trends data for search terms) is stated explicitly and is distinct from any other exposed operation.

    Naming Consistency5/5

    The single tool follows a clear verb_noun snake_case pattern (get_google_trends) that names both the action and the target service. Nothing deviates from this convention.

    Tool Count2/5

    A one-tool surface is thin: the tool bundles summary, interest-over-time, region/metro/city breakdowns, and related queries into one overloaded call. Users cannot request a single dimension without committing to the whole bundle, and there is no companion tool for related operations (e.g. realtime trends or keyword lookup).

    Completeness4/5

    Coverage of the Google Trends domain is solid for a scraper: per-term summary stats, time series, geographic breakdowns at multiple granularities, and related/rising queries. Minor gaps remain, such as no realtime/trending-searches feed and no way to persist or export results.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources