Skip to main content
Glama
OrellBuehler

Tdarr MCP Server

by OrellBuehler
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Tdarr MCP Server

No user-submitted related servers found.

    Related Servers

    • tdarr-mcp

      maximeallanic
      A
      license
      C
      quality
      D
      maintenance
      MCP server for interacting with Tdarr, a distributed transcoding system. Provides 21 tools for monitoring workers, managing flows, and controlling transcoding libraries.
      4
      100
      2
      MIT

    • sonarr-mcp

      OrellBuehler
      A
      license
      B
      quality
      B
      maintenance
      Connects AI agents to Sonarr, exposing 136 tools for managing a TV library — adding series, chasing missing episodes, fixing the download queue, tuning quality profiles, and diagnosing health issues.
      136
      8 npm
      MIT

    • flick

      Manny7717
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to interact with a Jellyfin media server, allowing them to search the library, fetch item details, list active playback sessions, and retrieve next-up episodes.
      5
      MIT

    • Arr MCP

      drmogie
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude to monitor and manage a self-hosted media stack—including Sonarr, Radarr, Prowlarr, Bazarr, Overseerr, qBittorrent, and Jellyfin—through tools for status, queues, searches, additions, requests, downloads, and now-playing checks. It also supports arbitrary API calls with safety levels and secret redaction.
      10
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 85 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action; even close pairs like delete_job_report/delete_job_reports or restart_server/relaunch_server/restart_node are clearly separated by description and target. The detailed descriptions make misselection unlikely.

    Naming Consistency4/5

    Overall naming follows a predictable verb_noun snake_case pattern (list_x, get_x, delete_x, update_x, search_x). There are minor inconsistencies like check_for_update vs verify_folder_exists, find_duplicates instead of list_duplicates, and alter_worker_limit vs update_node, but these deviations do not obscure the general convention.

    Tool Count1/5

    85 tools is far beyond the 25+ threshold and creates an enormous, unwieldy surface for an agent to consider. Even if each tool is individually focused, the set as a whole is excessive and hard to navigate.

    Completeness3/5

    The set covers operations, monitoring, plugin management, read-only flows, job reports, backups, and run-only automations, but lacks create/update/delete tools for libraries, flows, and automations, and has no backup restore. These are notable gaps for full lifecycle management, though core transcode workflows are covered.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources