AI News MCP Server
Allows automated refresh of the AI news cache via a scheduled Lambda function.
Provides AI-powered summarisation of AI news articles.
Fetches AI news from curated RSS feeds.
Click 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., "@AI News MCP Serverget me the latest AI news briefing"
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.
AI News MCP Server
A local stdio MCP server that fetches recent AI news from curated RSS feeds, summarises it with OpenAI, and can read a private AWS DynamoDB cache.
MCP Tools
list_ai_news_sourcesget_latest_ai_newsget_cached_ai_news
Related MCP server: OmniWire-MCP
MCP Prompts
daily_ai_news_briefingtopic_watchcompare_ai_sourcesexecutive_ai_digest
Local Setup
$env:UV_CACHE_DIR = ".uv-cache"
uv sync --python C:\Python311\python.exeSet local OpenAI credentials for live local summaries:
$env:OPENAI_API_KEY = "your_api_key_here"
$env:OPENAI_MODEL = "gpt-5.4-mini"Run the local MCP server:
uv run news-mcpLocal Tests
$env:UV_CACHE_DIR = ".uv-cache"
uv run pytestAWS Cache Flow
The CDK stack creates:
DynamoDB table
AiNewsCacheSecrets Manager secret
news-mcp/openai-api-keyLambda refresh function
EventBridge schedule that runs every 3 hours
IAM permissions for Lambda to read the secret and write DynamoDB
The Lambda writes the latest briefing to:
pk = BRIEFING
sk = LATESTBuild And Deploy AWS Cache
Rebuild the Lambda package after changing lambda_refresh/handler.py or lambda_refresh/requirements.txt:
.\scripts\build_lambda.ps1Synthesize and deploy:
$env:UV_CACHE_DIR = ".uv-cache"
$env:JSII_RUNTIME_PACKAGE_CACHE = "C:\Users\arzil\Desktop\news-mcp\.jsii-cache"
$env:NPM_CONFIG_CACHE = "C:\Users\arzil\Desktop\news-mcp\.npm-cache"
npx.cmd aws-cdk synth
npx.cmd aws-cdk deployAfter deploy, store the OpenAI key in Secrets Manager:
aws secretsmanager put-secret-value `
--secret-id news-mcp/openai-api-key `
--secret-string "YOUR_OPENAI_API_KEY_HERE"Invoke the Lambda once to populate the cache:
aws lambda list-functions --query "Functions[?contains(FunctionName, 'NewsCacheRefreshFunction')].FunctionName" --output table
aws lambda invoke `
--function-name "PASTE_FUNCTION_NAME_HERE" `
--payload "{}" `
lambda-output.jsonTest AWS-Backed MCP Tool
Inspector can be awkward on Windows, so this script tests the MCP protocol directly:
$env:AI_NEWS_CACHE_TABLE = "AiNewsCache"
$env:AWS_DEFAULT_REGION = "eu-west-2"
uv run python scripts\test_mcp_cached.pyYou should see the available tools and a cached news result with:
"cache_error": nullSource Configuration
RSS sources live in sources.toml. Disable a source by setting:
enabled = falseAvailable Tools
3 toolsget_cached_ai_newsD
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
get_latest_ai_newsD
| Name | Required | Description | Default |
|---|---|---|---|
| hours | No | ||
| limit | No | ||
| topics | No | ||
| source_ids | No |
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
list_ai_news_sourcesD
| Name | Required | Description | Default |
|---|---|---|---|
No parameters | |||
Output Schema
| Name | Required | Description |
|---|---|---|
No output parameters | ||
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
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.
3 tool updates
v0.1.0- First observed
get_cached_ai_news - First observed
get_latest_ai_news - First observed
list_ai_news_sources
TDQS
Each tool targets a distinct action: one retrieves cached news, one gets latest news, one lists sources. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case: get_cached_ai_news, get_latest_ai_news, list_ai_news_sources.
Three tools is appropriate for a focused news server; not too few or too many.
Covers cached and latest news retrieval and source listing, but lacks search or other advanced features. Minor gap.
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
Real-time curated crypto news for AI agents with sentiment, recaps, and search.
Summarize URLs, repurpose content, daily news digests, find competitors. Cost telemetry built in.
Your curated sources (RSS, YouTube, podcasts, Google News) as context for any AI agent. 26 tools.
Cross-source news (AP, BBC, NPR, HN, Google News) with topic filtering and dedup.
Related MCP Servers
- FlicenseAqualityDmaintenanceFetches RSS feeds from tech blogs and news sites and returns AI-generated summaries via Claude.15-
- AlicenseCqualityCmaintenanceEnables AI models to fetch and aggregate news from RSS, Atom, JSON, and HTML feeds with fault-tolerant circuit breaker protection.4146MIT
- FlicenseNot gradedqualityCmaintenanceProvides access to the latest AI trends by querying Google News RSS and Hacker News API, enabling AI assistants to retrieve real-time trending topics.-
- AlicenseNot gradedqualityCmaintenanceEnables AI to manage RSS subscriptions, fetch and summarize news, and organize results into tools like Notion.143MIT
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/sp716/news-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server