Skip to main content
Glama
ducnhd

google-data-mcp

by ducnhd
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to google-data-mcp

No user-submitted related servers found.

    Related Servers

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

    • Wikipedia Trends API

      trendsapi
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that exposes Wikipedia page view trends as clean JSON, providing normalized 0-100 trend scores, growth rates over 3M/6M/12M/5Y windows, and live most-viewed article feeds, comparable across 15 sources including Google, YouTube, and TikTok.
      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
      138 npm
      2
      MIT
    • Trends MCP by trendsapi

      Trends MCPofficial

      trendsapi
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides hosted trend data MCP server for querying Google, TikTok, Amazon, Reddit, YouTube, Steam, npm and 30+ trend sources in natural language from any MCP-compatible AI.
      MIT

    • trend-feeds

      trendsapi-ai
      A
      license
      Not graded
      quality
      C
      maintenance
      Hosted HTTP MCP server that lets clients pull weekly search-interest history, percentage growth, and live ranked trending feeds for a given source and keyword. It exposes these as three tools over a single remote endpoint with bearer-token authentication, so assistants can query trend data without local setup.
      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

    A4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool targets a distinct Google service or distinct operation within a service. google_trends_compare and google_trends_interest are clearly differentiated by their normalization semantics, and the ad tools (advertisers vs creatives) have distinct purposes. No two tools could be easily confused.

    Naming Consistency4/5

    Tool names follow a consistent service-prefix pattern (google_trends_, google_ads_, youtube_, google_play_), but the second part mixes nouns, verbs, and gerunds (e.g., compare, trending, listing, advertisers, creatives, reviews). While not perfectly uniform, the pattern is predictable and readable.

    Tool Count5/5

    With 7 tools, the set is well-scoped. It covers multiple Google data services without bloating, and each tool addresses a common use case, making the count feel right for the stated purpose.

    Completeness4/5

    The tool surface covers core workflows for Trends (compare, trending, interest), Ads (advertiser search and creatives), YouTube (listing videos), and Play (reviews). Minor gaps exist (e.g., no YouTube channel details, no Play app metadata), but the essential read operations are present. The server explicitly notes limitations like no transcripts, which clarifies its boundaries.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources