> For the complete documentation index, see [llms.txt](https://wiki.crosswatch.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers.md).

# Media servers

Supported media servers (Plex, Jellyfin, Emby) and setup notes for authentication, whitelisting, and matching.

Media servers are where your library and plays live. CrossWatch (CW) typically treats your media server as the source of truth.

{% hint style="success" %}
Start here if your library lives in Plex, Jellyfin, or Emby.
{% endhint %}

{% tabs %}
{% tab title="End users" %}
{% hint style="info" %}
Connect a media server in **Settings → Connections** before creating pairs.
{% endhint %}

### Supported media servers

<table data-view="cards"><thead><tr><th>Server</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td><strong>Plex</strong><br>Best external ID coverage and broad sync support.</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/plex.md">Plex</a></td></tr><tr><td><strong>Jellyfin</strong><br>Self-hosted server with strong local control.</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/jellyfin.md">Jellyfin</a></td></tr><tr><td><strong>Emby</strong><br>Media server with similar pair and scrobble support.</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/emby.md">Emby</a></td></tr><tr><td><strong>Silo</strong><br>Experimental household-aware server with watchlist, history, ratings, progress, collections, and scrobbling.</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/silo.md">Silo</a></td></tr><tr><td><strong>Tofa</strong><br>Experimental household-aware server with watchlist, history, progress, read-only library Collection, and scrobbling.</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers/tofa.md">Tofa</a></td></tr></tbody></table>

### Optional: whitelisting (recommended)

Whitelisting limits CW to specific libraries. It reduces noise, speeds up runs, and avoids syncing junk.

Guide: [Library Whitelisting](https://wiki.crosswatch.app/crosswatch/settings/connections/library-whitelisting.md).

#### Use whitelisting when

* you only want TV or anime
* the server has shared junk libraries
* you want faster dry runs

#### Skip it when

* the whole server is clean
* you want every library included
* you are still testing provider auth
  {% endtab %}

{% tab title="Power users" %}

### Library scoping matters

Whitelisting changes what CW thinks “exists”.

That affects both matching and deletion safety.

See: [Library Whitelisting](https://wiki.crosswatch.app/crosswatch/settings/connections/library-whitelisting.md).

### Matching note

Plex is usually strongest on external IDs.

Strict ID matching is now the default for Plex, Jellyfin, and Emby.

Emby/Jellyfin often need better metadata agents to reduce missing peers.

{% hint style="warning" %}
If matching quality is weak, fix metadata before enabling destructive writes.
{% endhint %}
{% endtab %}
{% endtabs %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
