ai-news-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_trending_newsA | Aggregates real-time AI/tech news from multiple sources (HackerNews, Dev.to, Reddit, ArXiv, GitHub Trending, GeekNews, Lobsters) with 1-hour caching. Reads from Supabase cache when available, falls back to local file cache. |
| get_top_picksB | Returns top N most relevant items for AI engineers, scored by source reputation (HN/Reddit > ArXiv > others) plus item score. Each item includes a one-liner 'why it matters' and optional try_url. |
| get_repo_quickstartA | Fetches a GitHub repo's metadata (stars, description, language, topics) and extracts install commands and a quickstart code block from its README. |
| get_paper_briefA | Fetches an ArXiv paper's title, authors, abstract, and submission date. Searches Papers With Code and GitHub for associated code repositories. |
| search_todayA | Search today's cached news by keyword query. Matches against title and summary, scores by word match count × item score. Returns top results. |
| get_new_sinceA | Queries Supabase for all cache rows created after a given ISO timestamp. Returns deduplicated news items sorted newest first. Requires Supabase connection. |
| get_topic_suggestionsA | Suggests blog topic ideas based on trending news, tailored per project (potenlab, treesoop, hanguljobs) and filtered against already-used topics. |
| check_cacheA | Check the current state of the news cache — Supabase connection status, whether local/Supabase cache exists, how old it is, and how many items per source. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Tools like get_trending_news, get_top_picks, search_today, and get_new_since all return news items but with distinct mechanisms—aggregation, ranking, keyword search, and time-based filtering. Some initial confusion possible between get_trending_news and get_top_picks, but descriptions clarify their unique purposes.
Most tools follow a get_ prefix with descriptive nouns (get_repo_quickstart, get_trending_news, get_top_picks, get_paper_brief, get_new_since, get_topic_suggestions), but search_today and check_cache deviate from this pattern. Still, the naming is largely predictable and readable.
With 8 tools covering news aggregation, search, ranking, paper/research lookups, repository quickstarts, topic suggestions, and cache status, the tool count is well-suited to the server's purpose. No tool feels redundant or unnecessary.
The tool surface covers the main workflows: retrieving trending news, searching it, getting top picks, fetching paper briefs and repo quickstarts, suggesting blog topics, and checking cache health. Minor omissions like fetching a specific news item by ID or source-specific filtering are workaround-able through search and time-based retrieval.