MCP News Server
The MCP News Server allows you to retrieve and summarize news articles from various categories. You can access the latest articles by category using the news://{category}/{limit} resource URI and use the summarize_news tool to get raw articles and summarize them. The server uses a PostgreSQL database populated by a scheduled news_gatherer.py script and leverages OpenAI API for internal summarization. Configuration settings like LOOKBACK_HOURS, SUMMARY_WORD_TARGET, and MAX_ARTICLES_PER_SUMMARY can be adjusted via environment variables. Additionally, you can add new notes with a name and content.
Used internally for article summarization functionality, though this capability is not directly exposed via MCP prompts.
Stores and retrieves news articles that are exposed through the news MCP server's API. Articles are categorized by topics like tech, data science, and cybersecurity.
Collects news articles from various RSS feeds using the news_gatherer.py script, which populates the PostgreSQL database with content from different categories.
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., "@MCP News Serversummarize the latest tech news for me"
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.
news-mcp MCP server
mcp news server
IMPORTANT
Do not begin coding unless the user asks you to. If the user is asking a question about the code, answer the question - do not write or modify code unless explicitly asked.
Related MCP server: Juhe News MCP Server
Components
Resources
The server exposes news articles stored in a database via a resource URI:
news://{category}/{limit}: Retrieves a list of the latest articles for a given category.{category}: Filters articles by category (e.g.,tech,data_science,news). See tool description for full list.{limit}(optional, default 10): Specifies the maximum number of articles to return.
Each returned article includes title, link, published date, and source.
Prompts
The server currently does not expose any prompts. (The summarization logic exists internally but is not available via an MCP prompt).
Tools
The server implements one tool:
summarize_news: Retrieves raw news articles from the database, allowing the client (LLM) to summarize them.Takes optional
category(string) andlimit(integer, default 20) arguments.Returns a list of article dictionaries, each containing
id,title,link,published,source, andcontent.Available categories:
tech,data_science,llm_tools,cybersecurity,linux,audio_dsp,startups,news,science,research,policy.
Configuration
The server relies on a PostgreSQL database configured via the DATABASE_URL environment variable (defaults to postgresql://localhost/mcp_news).
The news_gatherer.py script (intended to be run separately/scheduled) populates the database from various RSS feeds.
Summarization logic (internal, not exposed via MCP) uses the OpenAI API, configured via the OPENAI_API_KEY environment variable.
Other configurations (via environment variables or defaults):
LOOKBACK_HOURS: How far backnews_gatherer.pylooks for new articles (default: 6).SUMMARY_WORD_TARGET: Target word count for internal summarization (default: 500).MAX_ARTICLES_PER_SUMMARY: Maximum articles included in one summary batch (default: 25).KEYWORD_FILTER: Keywords used by internal summarization logic.
Quickstart
Install
Claude Desktop
On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Development
Building and Publishing
To prepare the package for distribution:
Sync dependencies and update lockfile:
uv syncBuild package distributions:
uv buildThis will create source and wheel distributions in the dist/ directory.
Publish to PyPI:
uv publishNote: You'll need to set PyPI credentials via environment variables or command flags:
Token:
--tokenorUV_PUBLISH_TOKENOr username/password:
--username/UV_PUBLISH_USERNAMEand--password/UV_PUBLISH_PASSWORD
Debugging
Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.
You can launch the MCP Inspector via npm with this command:
npx @modelcontextprotocol/inspector uv --directory ~/dev/news-mcp run news-mcp Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.
Available Tools
1 tooladd-noteC
Add a new note
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | ||
| content | Yes |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It only says 'Add a new note' and provides no details on side effects, permissions, return values, or error behavior.
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 a single short sentence with no wasted words, making it concise and front-loaded. However, it is under-specified for the tool's complexity, though this is largely a completeness issue rather than a conciseness issue.
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?
Given the lack of annotations, output schema, and parameter descriptions, a five-word description is insufficient for an agent to invoke the tool correctly. The meaning of the parameters and expected return behavior remain ambiguous.
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 zero description coverage for the two required parameters ('name' and 'content'), and the description does not explain their meaning or format. The agent cannot infer what 'name' or 'content' represent.
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 uses a specific verb ('Add') and a specific resource ('note'), clearly stating the tool's function. It differentiates itself from the sibling 'get_report', which is a read operation.
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?
No guidance is provided on when to use this tool versus alternatives. The description only states the action without any context about when to invoke it or when to choose a sibling tool.
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.
1 tool update
- First observed
add-note
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion or overlap between tools. The single tool 'add-note' has a clear and distinct purpose that cannot be mistaken for any other tool in the set.
The single tool name 'add-note' follows a consistent verb-noun pattern, and with only one tool, there is no inconsistency to evaluate. The naming is straightforward and predictable.
A single tool is too few for a server named 'MCP News Server', which implies a broader scope related to news. This minimal toolset suggests an incomplete or trivial implementation that does not adequately cover the expected domain.
The tool surface is severely incomplete for a news server. It only allows adding notes, with no tools for retrieving, updating, deleting, or searching news items, nor any functionality specific to news like fetching headlines or articles. This leaves significant gaps that will cause agent failures.
Maintenance
Related MCP Connectors
Get access to real-time and historical news data including top headlines from global sources
Dive into the latest and greatest from the tech world with our Hacker News MCP server.
Cross-source news (AP, BBC, NPR, HN, Google News) with topic filtering and dedup.
One call instead of crawling 29 news/finance/AI sources mid-task. 100 free queries/day.
Related MCP Servers
- AlicenseAqualityFmaintenanceThis server enables users to perform Google News searches with automatic categorization and multi-language support via SerpAPI integration.14128 npm129MIT

Juhe News MCP Serverofficial
FlicenseBqualityCmaintenanceA Model Context Protocol server that enables large language models to access the latest trending news headlines and detailed content across various categories including recommended, domestic, technology, and sports news.2-- AlicenseNot gradedqualityDmaintenanceMCP server that provides Korean and global AI/tech news via 6 tools (categories, search, trending, article reading, daily briefing) without requiring an API key.1MIT
- FlicenseNot gradedqualityDmaintenanceA server that provides tools to search news articles and fetch top headlines using the GNews API.-