OmniWire

OmniWire MCP Server is a production-ready news aggregation service that exposes feeds from diverse sources through the MCP (Model Context Protocol) interface. It uses a Universal Parser to automatically detect and normalize RSS, Atom, JSON, and HTML feeds, while a Sentinel Architecture with circuit breakers helps isolate failing sources to keep the overall system healthy. You can interact with the server through a set of tools and prompts designed for LLM workflows, such as fetching curated news, checking health status of sources, refreshing remote configurations, and resetting individual circuit breakers. To run it, you can either use npx for zero-setup deployments or run it via Docker for scalable production setups. The server can be fed with a remote JSON configuration (RSS_FEEDS) or a local defaults file, enabling hot-reloadable feeds without code changes. The included Tools and Prompts are designed to be easy to call from an automation layer or an LLM-assisted workflow, providing a streamlined path from source feeds to normalized NewsItem data.

Prerequisites:

• Node.js and npm (for npx-based usage) or Docker (for containerized deployment)
• Internet access to install or pull images

Option A: Quick start with npx (no local install)

1. Ensure Node.js and npm are installed
2. Run the MCP server via npx (uses the package you publish): npm install -g npm # if you need to refresh npm npx -y @furkankoykiran/omniwire-mcp

Option B: Docker deployment

1. Build the image locally (if a Dockerfile is provided by the project): docker build -t omniwire-mcp .
2. Run the container with default feeds configured via environment variable: docker run -e RSS_FEEDS="https://raw.githubusercontent.com/furkankoykiran/OmniWire-MCP/refs/heads/main/src/config/defaults/feeds.json" omniwire-mcp

Option C: Local development (clone and run from source)

1. Clone the repository: git clone https://github.com/furkankoykiran/OmniWire-MCP.git cd OmniWire-MCP
2. Install dependencies and build: npm install npm run build
3. Start the server: npm start

Prerequisites recap:

• Node.js and npm for npx usage or Docker for containerized runs
• Access to the feeds.json configuration (remote URL or embedded defaults)
• Optional: Docker installed if you prefer containerized deployment

Tips and common considerations:

• The RSS_FEEDS env var points to a JSON configuration that defines sources. You can host this remotely or use the defaults shipped with the repo.
• LOG_LEVEL can be adjusted (e.g., debug, info, warn, error) to control verbosity.
• When using Docker, ensure that the RSS_FEEDS URL is accessible from the container network.
• The MCP configuration schema supports hot-reloadable sources; you can update RSS_FEEDS to refresh the live feed configuration without redeploying.
• If you encounter parsing issues, ensure the feed URL is accessible and that the feed type is supported by the universal parser (RSS, Atom, JSON, HTML). The Sentinel service will step in to prevent cascading failures from malfunctioning sources.
• For clean exits or resets of circuit breakers, use the provided tools like fetch-news (with sourceId), check-health, or reset-source.