MCP.so
ログイン
G

Google Trends MCP Server

@Eason-Gao3

基本情報

カテゴリ

その他

トランスポート

stdio

認証方式

oauth

作者

Eason-Gao3

投稿者

Eason Gao

Google Trends MCP Server について

A production-grade Google Trends MCP server for AI workflow integration. Supports batch research of up to 50 keywords with cross-batch normalization, compare up to 5 keywords precisely, async task support, and REST API + GPT Actions. Compatible with 7 major AI clients: Claude Des

Google Trends MCP Server の設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

{
  "mcpServers": {
    "google-trends": {
      "url": "https://easontrendmcp.dpdns.org/mcp",
      "headers": {
        "Authorization": "Bearer gtmcp_live_your-api-key"
      }
    }
  }
}

Google Trends MCP Server のツール

ツール一覧はまだありません

この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。

このサーバーは認証が必要です。ツールの取得にはログインや提供元の認証情報が必要な場合があります。

上のボタンでサーバーのエンドポイントに接続し、ツール一覧を取得できます。

概要

What is Google Trends MCP?

Google Trends MCP is a Model Context Protocol server that gives AI assistants structured Google Trends data. It supports batch keyword research (up to 50 keywords per batch), cross-batch normalization for comparability, and production-level SaaS deployment. Built with FastMCP, it works with Claude Desktop, ChatGPT, Cursor, Perplexity, and other major AI clients.

How to use Google Trends MCP?

Install Python 3.11+, clone the repo, create a virtual environment, install dependencies, then run python server.py for local stdio mode. For a web service, use --transport streamable-http with host and port. Deploy publicly with Docker Compose. Configure client MCP entries with the endpoint URL and an API key (obtained from the dashboard after Google OAuth login).

Key features of Google Trends MCP

  • Four MCP tools: compare_keywords, research_keywords, research_keywords_async, get_research_task
  • Cross-batch normalization using an anchor keyword for comparability
  • Supports up to 50 keywords in a single research request
  • Multiple access methods: MCP protocol, REST API, and GPT Actions
  • Production-grade frontend with bilingual SaaS landing page, dashboard, and documentation
  • Docker Compose deployment with automatic HTTPS and Google OAuth authentication

Use cases of Google Trends MCP

  • Compare trending keywords over time to inform content strategy
  • Batch research dozens of keywords for competitive analysis and SEO planning
  • Integrate real-time Google Trends data into AI-driven market research workflows

よくある質問

1

What should I do if I hit a Google Trends 429 rate limit?

The server has built-in 1–3 second random delays and backoff retries. If you still hit limits, reduce call frequency, set an HTTPS proxy, or switch to the `trendspy` provider.

2

Why can’t I use print() in stdio mode?

In stdio mode, `stdout` carries MCP JSON-RPC protocol messages; ordinary text would break the protocol. Logs must be written to `stderr`. Only `--smoke-test` mode allows JSON output to stdout.

3

How is compare_keywords different from research_keywords?

`compare_keywords` returns raw Google Trends batch-relative scores for up to 5 keywords. `research_keywords` returns cross-batch normalized estimates using an anchor keyword, suitable for directional research across many keywords.

4

How fast is a batch research request?

With 2–4 concurrent threads and random delays, 10 keywords take about 5–10 seconds; 50 keywords take about 15–30 seconds. In-process caching (default 15 minutes) skips network calls for repeated requests.

5

What if I don’t have Google OAuth for local development?

When `GOOGLE_CLIENT_ID` is not set, the server enters dev mode. Visit `/auth/dev-login` to log in with a virtual account — no Google account needed.

コメント

「その他」の他のコンテンツ