An MCP server to access RSS feeds of Google News and Google Trends
An MCP server to access RSS feeds of Google News and Google Trends. That is what the google mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
An MCP server that slurps data from Google News and Google Trends RSS endpoints, optionally distills it with LLM/NLP, and barfs out structured results.
The server publishes 5 tools. What each one is for:
get_news_by_keyword — Search for news using specific keywordsget_news_by_location — Retrieve news relevant to a particular locationget_news_by_topic — Get news based on a chosen topicget_top_news — Fetch the top news stories from Google Newsget_trending_keywords — Return trending keywords from Google Trends for a specified locationThe server ships on npm as @modelcontextprotocol/inspector, so your MCP client can launch it on demand — there is no separate build step. Add the server block to your client's configuration, restart it, and the tools register themselves.
Among the AI and media services options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Google's toolset — get_news_by_keyword, get_news_by_location, get_news_by_topic and 2 more — is a fair guide to whether it matches your workflow.
This entry was verified against Google's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| get_news_by_keyword | Search for news using specific keywords. |
| get_news_by_location | Retrieve news relevant to a particular location. |
| get_news_by_topic | Get news based on a chosen topic. |
| get_top_news | Fetch the top news stories from Google News. |
| get_trending_keywords | Return trending keywords from Google Trends for a specified location. |
{
"mcpServers": {
"google-news-trends": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/inspector"]
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.