rss-mcp
Related Servers
Alternatives to rss-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceSecure MCP server for RSS/Atom feed reading with SQLite backend. Enables feed management, entry search, and OPML import/export.17AGPL 3.0
- AlicenseAqualityBmaintenanceStores RSS/Atom subscriptions in a local SQLite database and exposes tools over stdio for adding, refreshing, browsing, searching, and managing feed entries from an LLM client.12MIT
- AlicenseAqualityDmaintenanceFetches and reads RSS/Atom feeds, enabling MCP clients to pull latest items from blogs, news sites, and release feeds and build digests.237 npmMIT
- AlicenseAqualityCmaintenanceLocal MCP server for reading and searching RSS and Atom feeds, enabling AI assistants to fetch feed contents, search entries by keyword, and view feed metadata without any cloud intermediary.3MIT
- AlicenseAqualityCmaintenanceEnables subscribing to RSS/Atom feeds, polling them incrementally, and querying cached entries with search, summaries, and source listings. Tracks per-session consumption state so unacknowledged candidates can be surfaced for proactive notification.6MIT
- AlicenseBqualityDmaintenanceMCP server for fetching, parsing, and managing RSS feeds. Features Fetch and parse RSS/Atom feeds In-memory caching with TTL Batch fetching of multiple feeds Monitor feeds for new items Search content across multiple feeds Extract and format feed content636 npm12Apache 2.0
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.