rss-mcp
Related Servers
Alternatives to rss-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables intelligent RSS feed management with AI-powered semantic search, advanced filtering, and a comprehensive reading workflow. Supports OPML parsing, article organization with status tracking, and token-efficient browsing of large feed collections.5MIT
- AlicenseNot gradedqualityDmaintenanceEnables users to search a curated RSS/Atom catalog, subscribe to and collect feeds, and query collected articles through natural-language tools.2MIT
- AlicenseAqualityBmaintenanceEnables agents to subscribe to RSS and Atom feeds, fetch and cache entries, track read/unread state, read full article content, and run full-text search over a local SQLite database. Subscriptions can also be imported and exported as OPML, with all operations exposed as MCP tools over stdio.10MIT
- 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
- AlicenseAqualityCmaintenanceEnables querying a local SQLite database of curated RSS/Atom/RDF feeds through tools for latest headlines with filters, keyword search, cross-outlet coverage comparison, and source/freshness listing. Items are kept in their original language so an LLM can translate, summarize, and compare framing at query time.4Mozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceEnables searching, reading, and privately archiving news from supported publisher subscriptions, with per-user authentication via human sign-in links and separate tokens, sessions, and archives.321 PyPI1MIT
TDQS
Scored across 6 tools
feeds_ops and reader_ops both handle item retrieval and marking (e.g., fetch_items vs. inbox, mark/star in feeds_ops vs. stars in reader_ops), creating overlap that could cause misselection. show_reader_prefab_card also overlaps with reader_ops stats. Descriptions clarify intended separation, but boundaries are not crisp.
Most tools use a consistent noun_ops pattern (feeds_ops, readability_ops, reader_ops), but rss_help and rss_shutdown use a different prefix, and show_reader_prefab_card uses a verb_noun format. The mix is readable but not predictable.
Six tools is well-scoped for an RSS reader daemon. Each tool has a clear role: feed lifecycle, extraction, reading surface, help, shutdown, and a presentation card. None feels redundant or excessive.
The surface covers the full RSS reader lifecycle: subscription management (subscribe/unsubscribe/list/refresh/remove/OPML/health), article extraction and caching, reading inbox/stars/search/stats, background RAG sweeps, help, and graceful shutdown. No obvious operational gaps remain.