Google Trends API

io.github.catalyst-labs-devPublished by GitHub account catalyst-labs-devv1.0.0Updated Oct 25, 2026

Google Trends JSON + trend summary, $0.0025/keyword; rate-limited keywords never charged.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Remote Apify-hosted MCP server that lets an assistant fetch Google Trends data and trend summaries for keywords, billed per keyword.

What you can do
Retrieve Google Trends data as JSON for given keywords, through an Apify-hosted remote endpoint. Get a trend summary alongside the raw trends data. Keywords that are rate-limited are not charged.
When to use it
Useful when you want an assistant to pull Google Trends signals or a quick trend summary for keywords without building your own scraping setup, and you are comfortable paying a small per-keyword fee through Apify.
Requirements
Remote streamable HTTP endpoint at mcp.apify.com. Authentication is required: an Apify API token sent as an Authorization header in the form Bearer token, or OAuth sign-in with Apify if your MCP client supports it. An Apify account and network access are needed.
Before you install
Usage is billed at $0.0025 per keyword through Apify, so costs accrue with each request; rate-limited keywords are stated not to be charged. The server requires an Apify API token or OAuth sign-in, so treat that credential as sensitive. Keyword queries are sent to Apify and Google Trends as third parties.

Installation

In SourceWeft

  1. Open Google Trends API in the dashboard and add it to a workspace.
  2. Connect the required 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/io.github.catalyst-labs-dev%2Fgoogle-trends-api/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "google-trends-api": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=catalyst-labs/google-trends-api"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 25, 2026

Score

60% 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
  • Documentation15 pts

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

  • License10 pts

    Declare a license in the repository or the registry entry.