mcp-morning-brief
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_feedsA | List all subscribed RSS/Atom feeds. |
| add_feedA | Subscribe to a new RSS or Atom feed URL. Validates by attempting to fetch and parse it. |
| remove_feedA | Unsubscribe from a feed by URL or label. |
| fetch_feedB | Fetch a single RSS/Atom feed (does not need to be subscribed). Returns parsed items. |
| get_briefA | Generate a deduped digest of recent items across all subscribed feeds, grouped by feed. |
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 5 tools
Each tool has a clearly distinct purpose: adding a feed, fetching any feed, generating a brief, listing feeds, and removing a feed. No overlap in functionality.
All tool names follow a consistent verb_noun pattern in snake_case (add_feed, fetch_feed, get_brief, list_feeds, remove_feed), making them predictable.
With 5 tools, the server covers the core operations for managing RSS/Atom feeds and generating a brief. This is well-scoped and neither too few nor too many.
The set covers full lifecycle: subscribe (add_feed), list (list_feeds), fetch individual (fetch_feed), generate digest (get_brief), and unsubscribe (remove_feed). No obvious gaps for its stated purpose.