rss-mcp-server

Created By
gperdrizeta year ago
RSS feed reader Model Context Protocol server.
Overview

what is rss-mcp-server?

The rss-mcp-server is a server designed to read RSS feeds using the Model Context Protocol, enabling efficient data retrieval and processing.

how to use rss-mcp-server?

To use the rss-mcp-server, set up the server by running the provided Python script (rss_server.py) and configure it to connect to your desired RSS feeds.

key features of rss-mcp-server?

  • Supports multiple RSS feed formats
  • Utilizes Model Context Protocol for enhanced data handling
  • Easy integration with Gradio for user-friendly interfaces

use cases of rss-mcp-server?

  1. Aggregating news from various RSS feeds into a single interface.
  2. Building applications that require real-time updates from RSS sources.
  3. Creating custom dashboards for monitoring specific topics via RSS feeds.

FAQ from rss-mcp-server?

  • What programming language is rss-mcp-server written in?

The server is written in Python.

  • Is there a license for using rss-mcp-server?

Yes, it is licensed under the GPL-3.0 license.

  • How can I contribute to the rss-mcp-server project?

Contributions can be made through GitHub by submitting pull requests.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gperdrizet
Star
1
Language
Python
License
GPL-3.0 license
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago