@missionsquad/mcp-rss
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_rss_feedB | Fetches and parses an RSS feed, returning structured data with feed info and items |
| fetch_multiple_feedsA | Batch fetch multiple RSS feeds with success/error status for each |
| monitor_feed_updatesC | Check for new items in a feed since a specific time or last check |
| search_feed_itemsC | Search for content across one or more RSS feeds |
| extract_feed_contentC | Extract and format feed content for different use cases |
| get_feed_headlinesC | Gets a list of headlines from a feed, including title, summary, and URL. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OPML Export |
TDQS
Scored across 6 tools
Most tools have distinct purposes, but there is some overlap between 'fetch_rss_feed' and 'extract_feed_content' or 'get_feed_headlines', which could cause confusion. However, descriptions help clarify that 'fetch_rss_feed' provides full structured data, while others focus on specific aspects like headlines or formatted content.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'fetch_rss_feed', 'monitor_feed_updates', and 'search_feed_items'. This predictability makes it easy for agents to understand and use the tool set without naming confusion.
With 6 tools, the server is well-scoped for RSS feed management, covering core operations like fetching, monitoring, searching, and extracting content. Each tool serves a clear purpose without being overly sparse or bloated, fitting typical use cases effectively.
The tool set covers most essential RSS operations, including fetching, monitoring, searching, and extracting content. A minor gap is the lack of subscription management or feed modification tools, but agents can still handle common workflows like reading and tracking feeds without significant issues.