Skip to main content
The rss MCP adapter fetches and parses RSS 2.0 and Atom feeds from public URLs. No OAuth or API keys are required for typical public feeds — pass feed URLs directly in workflow steps for news monitoring, content pipelines, and aggregation.

​
Prerequisites

  • Publicly reachable RSS or Atom feed URLs (HTTPS recommended)
  • project_contributor access in AgentRuntime
  • No API credentials required for standard public feeds

​
Connect in AgentRuntime

1

Identify feed URLs

Collect RSS or Atom URLs from blogs, YouTube channels, podcasts, or product changelogs. Most sites expose /feed, /rss, or <link rel="alternate"> in HTML.
2

Create a connection (optional)

On Connections, click New custom connection only if you want to customize user_agent or request_timeout_seconds. Many teams install the adapter with default settings and no secrets.
3

Add rss MCP instance

Go to MCP, click Add instance for rss, wire a connection on Instance config if you created one, then set the profile active.
4

Test a feed

Run mcp_call → rss_fetch_items with a known feed URL and limit: 5.
See Authentication for binding connections to MCP instances.
Feeds behind login walls or IP allowlists may fail unless you expose a public URL or proxy. This adapter does not store feed credentials.

​
What you can build

  • Morning digest — rss_fetch_items_multi on industry feeds → LLM summary → email or Slack (when available).
  • Content pipeline — New blog item → LLM rewrite → human_task → publish via LinkedIn or Google Docs connectors.
  • Competitive monitoring — Daily fetch → diff titles against Postgres history → alert on new product posts.
  • Podcast/show notes — Parse episode feeds → extract links → add to ClickUp content calendar.

​
Tools

​
Example

Fetch the five latest items from a blog feed:

​
Configuration

​
Troubleshooting