MCP RSS Feed Server
This project is a server implementation that detects and parses RSS/Atom feeds using the Model Context Protocol (MCP).
Available Tools
feed
Detects and parses RSS/Atom feeds from a given URL.
url(string, required): Target URL to analyze for feedslimit(integer, optional): Maximum number of entries to return (default: 10, max: 100)
Returns: JSON containing:
feed_info: Feed metadata (title, description, language, etc.)entries: Array of feed entries with title, link, published date, description, author, and GUIDmetadata: Response metadata including feed URL, entry counts, and status
Features
- Automatic Feed Detection: Discovers RSS/Atom feeds from websites automatically
- Multiple Feed Format Support: Handles RSS 2.0, RSS 1.0, Atom 1.0, and other formats
- Intelligent Parsing: Extracts clean, structured data from feeds
- HTML Cleanup: Removes HTML tags from descriptions for clean text output
- Fallback Mechanisms: Tries common feed paths when direct detection fails
- Error Handling: Robust error handling with detailed logging
Installation
Using uv (recommended)
No special installation is needed when using uv. You can run mcp-server-rss directly with uvx.
Using PIP
Alternatively, you can install mcp-server-rss using pip:
pip install mcp-server-rss
After installation, you can run it as a script like this:
mcp-server-rss
Configuration
Configure for Claude.app
Add to your Claude settings:
Using uvx
{
"mcpServers": {
"rss": {
"command": "uvx",
"args": ["mcp-server-rss"]
}
}
}
Using pip installation
{
"mcpServers": {
"rss": {
"command": "mcp-server-rss"
}
}
}
Configure for VS Code
For quick installation, use one of the one-click install buttons below...
Command Line Options
You can specify the following options when running the server:
You can specify the following options when running the server:
--sse: Enable Server-Sent Events transport (on/off)--host: Server bind address (default: localhost)--port: Server port number (default: 8000)--log-level: Logging verbosity (debug, info, warning, error)
License
MIT License - see LICENSE file for details.
Metadata
Release files for mcp-server-rss 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| mcp_server_rss-0.1.0.tar.gz | 43.3 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_server_rss-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 52.7 kB
Release files / mcp_server_rss-0.1.0.tar.gz
| Download URL | mcp_server_rss-0.1.0.tar.gz |
|---|---|
| Size | 43.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
46840ede47188bed8e55a8a362d1588184fdf2c77c45a05592e4950e94363ff0
|
|
BLAKE2b-256 checksum How to use checksums |
6d37100d6e6b910fcc192d6ed520d9a46b0a4c27a0920267784e89d1f351ed9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Release files / mcp_server_rss-0.1.0-py3-none-any.whl
| Download URL | mcp_server_rss-0.1.0-py3-none-any.whl |
|---|---|
| Size | 9.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
b7bcd77e8cb903505e584bf7dc6c18cb9a8f840c6487c8d0836fd8657e9b405e
|
|
BLAKE2b-256 checksum How to use checksums |
0ba8c47c974a1d7572f844f9c0ddccf7489867a67427d7750cb3215d3c4d363f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
python-httpx/0.28.1
|
Security for mcp-server-rss 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.