Google Trends MCP Server
Provides access to Google Trends data, including trending topics, trending questions, and API status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Google Trends MCP Server what are the top trending topics right now?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Google Trends MCP Server
⚠️ IMPORTANT SECURITY NOTICE: Never commit API keys to version control. This package requires an API key to be set via environment variable.
An MCP (Model Context Protocol) server that provides access to Google Trends data through the Google Trends Scraper API.
Features
Status: Check the API status and health
Questions: Get trending questions from Google Trends
Trending: Get currently trending topics from Google Trends
Related MCP server: bigquery-google-trends-mcp
Installation
Option 1: Using npx (Recommended)
# Set your API key first
export GOOGLE_TRENDS_API_KEY="your-api-key-here"
# Run directly with npx
npx @andrewlwn77/google-trends-mcpOption 2: Global Installation
npm install -g @andrewlwn77/google-trends-mcpOption 3: Local Development
git clone <repository-url>
cd google-trends-mcp
npm install
npm run buildConfiguration
Optional: You can set the GOOGLE_TRENDS_API_KEY environment variable. If not set, a default API key will be used.
Get an API key from RapidAPI Google Trends Scraper
Set the environment variable:
# Option 1: Export in your shell export GOOGLE_TRENDS_API_KEY="your-api-key-here" # Option 2: Create a .env file (for local development) echo "GOOGLE_TRENDS_API_KEY=your-api-key-here" > .env
⚠️ Security: Never commit your .env file or API key to version control!
Usage
Running the server
# If installed globally or using npx
google-trends-mcp
# For local development
npm start
# For development with auto-reload
npm run devAvailable Tools
1. google_trends_status
Check the status of the Google Trends API.
Parameters:
language(optional): Language code (default: "en")country(optional): Country code (default: "US")
2. google_trends_questions
Get trending questions from Google Trends.
Parameters:
language(optional): Language code (default: "en")country(optional): Country code (default: "US")
3. google_trends_trending
Get currently trending topics from Google Trends.
Parameters:
language(optional): Language code (default: "en")country(optional): Country code (default: "US")
Example Usage with MCP Client
// Check API status
const status = await client.callTool('google_trends_status', {
language: 'en',
country: 'US'
});
// Get trending questions
const questions = await client.callTool('google_trends_questions', {
language: 'en',
country: 'US'
});
// Get trending topics
const trending = await client.callTool('google_trends_trending', {
language: 'en',
country: 'US'
});Configuration
The server can be configured using environment variables:
GOOGLE_TRENDS_API_KEY: Your RapidAPI key for the Google Trends Scraper API (optional, defaults to example key)
Development
Project Structure
google-trends-mcp/
├── src/
│ ├── index.ts # Main MCP server implementation
│ └── types.ts # TypeScript type definitions
├── tests/
│ ├── integration/ # API integration tests
│ ├── unit/ # Unit tests
│ └── helpers/ # Test helper utilities
├── package.json
├── tsconfig.json
├── .env.example
└── README.mdType Safety
This server is written in TypeScript and provides full type safety for:
API parameters
API responses
Error handling
Google Trends data structures
License
MIT
Available Tools
3 toolsgoogle_trends_questionsC
Get trending questions from Google Trends
Inputs: country, language.
google_trends_statusC
Check the status of the Google Trends API
Inputs: country, language.
google_trends_trendingB
Get currently trending topics from Google Trends
Inputs: country, language.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: one for trending questions, one for API status, and one for currently trending topics. There is no overlap or ambiguity.
All tools follow a consistent `google_trends_<noun>` pattern, with clear, descriptive names. The verb (get) is implied, and the naming is uniform.
Three tools is minimal but reasonable for a focused server. The count covers the core functionalities—trending topics, related questions, and status—without being excessive.
The server covers basic features like trending topics and questions but lacks tools for specific search queries (e.g., interest over time, comparisons). The surface is functional but not comprehensive.
Maintenance
Related MCP Connectors
Google Trends: Search, Images, News, Shopping over time, growth metrics. Free key at trendsmcp.ai
Google trending searches API + MCP: 30 countries, day lists, 30-day history. $5 pack; 50 free/day.
Bulk Google Trends: interest over time, regions, rising queries and plain-English trend summaries.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceProvides Google Search trend data as an MCP tool, with historical series, growth percentages, and live trending searches, no scraping or rate limits.1MIT
- FlicenseNot gradedqualityDmaintenanceMCP 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.-
- AlicenseAqualityDmaintenanceProvides 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.5147 npm2MIT
- AlicenseAqualityBmaintenanceEnables querying Google Trends data directly from conversational MCP clients, including search interest over time, related queries and topics, regional breakdowns, and trending searches, for market research without leaving the chat.112MIT