zurg can be driven by an AI agent

zurg has an endpoint at /mcp speaking the Model Context Protocol, so a client like Claude can search your library, work out why a release will not play and repair it. Turn it on with mcp: {enabled: true} and point the client at http://your-zurg:9999/mcp. Clients that only speak stdio use zurg mcp, which pipes to the instance already running.

Open that URL in a browser and zurg tells you what it is, what to connect with, and every tool it is offering.

The default is a working set for reading the library and repairing what is broken. toolsets: [all] gives you the rest, from Plex and Jellyfin to your accounts and the Usenet backend.

Anything that takes something away describes what it would do first and acts only when you confirm that exact plan. read_only: true withholds every tool that changes anything, and no result carries a token, a password or a resolved link.

https://notes.debridmediamanager.com/reference/mcp/

Enable it and let me know if it's useful for you