Skip to main content
Glama
rollecode

Sonarr MCP server

by rollecode

Related Servers

Alternatives to Sonarr MCP server

No user-submitted related servers found.

    Related Servers

    • 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
      9 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Exposes the Sonarr v3 REST API as MCP tools, enabling LLMs to read and manage a Sonarr instance including series, episodes, downloads, history, and more. Supports both read and write operations, with destructive tools flagged.
      15
      MIT
    • A
      license
      C
      quality
      A
      maintenance
      Enables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.
      171
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Enables AI assistants to manage TV series collections through Sonarr's API using natural language interactions. Supports searching, adding, updating, and deleting TV series with detailed control over quality profiles, season monitoring, and episode downloads.
      9
      -
    • A
      license
      C
      quality
      A
      maintenance
      Exposes all 209 Audiobookshelf API routes as tools, letting Claude.ai and Claude Code manage libraries, books, podcasts, playback, users, settings, and more.
      212
      78 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.
      28
      31 npm
      MIT

    TDQS

    C2.8/5.0

    Scored across 235 tools

    Disambiguation4/5

    Most tools map to a distinct resource+action and are clearly separable (get_series_by_id vs list_series vs delete_series_by_id). However, clusters like create_indexer_test / create_indexer_testall / create_indexer_action_by_name, and the 'create_' prefix applied to non-create POSTs (create_system_restart, create_system_shutdown, create_release_push), create mild confusion about which endpoint does what.

    Naming Consistency5/5

    An extremely systematic snake_case verb_noun convention is used throughout: get_/list_/create_/update_/delete_ + resource + suffix (_by_id, _bulk, _schema, _test, _testall). Deviations like get_result_page or get_by_path are rare and still readable.

    Tool Count1/5

    235 tools is a near-verbatim dump of the entire Sonarr v3 REST surface, far beyond what an agent can select from reliably. Many are low-value variants (per-resource test/testall/action-by-name, config singletons, static-resource readers) that bloat the surface.

    Completeness5/5

    Coverage is essentially exhaustive: full CRUD across series, episodes, files, indexers, download clients, import lists, notifications, quality/language profiles, plus config, commands, history, wanted, calendar, backup and system endpoints. No obvious lifecycle gaps remain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues