Google Trends API: Bulk Trend Summaries

com.meridianlabssoftwarePublished by meridianlabssoftware.comv1.0.0Updated Oct 24, 2026

Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.

The publisher's own server: Trend News Agency

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Lets an assistant pull bulk Google Trends data, including interest over time, regional breakdowns, rising queries and plain-English summaries.

What you can do
This remote MCP server exposes bulk Google Trends retrieval to an assistant. According to its description, it returns interest over time, regional interest, rising queries and plain-English trend summaries. It is hosted by Apify and reached over streamable HTTP rather than installed locally.
When to use it
Use it when you want an assistant to gather Google Trends signals in bulk, such as comparing search interest across terms, checking regional patterns, or surfacing rising queries and summarized trend narratives for research or reporting. It is less suited to one-off lookups that a single web search could answer.
Requirements
Remote MCP endpoint at over streamable HTTP. Authentication is required: a bearer token in the Authorization header (Bearer ), or OAuth sign-in to Apify for clients that support it. An Apify account is needed, and runs are billed per result.
Before you install
Requires an Apify API token sent in the Authorization header, or OAuth sign-in to Apify. Runs are billed to your Apify account per result, so usage can incur costs. Trend data is fetched from Google Trends through a third-party service.

Installation

In SourceWeft

  1. Open Google Trends API: Bulk Trend Summaries in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.meridianlabssoftware%2Fgoogle-trends/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "google-trends-api-bulk-trend-summaries": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=meridianlabs/google-trends-scraper",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Trend integrations