rss-mcp
Agent-only MCP server for RSS and Atom. A host drives it over stdio (default) or Streamable HTTP. There is no GUI, TUI, or interactive CLI. Subscriptions, cached entries, unread state, and full-text search live in one local SQLite file. Eleven tools plus two read-only resources; no prompts or MCP Apps.
Protocol: MCP 2026-07-28 (stdio or Streamable HTTP; tools + resources) via the official Python SDK v2 (mcp ≥ 2.3).
Requires Python 3.11+. Install from PyPI: uv tool install rss-mcp-server gives you the rss-mcp and rss-mcp-server commands, or run it once with uvx rss-mcp-server.
Host config
In stdio mode, the process reads JSON-RPC from stdin and writes MCP messages only to stdout. It exits when stdin closes.
Cursor mcp.json (any stdio host can use the same command):
{
"mcpServers": {
"rss-mcp": {
"command": "uvx",
"args": ["rss-mcp-server"],
"env": {
"RSS_MCP_DB": "/absolute/path/rss.db"
}
}
}
}
The PyPI distribution is rss-mcp-server (rss-mcp is blocked by a similar existing project); it installs both the rss-mcp-server and rss-mcp commands. From this checkout: uv run rss-mcp, or uvx --from /absolute/path/to/rss-mcp rss-mcp.
HTTP transport
Run the same server over Streamable HTTP instead of stdio, straight from PyPI:
uvx rss-mcp-server --transport streamable-http --host 127.0.0.1 --port 8000 --path /mcp
After uv tool install rss-mcp-server, use rss-mcp --transport streamable-http … instead; from this checkout, uv run rss-mcp --transport streamable-http ….
| Flag | Default |
|---|---|
--transport |
stdio (choices: stdio, streamable-http) |
--host |
127.0.0.1 |
--port |
8000 |
--path |
/mcp |
The MCP endpoint is then http://127.0.0.1:8000/mcp. Hosts that support remote servers can point at it directly:
{
"mcpServers": {
"rss-mcp": {
"url": "http://127.0.0.1:8000/mcp"
}
}
}
All sessions share one SQLite database (same RSS_MCP_DB setting). The endpoint serves both protocol eras: 2026-07-28 stateless per-request POSTs (with the MCP-Protocol-Version / Mcp-Method / Mcp-Name headers and _meta envelope) and the legacy initialize handshake (up to 2025-11-25, with sessions) for older hosts.
Set RSS_MCP_AUTH_TOKEN (or RSS_MCP_AUTH_TOKENS for several comma-separated tokens) to require Authorization: Bearer <token> on every MCP request (both eras; stdio is unaffected). Hosts that support custom headers:
{
"mcpServers": {
"rss-mcp": {
"url": "http://127.0.0.1:8000/mcp",
"headers": { "Authorization": "Bearer <token>" }
}
}
}
Without a token the endpoint is unauthenticated: keep the default loopback bind, or put it behind a reverse proxy with auth before exposing it beyond localhost.
The HTTP app also serves an unauthenticated GET /healthz (JSON: status, version, subscription count) for monitoring, and applies a per-client sliding-window rate limit (RSS_MCP_RATE_LIMIT_PER_MINUTE, default 120, 0 disables; keyed on bearer token or client IP, replies 429 when exceeded).
Server behavior
- Concurrent fetching:
fetch_feedwithout an id refreshes all subscriptions concurrently (RSS_MCP_FETCH_CONCURRENCY, default 8). - Failure handling: failed feeds record
last_errorand a failure count, then back off exponentially (60s doubling to 1h) in bulk fetches. AfterRSS_MCP_DISABLE_AFTER_FAILURESconsecutive failures (default 5,0never) a feed is auto-disabled and skipped until fetched by id or re-enabled viaupdate_subscription. - Scheduled refresh: set
RSS_MCP_REFRESH_INTERVAL(seconds) to refresh all feeds in the background on that interval; unset means fetch-on-demand only. - Retention: set
RSS_MCP_RETENTION_DAYSto prune entries older than that many days on each scheduled refresh (starred entries are kept). Unset keeps everything. - Per-feed overrides:
add_subscription/update_subscriptionacceptuser_agentandheadersfor feeds that block the default client.
Docker
The image runs the HTTP transport, stores the database in a /data volume, and runs as a non-root user:
docker build -t rss-mcp .
docker run -d --name rss-mcp --restart unless-stopped -p 127.0.0.1:8000:8000 \
-e RSS_MCP_AUTH_TOKEN="$(openssl rand -hex 32)" \
-v rss-mcp-data:/data rss-mcp
The container binds 0.0.0.0 internally (required for port mapping), so set RSS_MCP_AUTH_TOKEN whenever the published port is reachable beyond your machine. Publishing to 127.0.0.1 as above keeps it local. Run exactly one container per database volume.
Environment
| Variable | Default |
|---|---|
RSS_MCP_DB |
~/.local/share/rss-mcp/rss.db |
RSS_MCP_USER_AGENT |
rss-mcp/0.1 (+https://github.com/huangcheng/rss-mcp) |
RSS_MCP_AUTH_TOKEN |
unset (HTTP bearer auth disabled) |
RSS_MCP_AUTH_TOKENS |
unset (comma-separated extra tokens) |
RSS_MCP_FETCH_CONCURRENCY |
8 |
RSS_MCP_REFRESH_INTERVAL |
unset (no background refresh; seconds when set) |
RSS_MCP_DISABLE_AFTER_FAILURES |
5 (0 never auto-disable) |
RSS_MCP_RETENTION_DAYS |
unset (keep entries forever) |
RSS_MCP_RATE_LIMIT_PER_MINUTE |
120 (0 disables; HTTP only) |
list_entries and search_entries use limit 20 when omitted and clamp to 0–100. Each fetch upserts at most 50 entries and sends stored ETag / Last-Modified when the feed has them.
Tools
add_subscription— Add a feed by URL with optional tags, per-feeduser_agent/headers. Repeating a URL returns the existing subscription.update_subscription— Edit title/tags/user_agent/headers/disabled. Omitted fields are unchanged; empty string/dict/list clears;disabled=falsere-enables and resets failures.remove_subscription— Delete a subscription and its cached entries.list_subscriptions— List subscriptions with unread counts and fetch health, optionally filtered bytag.fetch_feed— Fetch one subscription, or every subscription concurrently when the id is omitted (disabled/backing-off feeds are skipped in bulk; fetching by id re-enables).list_entries— List cached entries (article bodies omitted). Limit falls back to the server default and is clamped.read_entry— Return one entry with full content and enclosures.fetch_fullreplaces content only when article text is returned.mark_readmarks it read.search_entries— Full-text search over cached title, summary, and content, bm25-ranked with a matchsnippet(bodies omitted; useread_entryfor full text).mark_entry— Mark entries read/unread byentry_ids, or a whole subscription viasubscription_id. Unknown ids are skipped.import_opml— Add each OPML feed, preserving folder names as tags. Existing URLs are skipped.export_opml— Export subscriptions as an OPML document, grouped by first tag.
Resources
rss://subscriptions— JSON: all subscriptions with unread counts and fetch health.rss://entries/unread— JSON: most recent unread entries across subscriptions (bodies omitted).
CI and releases
GitHub Actions runs the test suite on Python 3.11–3.13 (.github/workflows/ci.yml). Pushing a v* tag builds, secret-scans, and publishes to PyPI via Trusted Publishing (.github/workflows/release.yml) — no API tokens. One-time setup: on PyPI, add a pending trusted publisher for the project (owner huangcheng, repository rss-mcp, workflow release.yml, environment pypi).
Live tests
Optional network tests against a real Inoreader OPML export:
uv run pytest tests/test_real_inoreader_opml.py -v -s
They skip when /Users/huangcheng/Downloads/Cheng-Inoreader-feeds-final-20261016.opml is missing. Unit tests do not require that file.
License
MIT © 2026 HUANG Cheng
Metadata
Release files for rss-mcp-server 0.1.2
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 | Actions |
|---|---|---|---|---|
| rss_mcp_server-0.1.2.tar.gz | 108.8 kB | With provenance | Details for rss_mcp_server-0.1.2.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| rss_mcp_server-0.1.2-py3-none-any.whl | Python 3 | none | any | Details for rss_mcp_server-0.1.2-py3-none-any.whl |
Total release size: 131.6 kB
Release files / rss_mcp_server-0.1.2.tar.gz
| Download URL | rss_mcp_server-0.1.2.tar.gz |
|---|---|
| Size | 108.8 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
65c66b46987fc8c569fe3aa7ea519d9fb05d23d8cfd1581a08b20e356740264e
|
|
BLAKE2b-256 checksum How to use checksums |
6b9c2a8f79b523767b8a6844d17738cd866977900871b1d17adc53bdd304740f
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logRelease files / rss_mcp_server-0.1.2-py3-none-any.whl
| Download URL | rss_mcp_server-0.1.2-py3-none-any.whl |
|---|---|
| Size | 22.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
5f93ea1843e6cf4dd32d81580b5670fc44abe8b7e959e4856db086554c65e300
|
|
BLAKE2b-256 checksum How to use checksums |
040255092e2f480323039d9d0240b3fd92f2ecc9e9b6aca66e947f1041b07b1a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logSecurity for rss-mcp-server 0.1.2
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for rss_mcp_server-0.1.2.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 18, 2026.
Transparency logA 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.