# Auth: Media servers

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

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

### Supported media servers

* [Auth: Plex](/crosswatch/providers/authentication/auth-media-servers/auth-plex.md)
* [Auth: Jellyfin](/crosswatch/providers/authentication/auth-media-servers/auth-jellyfin.md)
* [Auth: Emby](/crosswatch/providers/authentication/auth-media-servers/auth-emby.md)

### Optional: whitelisting (recommended)

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

Guide: [Library Whitelisting](/crosswatch/library-whitelisting.md).

### Tips

* Add [Metadata](/crosswatch/providers/metadata.md) to improve matching.
* Plex, Jellyfin, and Emby now default to strict ID matching. Better metadata reduces “missing peer” noise.
* Use [Adapter: CrossWatch](/crosswatch/providers/synchronization/adapter-crosswatch.md) for local snapshots before risky changes.
  {% endtab %}

{% tab title="Power users" %}

### Library scoping matters

Whitelisting changes what CW thinks “exists”.

That affects both matching and deletion safety.

See: [Library Whitelisting](/crosswatch/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.
{% endtab %}
{% endtabs %}


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.crosswatch.app/crosswatch/providers/authentication/auth-media-servers.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.