komga-mcp
Related Servers
Alternatives to komga-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceA 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
- AlicenseAqualityBmaintenanceMCP 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.5MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to interact with a self-hosted comic/library server through its HTTP API, exposing libraries, series, books, collections, readlists, metadata, and administrative operations with read/write safety controls over stdio or Streamable HTTP.7MIT
- AlicenseNot gradedqualityCmaintenanceEnables interaction with a self-hosted Kavita server through its HTTP API, exposing libraries, series, collections, reading lists, search, metadata, statistics, and account/admin operations as MCP tools with read-only defaults and explicit confirmation for writes.MIT
- FlicenseNot gradedqualityAmaintenanceEnables AI agents to search, browse, download, organize, and post-process comics through MCP tools, including account login, favorites, comments, rankings, configuration, and download task control. Supports stdio, SSE, and HTTP transports while exposing knowledge resources for configuration and skill reference.-
- AlicenseBqualityAmaintenanceMCP 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.15MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.