rss-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RSS_MCP_DB | No | Path to the local SQLite file that stores subscriptions, cached entries, unread state, and full-text search data. | ~/.local/share/rss-mcp/rss.db |
| RSS_MCP_USER_AGENT | No | User-Agent header used when fetching feeds. | rss-mcp/0.1 (+https://github.com/huangcheng/rss-mcp) |
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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_subscriptionA | Add a feed by URL. Repeating a URL returns the existing subscription. |
| remove_subscriptionB | Delete a subscription and its cached entries. |
| list_subscriptionsB | List subscriptions with unread counts. |
| fetch_feedA | Fetch one subscription, or every subscription when the id is omitted. |
| list_entriesB | List cached entries (bodies omitted). Limit falls back to the server default and is clamped. |
| read_entryB | Return one entry. fetch_full replaces content only when article text is returned. mark_read sets read state. |
| search_entriesA | Full-text search over cached title, summary, and content. Omits entry bodies; use read_entry for full content. |
| mark_entryA | Mark entries read or unread. Unknown ids are skipped. |
| import_opmlB | Add each OPML feed. Existing URLs are skipped. |
| export_opmlB | Export subscriptions as an OPML document. |
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 10 tools
Most tools map to distinct resource+action pairs (subscriptions vs. entries vs. OPML), and descriptions clarify boundaries like cached listing vs. network fetch. Minor overlap remains: add_subscription vs. import_opml both add feeds, and read_entry's mark_read flag partially duplicates mark_entry.
Every tool is snake_case verb_noun (add_subscription, list_entries, read_entry, export_opml), with consistent verb choices (list/read/search/fetch/mark) across resources. No convention mixing.
Ten tools is well within the ideal range and each covers a distinct part of the RSS lifecycle: subscription management, fetching, entry reading/searching, read state, and OPML transfer. No tool feels redundant or padded.
The surface covers the core lifecycle: add/remove/list subscriptions, fetch, list/read/search entries, mark read state, and OPML import/export. Gaps are minor, such as no update/edit for an existing subscription (rename, polling settings) and no folder/category grouping.