Skip to main content
Glama
arr-mcps

komga-mcp

by arr-mcps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to komga-mcp

No user-submitted related servers found.

    Related Servers

    • komga-mcp

      pierrec18
      A
      license
      Not graded
      quality
      B
      maintenance
      A read-only MCP server that exposes Komga reading data via Streamable HTTP, providing tools for searching comics, listing unread series, and tracking reading progress.
      MIT

    • mylar3-mcp

      arr-mcps
      A
      license
      A
      quality
      A
      maintenance
      MCP server that exposes Mylar3's HTTP API as tools, letting an LLM read and manage a comic library including watchlist, wanted issues, upcoming, history, logs, story arcs, and providers.
      5
      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

    • calibreweb-mcp

      ni-c
      A
      license
      A
      quality
      A
      maintenance
      A read-only MCP server that connects to Calibre-Web ebook libraries via OPDS feeds, enabling AI assistants to search and browse books, shelves, covers, and library statistics.
      6
      43 npm
      MIT

    • qui-mcp

      arr-mcps
      A
      license
      B
      quality
      A
      maintenance
      MCP server that exposes qui's JSON REST API as tools for monitoring and managing qBittorrent instances, torrents, automations, cross-seeding, RSS, backups, and related services.
      12
      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.9/5.0

    Scored across 8 tools

    Disambiguation4/5

    The eight top-level tools are clearly separated by resource domain, and most operations have distinct purposes. However, within series and books there are overlapping list operations (e.g., get_latest_series vs get_new_series vs get_updated_series) that could cause an agent to pick the wrong one.

    Naming Consistency5/5

    All tools use the komga_<resource> pattern, and operations consistently follow snake_case verb_noun naming like get_series, create_library, mark_book_unread, and update_collection. The naming is highly predictable with no mixing of conventions.

    Tool Count4/5

    Eight namespace tools is a reasonable scope for a server covering Komga's broad API, and each namespace maps to a meaningful resource domain. However, each tool acts as a large dynamic dispatcher, hiding many operations behind a single tool, which slightly reduces discoverability.

    Completeness4/5

    The server covers the major Komga domains: libraries, series, books, collections, readlists, metadata, users/API keys, and server settings, with update, delete, search, and lifecycle operations. Minor gaps exist, such as no direct list-books-in-series operation (requires a structured search) and no server claim operation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources