A
licenseB
qualityB
maintenanceMCP server for FreshRSS RSS reader enabling feed reading, subscription management, and item actions via the Google Reader compatible API.
12
MIT
freshrss-mcp
by ni-c
Related Servers
Alternatives to freshrss-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for interacting with FreshRSS via the Google Reader API, enabling subscription management, content reading, and item operations.2MIT
- AlicenseAqualityCmaintenanceAn MCP server for managing and querying RSS/news feeds, enabling real-time fetching, searching, and retrieval of feed items.514 npm1MIT
- AlicenseBqualityDmaintenanceAn MCP server for RSS feed aggregation and article content extraction, allowing users to subscribe to feeds and extract full article content as Markdown.2203 npm5MIT
- FlicenseNot gradedqualityCmaintenanceA self-hosted RSS reader MCP server that manages RSS subscriptions and fetches live feed content, deployable on AWS.-
- AlicenseBqualityDmaintenanceAn MCP server that provides RSS feed tools for Claude Desktop, enabling fetching and parsing RSS feeds with configurable feeds and blocklists.6MIT
TDQS
A4.5/5.0
Scored across 16 tools
Disambiguation5/5
Each tool has a clearly distinct purpose with no overlapping functionality. For example, 'list_articles' and 'get_articles' are differentiated by scope (list vs. full text), and 'mark_articles' vs 'mark_all_as_read' are distinct in granularity.
Naming Consistency5/5
Tool names follow a consistent verb_noun pattern (e.g., get_user_info, list_feeds, subscribe_feed, export_opml) with occasional modifiers (all_as_read, category_or_label) but remain uniform and predictable. No mixed conventions like camelCase or inconsistent verbs.
Tool Count4/5
With 16 tools, the set is slightly above the typical 3–15 range but each tool serves a necessary function for a feed reader, covering subscription management, article handling, and OPML operations. The count feels justified rather than bloated.
Completeness5/5
The tool surface covers the full lifecycle of feed management: reading (list/get), writing (subscribe/update/unsubscribe), marking read states, category operations, and OPML import/export. The absence of search is explicitly noted as an API limitation, and alternatives are provided, so no critical gaps exist.
Maintenance
ActivityNo data
ResponsivenessSyncing