Skip to main content
Glama
andrewlwn77

Google Trends MCP Server

by andrewlwn77
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Google Trends MCP Server

No user-submitted related servers found.

    Related Servers

    • 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

    • Google Trends MCP

      jain-eshan
      A
      license
      A
      quality
      A
      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
      1
      MIT

    • trendzeist-mcp

      phalkmin
      A
      license
      A
      quality
      A
      maintenance
      Enables free, local Google Trends analysis through MCP, including ranked breakout/rising/evergreen topic discovery, interest over time, keyword comparison, related queries, regional interest, and real-time trending searches without an API key or browser.
      14
      49 PyPI
      MIT

    • bigquery-google-trends-mcp

      jp-caldas
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP 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.
      -

    • 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
      138 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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: one for trending questions, one for API status, and one for currently trending topics. There is no overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent `google_trends_<noun>` pattern, with clear, descriptive names. The verb (get) is implied, and the naming is uniform.

    Tool Count4/5

    Three tools is minimal but reasonable for a focused server. The count covers the core functionalities—trending topics, related questions, and status—without being excessive.

    Completeness3/5

    The server covers basic features like trending topics and questions but lacks tools for specific search queries (e.g., interest over time, comparisons). The surface is functional but not comprehensive.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources