> 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.md).

# Connections

Connect services  media servers, trackers, helpers and metadata

Providers are the services CW talks to.

Connect providers in **Settings → Connections**.

Then combine providers that support synchronization in pairs. [Movie Paradise](https://wiki.crosswatch.app/crosswatch/settings/connections/trackers/movieparadise.md) is currently hidden from Connections until sync support is ready. It cannot be used in sync pairs or scrobble routes.

{% hint style="success" %}
Best first setup: one media server and one tracker.
{% endhint %}

### Browse provider docs

<table data-view="cards"><thead><tr><th>Section</th><th data-card-target data-type="content-ref">Open</th></tr></thead><tbody><tr><td>Media servers</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-servers.md">Media servers</a></td></tr><tr><td>Trackers</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/trackers.md">Trackers</a></td></tr><tr><td>Media clients</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/media-clients.md">Media clients</a></td></tr><tr><td>Helpers and imports</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/others.md">Others</a></td></tr><tr><td>Metadata and mapping</td><td><a href="https://wiki.crosswatch.app/crosswatch/settings/connections/metadata.md">Metadata</a></td></tr></tbody></table>

### Connect a provider

1. Choose a media server, tracker, media client, or helper.
2. Select **Connect** or **Sign In**.
3. Approve access and save the provider settings.

The approval window may first show a waiting screen while CrossWatch prepares the provider sign-in page. For device-code connections such as Silo and Tofa, note the code before the window redirects. If your browser blocks the popup, use the approval link shown in the connection.

### Tips

* Add [TMDb Metadata and optional Fanart.tv artwork](https://wiki.crosswatch.app/crosswatch/settings/connections/metadata.md).
* Start with **one-way** in your first pair.

### Next steps

* Build your first pair: [Configure Pairs](https://wiki.crosswatch.app/crosswatch/settings/configure-pairs.md)
* Follow the guided setup order: [First-time setup](https://wiki.crosswatch.app/getting-started/first-time-setup.md)

### Browser approval screens

Some connection flows open a provider-branded waiting page before taking you to sign in. If it shows a device code, choose **Copy code and continue**, then paste that code on the provider's approval page. You can also note the code and wait for the countdown. A flow without a code offers **Continue**.

If copying fails, the page pauses. Copy or note the displayed code yourself, then select **Continue**. If the popup is blocked, use the approval link offered in the provider's connection dialog. Return to CrossWatch after approval and follow that provider's remaining steps; some providers still require you to paste a returned authorization code.


---

# 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.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.
