rss-reader-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | When TRANSPORT=httpStream, the listening port. | 8081 |
| TRANSPORT | No | Select the transport mode, either stdio (default) or httpStream. | stdio |
| MCP_SERVER_HOST | No | When TRANSPORT=httpStream, the listening address. | localhost |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
| completions | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_feed_entriesC | Fetch RSS feed entries from a given URL |
| fetch_article_contentA | Fetch and extract article content from a URL, formatted as Markdown |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one fetches a list of feed entries, the other fetches the full content of a single article. There is no overlap.
Both tools use a consistent verb_noun pattern with 'fetch_' prefix, making them predictable and easy to understand.
With only two tools, the server feels very thin for an 'rss-reader' purpose. A typical reader would include tools for managing feeds, subscriptions, or browsing, making this count too low.
The tool set is severely incomplete. There are no tools for feed management (e.g., add, list, remove feeds), no search or filter capabilities, and no persistence. The server cannot function as a full RSS reader.