Skip to main content
Glama

Related Servers

Alternatives to rss-publisher-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      301 PyPI
      MIT
    • 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
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      19 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to search a curated RSS/Atom catalog, subscribe to and collect feeds, and query collected articles through natural-language tools.
      2
      MIT

    TDQS

    B3.3/5.0

    Scored across 16 tools

    Disambiguation4/5

    Most tools map cleanly to distinct lifecycle actions: create, update, correct, retract, unpublish, republish, and feed/validation operations are well separated. The main ambiguity is between correct_entry and update_entry, since both modify an entry while preserving its identity; the correction framing helps but could overlap for simple edits.

    Naming Consistency5/5

    All tools follow a consistent snake_case verb_noun pattern with clear verbs such as get, list, create, update, validate, audit, and rebuild. Even specialized actions like correct_entry, retract_entry, unpublish_entry, and republish_entry use the same convention, making the set predictable.

    Tool Count4/5

    Sixteen tools is slightly above the usual sweet spot, but each covers a distinct facet of running an RSS publisher: configuration, entry lifecycle, corrections/retractions, validation/audit, rebuild, batching, and assets. It is not bloated, though a few tools like find_similar_active_entries add extra surface beyond a minimal CRUD set.

    Completeness4/5

    The entry lifecycle is well covered with create, read, update, unpublish, republish, correct, retract, and batch publish, plus feed configuration, validation/audit, and rebuild. Minor gaps exist around asset management since only get_asset is exposed and binary upload is handled outside the MCP server; there is also no explicit physical delete, though retract/unpublish appear to be intentional immutable alternatives.