Skip to main content
Glama
Feedbagel MCP Server

Feedbagel MCP Server

Official
by Prototypr

feedbagel-mcp

Model Context Protocol server for the Feedbagel API. Lets agents follow RSS feeds, manage webhook subscriptions, and read entries on a user's behalf.

Install

npm install -g feedbagel-mcp

Or run via npx feedbagel-mcp without installing.

Related MCP server: mcp-rss-aggregator

Setup

  1. Mint an API key at https://feedbagel.com/dashboard/keys (pick the "Agent" scope).

  2. Add the server to your MCP client config.

Claude Desktop / Cursor / Windsurf

{
  "mcpServers": {
    "feedbagel": {
      "command": "npx",
      "args": ["-y", "feedbagel-mcp"],
      "env": {
        "FEEDBAGEL_API_KEY": "fb_..."
      }
    }
  }
}

Tools

17 tools across discovery, follows, webhooks, and entry reads.

Discovery (read)

  • search_feeds — keyword search across the catalog

  • search_feeds_by_url — find feeds at a given host

  • get_host_metadata — title, favicon, and feed list for a host

  • list_entries — recent entries, paginated

  • get_entry, get_entry_by_slug — fetch a single entry

Follows (write)

  • list_subscriptions — unified follow + webhook list

  • follow_feed, unfollow_feed

Webhooks (write)

  • list_webhooks, create_webhook, delete_webhook

  • pause_webhook, resume_webhook

  • attach_feed_to_webhook, detach_feed_from_webhook

Account (read)

  • me — account email, plan, status (use as a smoke test)

Environment

  • FEEDBAGEL_API_KEY (required)

  • FEEDBAGEL_API_BASE (optional, defaults to production)

License

MIT

Available Tools

17 tools
attach_feed_to_webhookA

[write] Attach a feed to a webhook subscription so its new entries get delivered.

Inputs: webhook_id (required), feed_id (required).

create_webhookA

[write] Create a webhook subscription. The response includes webhook_secret ONCE; the bot must persist it for HMAC validation. Counts against the subscription cap.

Inputs: webhook_url (required), subscriber_name, notes.

delete_webhookA

[write] Delete a webhook subscription and all its feed attachments.

Inputs: webhook_id (required).

detach_feed_from_webhookB

[write] Stop delivering a feed's entries to a webhook subscription.

Inputs: webhook_id (required), feed_id (required).

follow_feedA

[write] Add a feed to the user's follow list. Idempotent. Counts against the subscription cap.

Inputs: feed_id (required).

get_entryB

[read] Fetch a single entry by numeric id.

Inputs: entry_id (required).

get_entry_by_slugA

[read] Fetch a single entry by its URL slug (matches /post/ on the site).

Inputs: slug (required).

get_host_metadataB

[read] Get metadata (title, description, favicon, feed list) for a host domain.

Inputs: host (required).

list_entriesA

[read] List recent entries across all feeds, paginated. Use sort_by='published' (default) for newest first.

Inputs: page, per_page, sort_by, sort_order.

list_subscriptionsA

[read] Unified list of the user's feed follows and webhook subscriptions. Each item is tagged kind: 'follow' or 'webhook'.

Inputs: no named parameters.

list_webhooksA

[read] List all webhook subscriptions owned by the user.

Inputs: no named parameters.

meA

[read] Return the authenticated account's email, plan, and status. Use as a smoke test before other calls.

Inputs: no named parameters.

pause_webhookA

[write] Pause deliveries for a webhook subscription. Existing attachments stay; the poller skips this subscriber until resumed.

Inputs: webhook_id (required).

resume_webhookA

[write] Resume deliveries for a paused webhook subscription.

Inputs: webhook_id (required).

search_feedsA

[read] Search the feed catalog by keyword. Matches feed titles, urls, and hostnames. Returns up to 20 results with recency stats.

Inputs: query (required).

search_feeds_by_urlA

[read] Find feeds at a specific hostname or URL fragment. Use this when the user already knows the site (e.g. 'theverge.com') and wants its feeds.

Inputs: url_or_host (required).

unfollow_feedB

[write] Remove a feed from the user's follow list.

Inputs: feed_id (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 17 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers