Skip to main content
Glama
Prototypr

Feedbagel MCP Server

Official
by Prototypr
README.md
# feedbagel-mcp

Model Context Protocol server for the [Feedbagel](https://feedbagel.com) API. Lets agents follow RSS feeds, manage webhook subscriptions, and read entries on a user's behalf.

## Install

```bash
npm install -g feedbagel-mcp
```

Or run via `npx feedbagel-mcp` without installing.

## 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

```json
{
  "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

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 issues