The model gets titles and metadata first and only fetches an article's full text when you ask about it — which is the difference between a feed reader that works in a chat and one that fills the context on the first question. Runtime feed management matters more than it sounds: you can add a source mid-conversation instead of editing a config and restarting. The private-IP blocking is a real consideration if you were thinking of pointing it at an internal feed.
A Go server that fetches syndication feeds you configure at launch and serves their items to an MCP client, with feeds also addable while it runs.
- all_syndication_feeds and get_syndication_feed_items — the feeds you loaded, then the items in one of them
- fetch_link — the full content of a single article, fetched only when you ask for it
- add_feed, remove_feed and list_managed_feeds — feeds changed at runtime instead of only in the config
- RSS, Atom and JSON feeds, plus an OPML file exported from Feedly, Inoreader, NewsBlur or The Old Reader
- Prompts for the recurring jobs: analyze_feed_trends, summarize_feeds, monitor_keywords, compare_sources and generate_feed_report
- Caching, rate limiting and circuit breakers, so a feed that starts failing does not stall everything else
- URL validation with private IP blocking
Nothing to authorize — no account, no key. Run the published Docker image, install through Homebrew, or install the MCP Bundle for your platform straight into Claude Desktop. Feed URLs go on the command line, or mount an OPML file and pass --opml.
One command — brew install richardwooding/tap/feed-mcp