How do I use OmniWire-MCP?

1. Click on "Install Server". 2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state. 3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@OmniWire-MCP fetch latest tech news from all sources" That's it! The server will respond to your query, and you can continue using it as needed. Here is a step-by-step guide with screenshots.

OmniWire-MCP

by furkankoykiran

Overview Schema Source Related Servers Score Discussions Admin

TypeScript

Remote

OmniWire MCP Server ⚡️

Release License MCP

OmniWire-MCP is a production-ready, fault-tolerant news aggregation server built on the Model Context Protocol (MCP). It bridges the gap between AI models and real-time information by providing a unified interface for consuming RSS, Atom, JSON, and HTML feeds.

Designed for resilience, it features a Sentinel Service with Circuit Breakers to handle failing sources gracefully and a Universal Parser that automatically adapts to different content formats.

✨ Features

Universal Parsing: Automatically detects and parses RSS, Atom, JSON, and HTML content.
Sentinel Architecture: Intelligent Circuit Breakers monitor source health, preventing cascading failures.
Dynamic Configuration: Hot-reload sources via remote JSON config (RSS_FEEDS) or fallback to local defaults.
Data Normalization: Transforms diverse feed formats into a standardized NewsItem schema.
AI-Native: Exposes specialized Tools and Prompts optimized for LLM consumption.
Zero-Config Deployment: Runs instantly via npx or Docker.

Related MCP server: rss-news

🚀 Quick Start

Using `npx` (Global)

Prerequisite: The package must be published to NPM or installed globally.

npx omniwire-mcp

Local Testing (Without Publishing)

If you are developing locally and want to test the npx command:

Link the package globally:
```
cd OmniWire-MCP
npm link
```
Run with npx:
```
npx omniwire-mcp
```

Custom Configuration

You can configure the server in two ways:

Remote URL: Provide a URL to a JSON configuration file.

RSS_FEEDS="https://raw.githubusercontent.com/furkankoykiran/OmniWire-MCP/refs/heads/main/src/config/defaults/feeds.json" npx omniwire-mcp

Direct JSON: Pass the configuration JSON directly as a string.
```
RSS_FEEDS='{"sources": [...]}' npx omniwire-mcp
```

📦 Installation & Publishing

Publish to NPM (Recommended)

To make npx omniwire-mcp available to everyone:

Login to NPM:
```
npm login
```
Publish the package:
```
npm publish --access public
```

Option 1: Docker (Cloud/Production)

The server is Docker-ready for easy deployment.

# Build the image
docker build -t omniwire-mcp .

# Run with custom config
docker run -e RSS_FEEDS="https://raw.githubusercontent.com/furkankoykiran/OmniWire-MCP/refs/heads/main/src/config/defaults/feeds.json" omniwire-mcp

Option 2: Local Development

Clone the repository:

git clone https://github.com/furkankoykiran/OmniWire-MCP.git
cd OmniWire-MCP

Install dependencies and build:
```
npm install
npm run build
```
Run the server:
```
npm start
```

🔌 MCP Configuration

Add OmniWire to your MCP client configuration (e.g., claude_desktop_config.json or mcp_config.json).

Standard Configuration (`npx`)

{
  "mcpServers": {
    "omniwire": {
      "command": "npx",
      "args": [
        "-y",
        "@furkankoykiran/omniwire-mcp"
      ],
      "env": {
        "RSS_FEEDS": "https://raw.githubusercontent.com/furkankoykiran/OmniWire-MCP/refs/heads/main/src/config/defaults/feeds.json",
        "LOG_LEVEL": "info"
      }
    }
  }
}

Docker Configuration

{
  "mcpServers": {
    "omniwire": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e", "RSS_FEEDS",
        "omniwire-mcp"
      ],
      "env": {
        "RSS_FEEDS": "https://raw.githubusercontent.com/furkankoykiran/OmniWire-MCP/refs/heads/main/src/config/defaults/feeds.json"
      }
    }
  }
}

🛠 Capabilities

Tools

Tool	Description	Arguments
`fetch-news`	Smat fetcher with Sentinel protection	`filter` (string), `sourceId` (string), `limit` (number)
`check-health`	Diagnostic report for sources	`sourceId` (optional)
`refresh-config`	Force reload of remote config	None
`reset-source`	Manually reset a circuit breaker	`sourceId` (string)

Resources

URI	Description
`news://all`	Aggregated feed from all healthy sources
`news://source/{id}`	Live feed from a specific source
`health://sources`	Real-time system health report
`config://current`	View active configuration

Prompts

Prompt	Application
`summarize-news`	"Give me a digest of topic X" (Uses `fetch-news`)
`analyze-sources`	"Diagnose my feed health" (Uses `check-health`)

⚙️ Configuration Schema

The configuration JSON file should match the following schema:

{
  "sources": [
    {
      "id": "tech-crunch",
      "name": "TechCrunch",
      "url": "https://techcrunch.com/feed/",
      "type": "rss",
      "enabled": true
    }
  ],
  "configPollIntervalMs": 60000,
  "requestTimeoutMs": 10000,
  "sentinel": {
    "failureThreshold": 3,
    "recoveryTimeoutMs": 60000
  }
}

