Skip to main content
Glama
arr-mcps

mylar3-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mylar3-mcp

No user-submitted related servers found.

    Related Servers

    • radarr-mcp

      arr-mcps
      A
      license
      C
      quality
      A
      maintenance
      MCP server exposing Radarr's v3 REST API as tools, enabling LLMs to read and manage movies, downloads, history, indexers, and more.
      100
      MIT

    • bookshelf-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server that exposes the Bookshelf (Readarr fork) v1 REST API as tools, allowing an LLM to read and manage authors, books, book files, editions, series, download queue, history, indexers, import lists, custom formats, tags, commands, and system status, with full read/write access and destructive tools flagged.
      15
      MIT

    • lidarr-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server exposing Lidarr's full v1 REST API as tools for reading and managing artists, albums, tracks, queue, history, and more. It enables LLMs to interact with a Lidarr instance via natural language.
      15
      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

    • qbit_manage-mcp

      arr-mcps
      A
      license
      A
      quality
      B
      maintenance
      MCP server exposing qbit_manage's Web API as tools, so an LLM can read and manage a qbit_manage instance: run maintenance commands on qBittorrent torrents, manage config files, scheduler, logs, security settings, and system state.
      6
      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

    A4.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    The five tools are clearly grouped by domain (comics, issues queue, lists/discovery, providers, system), making it easy to select the appropriate namespace. However, there is some overlap between mylar_comics and mylar_issues_queue (e.g., mylar_change_status vs. mylar_queue_issue/unqueue_issue) and subtle differences like mylar_get_comic vs. mylar_get_comic_info that could cause occasional misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case pattern of mylar_<domain> (mylar_comics, mylar_issues_queue, mylar_lists_discovery, mylar_providers, mylar_system). The operation names within each tool also consistently use the mylar_ prefix and a verb_noun style, ensuring predictability.

    Tool Count5/5

    With exactly 5 tools, the server falls well within the ideal 3-15 range. Each tool represents a logical domain and earns its place, even though it internally dispatches many operations. The count is neither too thin nor bloated for the Mylar3 management purpose.

    Completeness4/5

    The tool surface covers the major lifecycle operations for comics (add, delete, get, refresh, pause/resume), issues (queue/unqueue, search), lists (wanted, upcoming, read list, story arcs), providers (CRUD), and system management (version, logs, config, restart). Minor gaps exist, such as no direct tool to edit an issue's metadata beyond queue status, but core workflows are fully supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources