Skip to main content
Glama
maximeallanic

tdarr-mcp

by maximeallanic
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to tdarr-mcp

No user-submitted related servers found.

    Related Servers

    • Tdarr MCP

      hollanbm
      A
      license
      Not graded
      quality
      C
      maintenance
      A FastMCP server that exposes Tdarr's OpenAPI endpoints as MCP tools, enabling management and monitoring of Tdarr transcoding jobs.
      MIT

    • Arr-MCP

      LtMarx
      F
      license
      A
      quality
      B
      maintenance
      MCP server to manage your *ARR media stack (Radarr, Sonarr, Lidarr, Readarr, Prowlarr) for searching, adding, and managing movies, TV shows, music, books, and indexers.
      1
      -

    • prowlarr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Prowlarr's API v1 as tools for managing indexers, applications, download clients, and more, including cross-indexer searches and system commands.
      10
      MIT

    • mcp-arrstack

      indlns
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that enables local LLMs to manage a home media stack including Radarr, Sonarr, Prowlarr, and others.
      MIT

    • Tdarr MCP Server

      OrellBuehler
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to monitor, manage, and operate a Tdarr transcoding farm by inspecting nodes, workers, queues, libraries, plugins, and job reports, and by triggering scans, requeues, and worker actions.
      85
      85 npm
      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

    C2.6/5.0

    Scored across 105 tools

    Disambiguation2/5

    While most tools are named by resource+action, several generic database accessors overlap: tdarr_cruddb, tdarr_client, and legacy tdarr_search_db all provide table/file lookups or updates. tdarr_status/tdarr_is_server_alive and tdarr_read_plugin/tdarr_read_plugin_text also blur boundaries, so an agent may not reliably pick the right tool.

    Naming Consistency3/5

    All tools share the tdarr_ prefix and mostly use snake_case verb_noun names, but conventions are mixed: generic tools like tdarr_cruddb, tdarr_client, tdarr_status, tdarr_debug, and tdarr_item_proc_end break the verb_noun pattern, while stats_get_* and auth_*/admin_*/public_auth_* introduce different orderings. The pattern is readable but not predictable enough for a set this large.

    Tool Count1/5

    105 tools is far beyond a typical MCP surface and includes low-level node handshake/relay methods, updater mechanics, and raw database access that duplicate higher-level operations. The sheer count makes browsing and selection impractical, fitting the extreme mismatch calibration.

    Completeness4/5

    The set covers most Tdarr workflows: backups, libraries/scans, transcode decisions, plugins, nodes, stats, auth, and job reports. It lacks explicit library create/delete operations and some higher-level flow management, but the generic db/client tools and broad coverage mean agents can work around minor gaps.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources