freshrss-mcp
Related Servers
Alternatives to freshrss-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to read and manage FreshRSS feeds, including listing subscriptions, browsing articles, marking read/unread, and starring.-
- AlicenseNot gradedqualityDmaintenanceEnables interaction with RSS readers that support the FreshRSS API through natural language. Allows users to manage and query their RSS feeds and articles via LLM conversations.7MIT
- AlicenseBqualityDmaintenanceEnables interaction with FreshRSS instances through the Google Reader API. Supports managing articles, feeds, folders, labels, and OPML import/export for RSS feed aggregation through natural language.2734 npm2MIT
- AlicenseAqualityDmaintenanceEnables interaction with a FreshRSS instance to manage RSS feeds, read and organize articles, and handle subscriptions through natural language.18MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to interact with FreshRSS feeds via the Fever API, allowing listing feeds, fetching unread items, marking items as read/unread, and managing feed subscriptions.86 npm10MIT
- FlicenseNot gradedqualityDmaintenanceEnables interaction with FreshRSS RSS feed readers through the Google Reader compatible API. Supports feed management, article reading/searching, and marking articles as read or starred.-
TDQS
Scored across 18 tools
Each tool maps to a distinct resource/action pair (feeds, categories, articles, OPML, read/star state), and descriptions clarify parameters and stream semantics. Minor overlap exists: freshrss_get_unread_counts partially duplicates data from list_feeds/list_categories, and mark_all_read overlaps conceptually with mark_read, but boundaries remain clear.
All tools share the freshrss_ prefix with a consistent snake_case verb_noun pattern (list_feeds, get_article, mark_read, delete_category). Even the paired state toggles (mark_read/mark_unread, star/unstar) follow a predictable symmetry.
18 tools is slightly on the heavy side but each covers a genuine operation across feeds, categories, articles and OPML. Nothing appears redundant enough to remove, though the count sits at the upper edge of a comfortable set.
Strong lifecycle coverage: feed subscribe/edit/unsubscribe/list, category list/rename/delete, article read/search/mark/star, and bidirectional OPML. Gaps are minor — there is no standalone create_category (only implicit via subscribe) and no feed URL/refresh-settings update.