Koskamo

Apify Google Trends API MCP

An MCP server that exposes the Google Trends API Actor, allowing AI agents to retrieve bulk Google Trends data including interest over time, interest by region, related queries, and trending searches for any keyword, country, and time range.

Visit Apify

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

Apify Google Trends API MCP logo, by ApifyCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-07Published by Apify
You need:Each recipe needs an Apify API tokenApify's free plan includes $5 of monthly credit
MCP endpoint (Streamable HTTP)
https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Compare interest in multiple keywords over a specific time period
  • Identify rising searches and breakout terms around a topic
  • Determine current trending searches in a specific country
  • Analyze seasonality and demand peaks for products

Source and maintenance

Community listingRegistry 1.0.0
mcp-registry: io.github.saulius876-lgtm/google-trends@1.0.0Project website

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
511 ms
95th percentile latency
511 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 511 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http google-trends-api-mcp-apify https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add google-trends-api-mcp-apify --url https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api

Cursor

Merge this server into .cursor/mcp.json in your project, then enable google-trends-api-mcp-apify in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "google-trends-api-mcp-apify": {
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "google-trends-api-mcp-apify": {
      "type": "streamableHttp",
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start google-trends-api-mcp-apify and inspect its tools.
VS Code configuration
{
  "servers": {
    "google-trends-api-mcp-apify": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http google-trends-api-mcp-apify https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "google-trends-api-mcp-apify": {
      "serverUrl": "https://mcp.apify.com/?tools=sauliusautomatesit/google-trends-api"
    }
  }
}

Let your agent find its tools

Find servers like Apify Google Trends API MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 6,919