FreshRSS MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHRSS_API_URL | Yes | URL to your FreshRSS instance (e.g., 'https://rss.example.com') | |
| FRESHRSS_PASSWORD | Yes | Your FreshRSS password | |
| FRESHRSS_USERNAME | Yes | Your FreshRSS username |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_feedsA | List all feed subscriptions |
| get_feed_groupsC | Get feed groups |
| get_unreadB | Get unread items |
| get_feed_itemsA | Get items from a specific feed |
| mark_item_readB | Mark an item as read |
| mark_item_unreadB | Mark an item as unread |
| mark_feed_readA | Mark all items in a feed as read |
| get_itemsA | Get specific items by their IDs |
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 8 tools
Each tool has a clear, distinct purpose: listing feeds, retrieving items by different criteria, and toggling read state. The three retrieval tools (get_unread, get_feed_items, get_items) are differentiated by their filters, and the mark operations are unambiguous.
Most tools follow a get_<resource> or mark_<resource>_<state> pattern, but list_feeds uses 'list' instead of 'get', and get_unread omits the noun 'items'. These minor deviations are still readable and predictable.
Eight tools is well-scoped for an RSS reader, covering the core read and mark operations without excessive granularity. Each tool earns its place in the set.
The read and mark workflows are well covered, but the server lacks feed management operations (add, update, delete feeds) and has no search capability. These gaps limit the toolset to a read-only consumer rather than a full FreshRSS manager.