🤝 Contributing

We welcome contributions! Please see our Contributing Guide for details on how to set up your development environment and submit Pull Requests.

📄 License

This project is licensed under the MIT License.

Available Tools

4 tools

check-healthD

ParametersJSON Schema

Name	Required	Description	Default
`sourceId`	No	Specific source to check, or all if omitted

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

fetch-newsD

ParametersJSON Schema

Name	Required	Description
`limit`	No	Max items to return
`filter`	No	Keyword to filter titles/descriptions by
`sourceId`	No	Specific source ID to fetch from

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

refresh-configD

ParametersJSON Schema

Name	Required	Description	Default
No parameters

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

reset-sourceD

ParametersJSON Schema

Name	Required	Description	Default
`sourceId`	Yes	Source ID to reset

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

4 tool updatesv1.0.6Jul 30, 2026
- First observedcheck-health
- First observedfetch-news
- First observedrefresh-config
- First observedreset-source

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2/5.0

Disambiguation4/5

Tool names suggest distinct actions: fetch-news, check-health, refresh-config, and reset-source. Some potential overlap between refresh-config and reset-source, but overall they appear to target different resources. Without descriptions, ambiguity is low but not zero.

Naming Consistency5/5

All tools use a consistent lowercase hyphenated verb_noun pattern (fetch-news, check-health, refresh-config, reset-source). No mixing of conventions or case styles.

Tool Count5/5

Four tools is a reasonable and focused set for a server. It is neither too sparse nor too large, fitting a typical small-to-medium integration.

Completeness3/5

Only four tools are exposed, covering news fetching, health check, config refresh, and source reset. Missing obvious operations like managing news items (create, update, delete) or configuration viewing, which may limit agent capabilities.

Maintenance

ActivityInactive

ResponsivenessUnresponsive

Resources

Need Help?

Related Servers

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

SteadyFetch A
io.github.carsonroell-debug
Reliable web fetching for AI agents with retry, circuit breaker, caching, and anti-bot bypass
Browser Automation Web Scraping Agent Orchestration
52
RSS and news feeds for agents A
io.github.ux-xd
RSS, Atom and JSON feeds for agents: find a site's feed, read items as JSON, keyless news search.
Browser Automation Search Web Scraping
31
FeedNestOAuth
io.github.LucaIaconelli
Your curated sources (RSS, YouTube, podcasts, Google News) as context for any AI agent. 26 tools.
Search RAG Systems
11
Hypeline
io.hypeline
Give an AI agent eyes on the web: turn any feed, page, or stream into deduplicated change events.
Browser Automation Web Scraping
2

Related MCP Servers

News Aggregator MCP Server
Search Entertainment & Media
AiAgentKarl
A
license
A
quality
D
maintenance
Enables AI agents to fetch and search news from multiple sources including RSS/Atom feeds, HackerNews, and GDELT global news intelligence without requiring an API key.
Updated 5 months ago (2026-04-03 16:05 UTC)
11
4
MIT
rss-news
Search Text Summarization Note Taking
max1ab
A
license
A
quality
C
maintenance
Enables AI to manage RSS subscriptions, fetch and summarize news, and organize results into tools like Notion.
Updated 5 months ago (2026-04-17 04:48 UTC)
9
14
3
MIT
MyNews MCP Server
Search RAG Systems
iamvazghen
A
license
Not graded
quality
C
maintenance
Enables AI agents to fetch categorized news headlines and full article text from a multi-topic RSS aggregator, with no API keys required.
Updated 3 months ago (2026-06-23 23:01 UTC)
5
ISC
world-news-feeds
Search Entertainment & Media
pipeworx-io
A
license
Not graded
quality
C
maintenance
Provides curated international news feeds with tools to list, read, and fetch RSS/Atom/RDF feeds. Enables AI agents to access and filter world news data through natural language.
Updated 13 days ago (2026-08-26 17:50 UTC)
9
MIT

Appeared in Searches

Aggregated RSS Feed Curation and Quality Control Tools

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/furkankoykiran/OmniWire-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server

OmniWire MCP Server ⚡️

✨ Features

🚀 Quick Start

Using npx (Global)

Local Testing (Without Publishing)

Custom Configuration

📦 Installation & Publishing

Publish to NPM (Recommended)

Option 1: Docker (Cloud/Production)

Option 2: Local Development

🔌 MCP Configuration

Standard Configuration (npx)

Docker Configuration

🛠 Capabilities

Tools

Resources

Prompts

⚙️ Configuration Schema

🤝 Contributing

📄 License

Available Tools

Tool Schema Changelog

Maintenance

Resources

Looking for Admin?

Related MCP Connectors

Related MCP Servers

Appeared in Searches

Latest Blog Posts

MCP directory API

Using `npx` (Global)

Standard Configuration (`npx`)