Juhe News MCP Server
OfficialClick on "Install 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., "@Juhe News MCP Servershow me the latest tech news headlines"
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.
Juhe News MCP Server
一个提供新闻头条信息功能的模型上下文协议(Model Context Protocol)服务器。该服务器使大型语言模型(LLMs)能够获取当前最新的热点新闻头条(包括:推荐、国内、科技、体育等类型)及详细内容信息。
Components
Tools
服务器实现了两个工具:
get_news_list: 根据新闻类型获取今日热点新闻头条
需要传入 "type"(新闻类型)作为选填的字符串参数。
async def get_news_list(type: str = "top", page: int = 1, page_size: int = 20) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:get_news_content: 根据新闻类型获取今日热点新闻头条
需要传入 "uniquekey"(新闻id)作为必须的字符串参数。
async def get_news_content(uniquekey: str) -> list[types.TextContent | types.ImageContent | types.EmbeddedResource]:Related MCP server: Pulse CN MCP Server
Install
This server requires Python 3.10 or higher. Install dependencies using uv (recommended) or pip
Using uv (recommended)
When using uv no specific installation is needed. We will use uvx to directly run jnews-mcp-server.
uvx jnews-mcp-serverUsing PIP
Alternatively you can install jnews-mcp-server via pip:
pip install jnews-mcp-serverAfter installation, you can run it as a script using:
python -m jnews_mcp_serverConfiguration
Environment Variables
JUHE_NEWS_API_KEY: 聚合数据的新闻头条API密钥。获取:https://www.juhe.cn/docs/api/id/235
JUHE_NEWS_API_KEY=your_api_keyClaude Desktop
On MacOS:
~/Library/Application\ Support/Claude/claude_desktop_config.jsonOn Windows:
%APPDATA%/Claude/claude_desktop_config.json
"mcpServers": {
"jnews-mcp-server": {
"command": "uvx",
"args": [
"jnews-mcp-server"
],
"env": {
"JUHE_NEWS_API_KEY": "your_api_key"
}
}
}"mcpServers": {
"jnews-mcp-server": {
"command": "python",
"args": [
"-m",
"jnews_mcp_server"
],
"env": {
"JUHE_NEWS_API_KEY": "your_api_key"
}
}
}Debugging
You can use the MCP inspector to debug the server. For uvx installations:
npx @modelcontextprotocol/inspector uvx jnews-mcp-server Or if you've installed the package in a specific directory or are developing on it:
cd path/to/servers/src/jnews-mcp-server
npx @modelcontextprotocol/inspector uv run jnews-mcp-serverExamples of Questions for Cline
"今日有哪些热点新闻?"
"当前体育热点头条?"
"第5条新闻的详细内容"
Available Tools
2 toolsget_news_contentB
根据新闻ID获取新闻的详细内容
| Name | Required | Description | Default |
|---|---|---|---|
| uniquekey | Yes | 新闻ID(gew_news_list中返回的uniquekey) |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, and the description lacks details about behavioral traits such as read-only nature, authentication requirements, error handling, or response format. It only implies a read operation through the verb 'get'.
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?
The description is extremely concise (one sentence) and directly conveys the core purpose. It is front-loaded and wastes no words, though it could include more context without sacrificing brevity.
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?
For a simple retrieval tool with one parameter and no output schema, the description is adequate but not complete. It does not specify the structure or scope of the detailed content, nor any edge cases like missing IDs.
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?
The input schema has 100% coverage with a clear description for the only parameter. The tool description adds no additional meaning beyond what the schema already provides, so baseline score is appropriate.
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 action (获取/get) and resource (新闻详细内容/detailed news content) with a specific identifier (by news ID). It distinguishes from the sibling tool get_news_list, which likely returns a list, by specifying 'detailed content'.
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 does not explicitly state when to use or not use this tool, but it indicates the prerequisite by mentioning the origin of the uniquekey (from get_news_list), providing implicit context for usage.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_news_listA
通过新闻类型获取今日热点新闻头条
| Name | Required | Description | Default |
|---|---|---|---|
| type | No | 新闻类型:top(推荐,默认),guonei(国内),guoji(国际),yule(娱乐),tiyu(体育),junshi(军事),keji(科技),caijing(财经),youxi(游戏),qiche(汽车),jiankang(健康) | |
| page | No | 当前页数, 默认1, 最大50 | |
| page_size | No | 每页返回新闻条数, 默认20, 最大50 |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided; description does not disclose any behavioral traits beyond the input schema. No mention of rate limits, pagination behavior, or data freshness.
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?
Single sentence, no filler. Perfectly concise for its purpose.
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?
Description is sufficient for a simple list tool but lacks context about output format (e.g., returns news items with title and id). With no output schema, the description could be more helpful.
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 covers 100% of parameters with descriptions. The tool description adds no additional meaning beyond what the schema already provides.
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?
Description clearly states the tool fetches today's hot news headlines (资源) filtered by news type (维度). The verb '获取' is specific. It distinguishes from sibling tool get_news_content, which likely retrieves full article content.
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?
Description implicitly indicates use for browsing headlines, but lacks explicit guidance on when to use this versus get_news_content. No exclusions or prerequisites are mentioned.
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.
2 tool updates
- First observed
get_news_content - First observed
get_news_list
TDQS
The two tools have clearly distinct purposes: one lists news by type, the other retrieves detailed content by ID. There is no overlap or ambiguity.
Both tools follow a consistent snake_case pattern with the 'get_' prefix and a descriptive noun, making them predictable and easy to understand.
With only two tools, the set is minimal for a news server. It covers basic listing and detail retrieval, but feels thin compared to typical news APIs that include search, categories, or pagination.
The tool surface lacks essential operations such as searching news, filtering by date or category, or pagination. Users cannot navigate beyond today's hot headlines, which is a significant gap for a comprehensive news service.
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
Dive into the latest and greatest from the tech world with our Hacker News MCP server.
Real-time news and trending topics from major sources
Free cross-lingual news briefings for AI agents across 89 languages. Read-only, hosted.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseBqualityCmaintenanceA Model Context Protocol server that provides real-time hot trending topics from major Chinese social platforms and news sites.11,706201MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides AI models with real-time trending content from 18 major Chinese internet platforms, including Weibo, Zhihu, and Bilibili.13-
- AlicenseAqualityBmaintenanceA real-time news and hot spot aggregation server that monitors multiple platforms like Weibo, Zhihu, and Bilibili. It enables AI assistants to fetch, filter, and analyze trending topics through the Model Context Protocol for personalized information tracking.131GPL 3.0
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol server that retrieves Bangla news headlines and allows querying news by topic for integration with LLMs.4MIT
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/juhemcp/jnews-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server