rss-news
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RSS_MCP_DEBUG | No | set 1 or true to enable debug logs | |
| RSS_MCP_DB_PATH | No | SQLite path (default: %APPDATA%/rss-news/rss.sqlite on Windows, ~/.local/share/rss-news/rss.sqlite on other platforms) | ~/.local/share/rss-news/rss.sqlite |
| RSS_MCP_USER_AGENT | No | custom request User-Agent | |
| RSS_MCP_REQUEST_TIMEOUT_MS | No | fetch timeout in milliseconds (default: 15000) | 15000 |
| RSS_MCP_DEFAULT_FETCH_LIMIT | No | default global fetch limit (default: 20) | 20 |
| RSS_MCP_DEBUG_PREVIEW_LENGTH | No | preview length of response body for debug (default: 300) | 300 |
| RSS_MCP_MAX_FEEDS_PER_REQUEST | No | max feed count for each call (default: 50) | 50 |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_subscriptionsA | List subscribed RSS feeds and their current sync metadata. |
| upsert_subscriptionsA | Create or update RSS subscriptions and return canonical feedUrls. Known RSSHub instance URLs are stored as rsshub://.... |
| remove_subscriptionsA | Remove RSS subscriptions, with optional purge of stored entries and read state. RSSHub subscriptions must be removed using their stored rsshub://... feedUrl. |
| preview_feedA | Preview one or more feed URLs without subscribing, for example to verify fetchability and content before subscribing. Known RSSHub instance URLs are normalized to rsshub://.... For example, RSSHub routes can be discovered at https://docs.rsshub.app/routes/. |
| sync_newsC | Fetch subscribed RSS feeds and update stored entries. |
| fetch_newsA | Read the latest news from local storage without changing read state. Unsubscribed feedUrls are not allowed. |
| consume_newsC | Read the latest news and mark unread items as consumed. |
| count_newsC | Count recent news items across subscribed feeds. |
| set_consumption_statusC | Set consumed or unconsumed status for stored news within a UTC date range. |
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 9 tools
Each tool targets a distinct action: subscription management, previewing, syncing, reading, consuming, counting, and updating read state are clearly separated. The only slight overlap is between fetch_news and consume_news, but the read-state difference is explicitly described, so confusion is unlikely.
Tool names consistently follow a verb_noun pattern: list_subscriptions, upsert_subscriptions, remove_subscriptions, preview_feed, sync_news, fetch_news, consume_news, count_news, set_consumption_status. The naming is uniform, predictable, and easy to navigate.
Nine tools is well within the ideal range for an RSS news server. Each tool covers a distinct part of the subscription-to-consumption workflow without redundancy or unnecessary bloat.
The toolset covers the full lifecycle: subscription management, previewing, syncing, reading, consuming, counting, and modifying consumption status. Minor gaps exist around per-item granularity, such as individual entry retrieval or single-item read-state updates, but the date-range-based status tool covers most practical needs.