rss-mcp
Server 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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| fetch_feedA | Fetch and parse an RSS or Atom feed. Returns feed metadata (title, subtitle, language) and a list of entries (title, link, published date, author, summary, tags). Use |
| search_entriesA | Fetch a feed and return only entries whose title or summary contain a keyword (case-insensitive). Useful when you want the AI to check a feed for specific topics without wading through everything. |
| list_feed_metadataA | Fetch metadata for one or more feeds without loading all entries — title, subtitle, entry count, last update time. Useful for building a dashboard of feeds you follow. |
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 3 tools
The three tools have distinct primary outputs—full feed entries, filtered search results, and metadata-only—so agents can usually tell them apart. There is minor overlap because fetch_feed also returns metadata, but the descriptions are clear enough to prevent confusion.
All tools follow a consistent verb_noun snake_case pattern: fetch_feed, search_entries, list_feed_metadata. The verbs accurately reflect each tool's behavior.
Three tools is well-scoped for a read-only RSS/Atom utility. Each tool covers a distinct need: full retrieval, keyword search, and lightweight metadata lookup.
For the domain of public feed retrieval, the surface is complete: fetching entries, searching by keyword, and listing metadata are all covered. There are no obvious dead ends or missing core operations.