Skip to main content
Glama
Sign In
Google Trends MCP

Google Trends MCP

by den-indance
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Google Trends MCP

No user-submitted related servers found.

    Related Servers

    • Google Trends MCP Server

      mamrrez
      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

    • 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

      jain-eshan
      A
      license
      A
      quality
      B
      maintenance
      Enables querying Google Trends data directly from conversational MCP clients, including search interest over time, related queries and topics, regional breakdowns, and trending searches, for market research without leaving the chat.
      11
      2
      MIT

    • Google Trends MCP

      trendsmcp-ai
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to query live trend data and historical search volume across 30+ platforms like Google, TikTok, YouTube, Amazon, and Reddit, including growth comparisons and top-ranking trends.
      3
      16
      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

    B3.4/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Resources