Google News MCP Server
模型上下文协议 (MCP) 服务器实现,通过 SerpAPI 集成提供 Google 新闻搜索功能。自动对新闻结果进行分类,并支持多种语言和地区。
https://github.com/user-attachments/assets/1cc71c27-f840-4c94-9ab5-460d84ba4779
✨ 特点
🔍 灵活的搜索选项
全面的搜索功能,包括基于查询的搜索、主题搜索、出版物过滤和故事报道。
🌐 全球覆盖
通过可配置的语言和国家代码支持多种语言和地区。
📊 智能分类
自动将新闻结果分类为人工智能与技术、商业、科学与研究和医疗保健等主题。
🔀 多种结果类型
处理各种新闻结果类型,包括标题、故事、相关主题和菜单链接。
🛠️ 强大的错误处理
针对 API 故障和无效输入进行全面的错误处理,并提供有用的错误消息。
🌍 语言支持
对于不支持的语言代码,自动恢复为英语,并发出适当的用户通知。
🔑 SERP API 设置指南
开始之前,您需要获取 SERP API 密钥。具体方法如下:
访问SERP API 网站并创建帐户
注册后,转到您的仪表板:
找到“API 密钥”部分
复制您的 API 密钥
新用户可获得 100 次免费 API 调用
API 使用详情:
免费套餐:每月 100 次搜索
付费计划起价为每月 50 美元,可进行 5000 次搜索
根据成功的 API 调用计费
多种付款方式:信用卡、PayPal等。
使用限制:
请求率:每秒 2 个请求
IP限制:无
并发请求:5
响应缓存时间:1小时
👩🔧 MCP 服务器与 NVM/NPM 连接问题解决方案
点击查看我的配置解决方案👉https: //github.com/modelcontextprotocol/servers/issues/76
🚀 快速入门
安装依赖项:
npm install构建服务器:
npm run build配置环境:使用以下内容修改您的
claude_desktop_config.json(根据您的系统调整路径):
"google-news": {
"command": "D:\\Program\\nvm\\node.exe",
"args": [
"D:\\github_repository\\path_to\\dist\\index.js"
],
"env": {
"SERP_API_KEY": "your-api-key"
}
}启动服务器:
npm start故障排除
API 密钥无效
验证
claude_desktop_config.json中的 API 密钥配置确认 API 密钥在 SERP API 仪表板中处于活动状态
请求失败
检查网络连接
验证 API 调用配额是否未超出
验证请求参数格式
Related MCP server: Google News13 MCP Server
运行评估
evals 包会加载一个 mcp 客户端,然后运行 index.ts 文件,因此测试之间无需重新构建。您可以通过在 npx 命令前添加前缀来加载环境变量。完整文档可在此处找到。
OPENAI_API_KEY=your-key npx mcp-eval src/evals/evals.ts src/index.ts📦安装
通过 Smithery 安装
要通过Smithery自动为 Claude Desktop 安装 Google 新闻:
npx -y @smithery/cli install @chanmeng666/google-news-server --client claude通过 mcp-get 安装
npx @michaellatman/mcp-get@latest install @chanmeng666/google-news-server如果您使用的是旧版本的 Windows PowerShell,则可能需要在执行此命令之前运行
Set-ExecutionPolicy Bypass -Scope Process。
手动安装
@chanmeng666/google新闻服务器
# Using npm
npm i @chanmeng666/google-news-server
# or
npm install @chanmeng666/google-news-server
# Using yarn
yarn add @chanmeng666/google-news-server
# Using pnpm
pnpm add @chanmeng666/google-news-server💻 技术栈
📖 API 文档
服务器实现了模型上下文协议,并公开了一个具有以下参数的 Google 新闻搜索工具:
q:搜索查询字符串gl:国家代码(例如“us”、“uk”)hl:语言代码(例如,'en'、'es')topic_token:特定新闻主题的令牌publication_token:特定发布者的令牌story_token:用于全面报道故事的令牌section_token:特定部分的令牌
🔧 开发
# Run in development mode with hot reload
npm run dev
# Run linting
npm run lint
# Run tests
npm run test📝 许可证
该项目已获得 MIT 许可。
🙋♀ 作者
由Chan Meng创建并维护。
Available Tools
1 toolgoogle_news_searchA
Search Google News for articles and news content. Results will be automatically categorized by topic.
| Name | Required | Description | Default |
|---|---|---|---|
| q | No | Search query | |
| gl | No | Country code (e.g., us, uk) | us |
| hl | No | Language code (e.g., en) | en |
| story_token | No | Story token for full coverage of a story | |
| topic_token | No | Topic token for specific news topics | |
| section_token | No | Section token for specific sections | |
| publication_token | No | Publication token for specific publishers |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It discloses that results are automatically categorized by topic, adding some behavioral context, but lacks details on rate limits, authentication, or mutation implications.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
Two short, front-loaded sentences with no wasted words. Every sentence adds value: the first states the action, the second adds a behavioral trait.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With 7 parameters and no output schema or annotations, the description is too brief. It does not explain return format, pagination, or how to use the various tokens (story, topic, section, publication). A user would need external knowledge.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema coverage is 100%, so the schema already documents all 7 parameters. The description does not add meaning beyond the schema, meeting the baseline for high coverage.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the verb (Search) and resource (Google News for articles and news content), and adds that results are categorized by topic, which distinguishes it from generic web searches.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies usage for searching news but provides no explicit guidance on when to use this tool versus alternatives or when not to use it. It relies on self-evident purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
v1.0.1- First observed
google_news_search
TDQS
With only one tool, there is no possibility of confusion between tools. The tool's purpose is clearly stated.
Single tool follows a clear and conventional naming pattern; no inconsistencies exist.
A single tool for a news search server is too minimal. Users expect additional functionality such as filtering by category or retrieving article details.
The tool only provides search capability, missing essential news operations like reading full articles, date filtering, or topic-specific queries.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Google News headlines, sources, and links via the Apify Google News API, hosted MCP.
12 Google News endpoints. Pay per call in USDC via x402.
Cross-source news (AP, BBC, NPR, HN, Google News) with topic filtering and dedup.
MCP server for Google search results via SERP API
Related MCP Servers
- AlicenseBqualityDmaintenanceThis server allows users to perform web searches using Perplexity AI, providing a tool for retrieving search results through a simple API interface.1753Apache 2.0
- AlicenseBqualityDmaintenanceProvides tools to search and retrieve news across various categories including business, technology, science, and sports via the Google News API. It supports keyword searches, autocomplete suggestions, and region-specific news across multiple languages.11MIT
- FlicenseNot gradedqualityFmaintenanceMCP server providing access to the GNews API for fetching news articles and headlines. Supports search and top headlines with advanced filtering by language, country, category, and date.1-
- FlicenseNot gradedqualityCmaintenanceA server that provides tools to search news articles and fetch top headlines using the GNews API.-
Appeared in Searches
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/ChanMeng666/server-google-news'
If you have feedback or need assistance with the MCP directory API, please join our Discord server