Requirements and responsibilities
Name the team, server, hostname, owner and affected users for the Jellyfin application. Record the current version and the actual business flow that must survive the change. Confirm the current dashboard form, plan eligibility, and server capacity before committing a resource change. A one-click catalog listing is discovery, not permission or proof that the connected MCP profile can install it.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Prepare a non-sensitive test input and an acceptance record. Keep access to the app administrator and an independent observer where possible; omit secrets from AI prompts and client reports.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
For a Docker app, identify persistent volumes, bind mounts, external databases and app-level export requirements. A Docker backup briefly stops the app, and an in-place restore replaces current state. Agree a maintenance window and owner before any action that interrupts the service or overwrites data.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Illustrative situation
A household Jellyfin library still loads but some users cannot play a newly added video. The operator must separate library rights, scan state, codec/transcoding and storage recovery.
Choose the approach
A metadata backup cannot replace source media files.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
A successful admin playback is not proof a limited user or remote device has access.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Dashboard and application procedure
Follow these steps yourself, or use the scoped AI handoff below for supported hosting operations.
Step 1 of 5
Check library and user scope
- Where
- Jellyfin Dashboard → Libraries and Users
- Permissions
- Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Affected user, media path, library permission
- Action
- Confirm the file exists and the user's account can view that library. Note whether newly added libraries inherit access.
- Expected result
- A permission diagnosis.
- Verify
- Compare admin and limited-user library lists.
- If it fails
- If user lacks rights, grant only intended library access.
Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types
Step 2 of 5
Inspect scan and metadata
- Where
- Jellyfin library scan and logs
- Permissions
- Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- File path, scan time, metadata result
- Action
- Run or review library scan and check whether the item is indexed under the intended library. Inspect path and container mount permissions.
- Expected result
- A known indexing state.
- Verify
- Search item as limited user and compare logs.
- If it fails
- If media is absent, fix mount/path before transcoding settings.
Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types
Step 3 of 5
Test playback on target client
- Where
- Jellyfin viewer client
- Permissions
- Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Known item, browser/device, subtitles
- Action
- Play the affected item and a known-good control, noting direct play versus transcode and error text.
- Expected result
- A client-specific playback result.
- Verify
- Compare CPU, disk and network during playback.
- If it fails
- If only one codec/device fails, address transcoding or client support instead of moving all media.
Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types
Step 4 of 5
Check users and remote access
- Where
- Jellyfin users/network settings
- Permissions
- Authorized Jellyfin application administrator or delegated role with rights for this task; hosting access alone is insufficient.
- Inputs
- Remote access policy, device list
- Action
- Review account restrictions and remote exposure; test a second limited account and revoke stale access.
- Expected result
- A controlled viewing policy.
- Verify
- Confirm forbidden library remains hidden.
- If it fails
- If remote access is accidental, close it before adding new users.
Sources: Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types
Step 5 of 5
Protect app data and media
- Where
- Jellyfin backup and xCloud Docker Backup
- Permissions
- Authorized xCloud team/site operator with the discovered write scope for this exact operation and owner approval for its target and interruption.
- Inputs
- Metadata snapshot, source media storage, owner
- Action
- Verify a Completed Jellyfin metadata/app backup and a separate copy of source media. Document version compatibility and restore target.
- Expected result
- A full recovery map for app and files.
- Verify
- Restore a small test library in isolation.
- If it fails
- If original media is missing from backups, label that gap and protect it separately.
Sources: Back up and restore Docker apps · Docker backup operations and storage constraints · Jellyfin backup and restore
Maintenance
Review this task after app or template updates and at the cadence agreed with the owner. Record failures as dated observations rather than assuming host health proves service health.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Watch access changes, backup completion, free storage and external providers. Recheck integrations after credential, DNS, mail or source-data changes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Recovery decisions
Before data recovery, identify incident time, completed backup, target and records created after the snapshot. Preserve current evidence and live data before replacement.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
Use the documented dashboard or application recovery procedure with the authorized owner. Repeat the task-specific limited-user check; reconcile newer records before reopening writes.
xCloud agent capability boundaries · xCloud MCP documentation and connection profiles · Jellyfin backup and restore · Jellyfin user and library access · Jellyfin library administration · Jellyfin transcoding and playback types · Back up and restore Docker apps · Docker backup operations and storage constraints · xCloud One Click Apps catalog
AI handoff
Connect an authorized xCloud MCP profile and discover its exact tools and team scope. The packaged REST wrapper is GET-only; use dashboard or app controls for undocumented writes.
Supported scope
- Confirm requirements and inspect resources mcp · read
Discover the connected profile and operation schema first; only teams granted to the connection are visible.
Checkpoint: Confirm exact team, server and site identity. Use dashboard_url returned by the resource; do not invent a dashboard link.
Operation identifiers and scopes to discover
teams.index, servers.show, sites.show
Scopes: read:servers, read:sites
xCloud MCP documentation and connection profiles · xCloud agent capability boundaries
Copyable agent brief
Manual checkpoints
- Approve exact site, target, cost and any write or maintenance window after inspecting the proposed plan.
- An authorized Jellyfin administrator must configure and test app users, content, integrations and business rules in the app.
- Native WordPress staging, backup schedule/settings, push/pull and all restores are dashboard-only; Docker restore is dashboard-only and replaces state.
- Reconcile data created after the chosen recovery point before any destructive restore.
Feature coverage
- media-ops decision, evidence and task action (covered): The procedure identifies the authorized task boundary and observable result. Check library and user scope Inspect scan and metadata Test playback on target client Check users and remote access
- backup, ongoing operation and recovery (covered): Recovery and maintenance are checked in the task procedure. Check users and remote access Protect app data and media
Sources
- xCloud agent capability boundaries
- xCloud MCP documentation and connection profiles
- Jellyfin backup and restore
- Jellyfin user and library access
- Jellyfin library administration
- Jellyfin transcoding and playback types
- Back up and restore Docker apps
- Docker backup operations and storage constraints
- xCloud One Click Apps catalog