
Feed Reader
io.github.tono628developPublished by GitHub account tono628developv0.1.0Updated Oct 27, 2026
Fetch and read RSS/Atom feeds from any MCP client.
Overview
Local MCP server that fetches RSS/Atom feeds so an assistant can pull recent items from blogs, news and release feeds and build digests.
- What you can do
- Fetch a single RSS/Atom feed and return recent items with title, link, date and snippet
- Fetch several feeds at once and return one merged, date-sorted list as a digest
- When to use it
- Useful when you want an assistant to stay current with specific blogs, news sites or release-note feeds without scraping pages, and to assemble periodic digests from a set of feeds.
- Requirements
- Runs as a local stdio process installed from the npm package feed-reader-mcp (for example via npx). Needs Node.js and network access to reach the feed URLs. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open Feed Reader in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
feed-reader-mcp
An MCP server that fetches and reads RSS / Atom feeds, so any MCP client (Claude Desktop, Claude Code, etc.) can pull the latest items from blogs, news sites, and release feeds — and build digests.
Why
LLM clients can't reliably read RSS on their own. This server exposes two simple tools so an agent can stay current with the feeds you care about (release notes, news, blogs) without scraping.
Tools
Install
Use with Claude Desktop / Claude Code
Add to your MCP config (claude_desktop_config.json or .mcp.json):
Then ask: "Use feed-reader to get the latest 5 items from https://hnrss.org/frontpage" or "Build a digest from these three feeds…".
Develop
License
MIT © tono628develop
Source: README.md at commit acf63be
Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts