Feedbagel MCP Server
OfficialRelated Servers
Alternatives to Feedbagel MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that allows interaction with RSS feeds, enabling users to import subscriptions via OPML files, fetch and update articles automatically, and filter content by source and status.7 npmMIT
- AlicenseAqualityAmaintenanceModel Context Protocol Server for aggregating RSS feeds in Claude Desktop327Mozilla Public 2.0
- AlicenseCqualityDmaintenanceAn extensible Model Context Protocol server that provides standardized access to social platform data (currently Farcaster) and onchain data for LLMs.1013MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation built with FastAPI that enables AI agent interactions. Provides a structured foundation for building AI-powered applications with proper data validation and modern Python tooling.-
- AlicenseAqualityDmaintenanceA Model Context Protocol server that exposes Firebase Firestore and Authentication to AI agents, supporting multi-project configurations and read operations.5166 npmMIT
- AlicenseAqualityDmaintenanceA Model Context Protocol server for reading public Reddit data and posting authenticated replies, enabling AI agents to interact with Reddit content.6MIT
TDQS
Scored across 17 tools
Each tool targets a distinct action or resource (e.g., feed follow/unfollow, webhook CRUD, entry retrieval, search variants). The two search tools are differentiated by search method (keyword vs URL), and webhook state management tools (pause/resume) are clearly separate from creation/deletion.
All tool names follow a consistent verb_noun pattern (e.g., follow_feed, create_webhook, get_entry), with some longer phrases like attach_feed_to_webhook that remain predictable. No mixing of camelCase or inconsistent verb styles.
With 17 tools, the set is slightly above the typical 3-15 range but still well-scoped for a feed/webhook management server. Each tool serves a clear purpose, and none feel superfluous.
Core workflows are covered: feed following/unfollowing, webhook creation/deletion/pause/resume, entry retrieval, and search. Minor gaps exist (e.g., no webhook update, no feed creation), but they do not severely hinder typical use cases.