Skip to main content
Glama
FeedKeeper RSS/Atom reader and remote MCP Server

FeedKeeper RSS/Atom reader and remote MCP Server

Related Servers

Alternatives to FeedKeeper RSS/Atom reader and remote MCP Server

  • A
    license
    A
    quality
    D
    maintenance
    Enables digital marketers to fetch, search, and filter RSS blog feeds from multiple sources, with tools for managing feeds and searching across categories and date ranges.
    8
    29 npm
    Apache 2.0
  • A
    license
    A
    quality
    B
    maintenance
    An MCP server for reading and managing RSS feeds from a self-hosted FreshRSS instance, enabling listing feeds, fetching articles, and subscribing/unsubscribing through the FreshRSS API.
    16
    97 npm
    4
    MIT

Related Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables 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.
    6
    MIT
  • F
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude to fetch, parse, and manage RSS/Atom feeds through the Model Context Protocol. It supports feed registration and retrieval, allowing users to access article summaries and full content from multiple sources via natural language.
    1
    -
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables Claude on web, desktop and mobile to read, mark and manage Inoreader feeds through a self-hosted remote MCP connector, exposing ten tools for unread counts, subscriptions, folders, article retrieval, starring, subscribing and marking articles read or unread.
    MIT
  • A
    license
    C
    quality
    C
    maintenance
    Enables MCP clients to authenticate with Feedbin, poll unread articles, fetch and cache full entry bodies in SQLite, and list or retrieve cached entries through the Feedbin v2 API.
    42
    MIT

TDQS

A3.8/5.0

Scored across 34 tools

Disambiguation4/5

Most tools map to a distinct resource+action (feeds, folders, editions, bookmarks, keywords, OPML), and the item-reading cluster (get_digest, get_new_items, list_items, get_item, search_items) is explicitly differentiated with 'do NOT use for...' cross-references. Still, five overlapping item-retrieval tools plus get_edition_candidates vs get_digest create real misselection risk for an agent skimming names.

Naming Consistency4/5

Almost all names follow a consistent snake_case verb_noun pattern (list_feeds, create_folder, publish_edition, mark_all_read). Minor deviations: unmute_keyword breaks the add_muted_keyword/list_muted_keywords family symmetry and fetch_full_text/save_to_inbox drop the object noun convention, but the overall pattern is predictable.

Tool Count3/5

34 tools is heavy for an RSS reader; the edition-curation workflow (get_edition, get_edition_candidates, publish_edition, dismiss_edition) and keyword-filter trio each add surface area. Every tool is individually justified, but the set is at the upper bound of what an agent can hold coherently in one server.

Completeness4/5

Broad lifecycle coverage: feeds (subscribe/discover/update/refresh/unsubscribe), folders (create/rename/delete/move/list), items (read/unread/mark-all/search/full-text), bookmarks, keyword filters, OPML import/export, inbox capture, and a full edition lifecycle. Gaps: no dedicated bookmark-listing tool (only filters on other tools) and no tag/label or item-delete operations, though these are workable around.

Maintenance

ActivityActive
ResponsivenessNo recent community issues