# Watchmode [Health: Active]

**Category:** 🔗 Aggregators  
**Repository:** https://github.com/pipeworx-io/mcp-watchmode  
**GitHub Stars:** 0  
**npm Downloads (last month):** 606  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/watchmode

## Description
Streaming availability across 200+ services: titles, sources, releases.

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

```json
"mcpServers": {
  "watchmode": {
    "command": "npx",
    "args": ["-y","@pipeworx/mcp-watchmode"],
    "env": {
      "PLATFORM_WATCHMODE_KEY": ""
    }
  }
}
```

**Requires environment variables:** `PLATFORM_WATCHMODE_KEY` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What Watchmode MCP server does

The Watchmode MCP server exposes Watchmode’s streaming and title data to MCP-compatible clients. It covers more than 200 streaming services and can help an agent find titles, inspect metadata, identify viewing sources, and query release information.

The integration is useful for applications that need availability by region, such as recommendation assistants, watchlist tools, content research workflows, or agents answering questions about where a title can be watched. It also exposes reference data for sources, networks, genres, regions, and languages.

## How it works

The server uses the Watchmode API at `https://api.watchmode.com/v1`. It supports two connection patterns:

- A local stdio process started with the `@pipeworx/mcp-watchmode` npm package.
- A hosted MCP endpoint at `https://gateway.pipeworx.io/watchmode/mcp`.

The hosted endpoint lists the Watchmode tools together with shared Pipeworx gateway tools. Those shared tools include routing and discovery functions such as `ask_pipeworx`; the exact tool list is returned by the connection’s `initialize` response. The local process exposes only the Watchmode tool set.

The same gateway also provides a general endpoint at `https://gateway.pipeworx.io/mcp`. In either hosted configuration, HTTP clients can call tools directly through paths such as `/v1/tools/title_search`.

## Setup and configuration

For a local MCP configuration, run the package with `npx`:

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

The Watchmode MCP server can also be added by URL:

```json
{
  "mcpServers": {
    "watchmode": {
      "url": "https://gateway.pipeworx.io/watchmode/mcp"
    }
  }
}
```

Gateway authentication uses `PLATFORM_WATCHMODE_KEY`. The API can also receive a customer-supplied key through the `_apiKey` query parameter. Local stdio operation does not require a Pipeworx account.

## Tools and capabilities

The Watchmode MCP server provides these operations:

- `title_search` searches titles, with optional search fields and title types.
- `title_detail` retrieves title information and can append related data such as cast or sources.
- `title_sources` finds streaming sources for a title, optionally filtered by region.
- `title_seasons` returns seasons for a series.
- `releases` filters recent or upcoming releases by dates, regions, sources, types, and pricing-related region settings.
- `list_titles` queries the catalog using filters such as genres, networks, regions, source types, release dates, sorting, pagination, and limits.
- `sources`, `networks`, `genres`, `regions`, and `languages` return Watchmode reference lists.

The gateway’s `ask_pipeworx` tool can accept a natural-language question and select a suitable tool and arguments. Direct HTTP callers can inspect a tool with a GET request and invoke it with a POST request.

## Limitations and notes

This is an independent, unofficial Watchmode integration and is not affiliated with or endorsed by Watchmode. Watchmode’s free tier is listed as allowing 1,000 requests per month.

The hosted pack endpoint includes shared Pipeworx tools in addition to the Watchmode tools, so its reported tool count is larger than the local package’s list. The local server does not provide Pipeworx-wide routing through `ask_pipeworx`. Regional availability and source results depend on the data returned by Watchmode and the regions supplied to the relevant tool.

_Full upstream README: https://allmcps.com/mcp/watchmode/readme_