# Travel Feeds [Health: Active]

**Category:** 🚆 Travel & Transportation  
**Repository:** https://github.com/pipeworx-io/mcp-travel-feeds  
**GitHub Stars:** 0  
**npm Downloads (last month):** 491  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/travel-feeds

## Description
Travel Feeds MCP.

## Tools
Capabilities this server exposes over MCP:

- **list_feeds** — List the curated travel feeds (id, title, category, source). Optionally filter by category (travel) or keyword. Pass an id to read_feed.
- **read_feed** — Read a curated travel feed by its id (from list_feeds). Returns normalized items (title, link, published, summary). Optionally filter items by keyword.
- **fetch_feed** — Fetch and normalize any RSS / Atom / RDF feed by URL. CF-robust: fetches directly and falls back to a proxy if the source blocks the gateway. Use list_feeds first for curated sources.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "travel-feeds": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-travel-feeds"]
  }
}
```

## Documentation

## What Travel Feeds MCP server does

The Travel Feeds MCP server gives an MCP-compatible agent access to travel-related feed data. It supports two ways to find content: browse a curated catalog, or provide a feed URL directly. Returned entries are normalized so consuming applications can work with consistent fields instead of handling each feed format separately.

The curated catalog includes feed IDs, titles, categories, and source URLs. Agents can filter that catalog by the travel category or by a keyword. After selecting a feed ID, they can retrieve its items and optionally filter those items by keyword.

## How it works

The server exposes three tools:

- `list_feeds` returns available curated feeds and accepts optional category or keyword filters.
- `read_feed` reads a curated feed selected by its ID and returns normalized items containing a title, link, publication date, and summary. A keyword filter is available for the items.
- `fetch_feed` accepts a URL and fetches an RSS, Atom, or RDF feed, then converts its entries into the normalized format.

For direct retrieval, the Travel Feeds MCP server first attempts to fetch the source and can use a proxy fallback if the source blocks the gateway. The documented workflow is to use `list_feeds` for curated sources, then pass a selected ID to `read_feed`.

## Setup and configuration

A hosted MCP connection is available at `https://gateway.pipeworx.io/travel-feeds/mcp`. The README provides configuration examples for Claude Desktop, Cursor, and Windsurf. The same gateway also has a full endpoint at `https://gateway.pipeworx.io/mcp`; the scoped endpoint lists this pack's tools directly, while both endpoints can reach the broader gateway through its shared routing tools.

The package can also run locally without a Pipeworx account or gateway round trip. Configure an MCP client to run `npx -y @pipeworx/mcp-travel-feeds`, or execute that command directly. The local process communicates over stdin and stdout and exposes only the travel-feed tools.

No environment variables are documented as required. The hosted HTTP tool API can also be called without an MCP client using POST requests to the gateway's tool endpoint.

## Tools and capabilities

Use `list_feeds` when the agent needs to discover available curated sources before reading one. Use `read_feed` when the source is already identified by a catalog ID and the result should be limited to matching items. Use `fetch_feed` for a feed URL that is not part of the curated catalog or when an application needs to process its own RSS, Atom, or RDF source.

Each normalized item includes `title`, `link`, `published`, and `summary`. This makes the output suitable for tasks such as finding recent travel articles, filtering feed entries by a subject keyword, or presenting several sources in a common structure.

## Limitations and notes

The Travel Feeds MCP server is focused on feed discovery and retrieval.

A scoped hosted connection includes shared Pipeworx meta-tools in addition to the three pack tools, so its `tools/list` response contains more tools than the local package. The exact hosted scope can change and is stated by the connection's `initialize` response. The local stdio mode does not include those shared meta-tools or cross-catalog routing.

_Full upstream README: https://allmcps.com/mcp/travel-feeds/readme_