Skip to main content
Glama
sp716
by sp716

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_sources

  • get_latest_ai_news

  • get_cached_ai_news

Related MCP server: OmniWire-MCP

MCP Prompts

  • daily_ai_news_briefing

  • topic_watch

  • compare_ai_sources

  • executive_ai_digest

Local Setup

$env:UV_CACHE_DIR = ".uv-cache"
uv sync --python C:\Python311\python.exe

Set 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-mcp

Local Tests

$env:UV_CACHE_DIR = ".uv-cache"
uv run pytest

AWS Cache Flow

The CDK stack creates:

  • DynamoDB table AiNewsCache

  • Secrets Manager secret news-mcp/openai-api-key

  • Lambda 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 = LATEST

Build And Deploy AWS Cache

Rebuild the Lambda package after changing lambda_refresh/handler.py or lambda_refresh/requirements.txt:

.\scripts\build_lambda.ps1

Synthesize 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 deploy

After 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.json

Test 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.py

You should see the available tools and a cached news result with:

"cache_error": null

Source Configuration

RSS sources live in sources.toml. Disable a source by setting:

enabled = false

Available Tools

3 tools
get_cached_ai_newsD
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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
ParametersJSON Schema
NameRequiredDescriptionDefault
hoursNo
limitNo
topicsNo
source_idsNo

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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
ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription

No output parameters

TDQS

D1/5.0
Behavior1/5

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.

Conciseness1/5

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.

Completeness1/5

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.

Parameters1/5

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.

Purpose1/5

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.

Usage Guidelines1/5

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.

  1. 3 tool updatesv0.1.0
    • First observedget_cached_ai_news
    • First observedget_latest_ai_news
    • First observedlist_ai_news_sources

TDQS

C2.1/5.0
Disambiguation5/5

Each tool targets a distinct action: one retrieves cached news, one gets latest news, one lists sources. No overlap.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case: get_cached_ai_news, get_latest_ai_news, list_ai_news_sources.

Tool Count5/5

Three tools is appropriate for a focused news server; not too few or too many.

Completeness4/5

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

Related MCP Servers

  • A
    license
    C
    quality
    C
    maintenance
    Enables AI models to fetch and aggregate news from RSS, Atom, JSON, and HTML feeds with fault-tolerant circuit breaker protection.
    4
    14
    6
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Provides access to the latest AI trends by querying Google News RSS and Hacker News API, enabling AI assistants to retrieve real-time trending topics.
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI to manage RSS subscriptions, fetch and summarize news, and organize results into tools like Notion.
    14
    3
    MIT

Latest Blog Posts

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