# RSS Feed Parser MCP

> The RSS Feed Parser takes raw XML or Atom feed data from any blog, news site, or podcast and converts it into clean, structured JSON objects. It extracts all critical metadata—titles, links, publication dates, authors, categories, and full content snippets—without needing to scrape messy HTML. This lets your agent process reliable, machine-readable content feeds instantly.

## Overview
- **Category:** productivity
- **Price:** Free
- **Tags:** rss, atom, content-aggregation, web-scraping, json-parsing, news-monitoring

## Description

Content teams spend way too much time manually copying article data from multiple sources. You're supposed to monitor twenty competitor blogs and five industry news sites, but you end up staring at fragmented HTML that breaks every other day.

This MCP changes that. It reads native web feeds—the XML or Atom format—and turns the entire stream into clean JSON objects. This means your agent gets predictable data: titles, links, publication dates, authors, and full content snippets, all packaged neatly for summarization or automated distribution. You don't have to worry about messy DOM traversal; this tool handles the tough parsing work so you can focus on what matters.

Whether it’s an entire blog feed or a podcast channel with enclosures, the data is structured and ready to go. Accessing reliable content feeds like this used to require custom scrapers for every single site. Now, through Vinkius, your agent gets access to one unified parser that handles both RSS 2.0 and Atom formats identically.

## Tools

### parse_rss_feed
Converts raw RSS 2.0 or Atom XML strings into structured JSON, extracting titles, links, dates, categories, and full content snippets.

## Prompt Examples

**Prompt:** 
```
Monitor TechCrunch's RSS feed and give me the latest 5 articles with titles and publish dates.
```

**Response:** 
```
5 articles extracted: title, link, pubDate, author, and content snippet for each.
```

**Prompt:** 
```
Parse our company blog feed and extract all articles tagged 'product-update' from the last 30 days.
```

**Response:** 
```
8 articles found with 'product-update' category in the last 30 days.
```

**Prompt:** 
```
Get the latest episode URLs from this podcast RSS feed for our newsletter.
```

**Response:** 
```
3 episodes with audio URLs, durations, and descriptions extracted.
```

## Capabilities

### Extract structured article data
Pass a raw XML feed string and receive a clean JSON array containing titles, links, dates, and content for multiple items.

### Handle multiple feed standards
Processes both RSS 2.0 and Atom formats using the same unified structure.

### Extract podcast metadata
Identifies audio or video enclosures within a feed, providing URLs, durations, and file sizes.

## Use Cases

### Monitoring Competitor News
A content strategist wants to track five competitors' latest posts. They use the MCP to feed the raw XML for each site, allowing their agent to consolidate titles and publication dates into a single JSON list for weekly reporting.

### Building a Podcast Content Index
A marketing team needs all recent episode details (URL, duration, description) from a podcast. The MCP ingests the feed and gives them an array of clean objects containing the necessary enclosure data for their newsletter.

### Curating Industry News Briefs
A researcher needs to summarize key takeaways from three industry news aggregators. They run the `parse_rss_feed` tool on all three feeds, receiving a consistent JSON output that can be fed into a summarization model.

### Validating Content Source Integrity
A product team needs to ensure an external data partner's feed is reliable. They use the MCP to test various raw XML strings, verifying that all expected metadata fields—like author and category—are consistently present.

## Benefits

- Stop dealing with inconsistent HTML. This MCP reads native feed XML/Atom and delivers structured JSON, so your agent never has to worry about broken tags or malformed code.
- Process entire content streams, not just single articles. You can pass a raw feed string and get up to twenty items returned in one clean batch of data.
- Capture rich podcast details automatically. The tool extracts enclosure URLs, durations, and file sizes from episode feeds, which is critical for media monitoring.
- Centralize multiple formats. It treats RSS 2.0 and Atom feeds the same way, unifying disparate content sources into a single, predictable JSON structure.
- Eliminate manual data entry. Instead of copying titles, links, and dates across dozens of tabs, your agent gets all that metadata in one go.

## How It Works

The bottom line is that you trade unpredictable website code for predictable, standardized data objects.

1. You supply the raw XML string from the RSS or Atom feed.
2. The MCP processes this stream, extracting all metadata (titles, links, dates, content) into a structured JSON format.
3. Your agent receives the clean JSON object, which is ready for immediate use in workflows like summarization or data storage.

## Frequently Asked Questions

**How do I use the RSS Feed Parser with podcast feeds?**
The MCP handles podcast data by extracting enclosure metadata. You simply pass the feed XML; it returns a structured JSON object that includes URLs, durations, and descriptions for every episode.

**Does the RSS Feed Parser support Atom feeds or only RSS 2.0?**
No, the MCP is built to handle both. It parses both RSS 2.0 and Atom formats identically, unifying them into one consistent JSON structure for your agent.

**What kind of data does parse_rss_feed extract?**
It extracts comprehensive metadata including the title, full link, publication date, author, categories, content snippet, and even podcast enclosure details into a single structured JSON object.

**Can I use the RSS Feed Parser for news sites that require logins?**
No. This MCP requires access to the public feed XML/Atom URL. If the site content is paywalled or behind a login, you won't be able to parse it.

**Is this better than simple web scraping?**
Yes. Traditional scraping parses messy HTML; this MCP understands standardized feed XML and delivers clean JSON directly. It’s reliable because the input format is controlled by the web standard, not the site's design.