komga
Related Servers
Alternatives to komga
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients to a self-hosted photo library through its REST API, exposing assets, albums, people, search, and optional administrative toolsets with read-only defaults and confirm-gated writes. It supports stdio and localhost Streamable HTTP transports.66 npmMIT
- AlicenseNot gradedqualityCmaintenanceConnects MCP clients to a self-hosted Seafile server through the seahub HTTP API, exposing libraries, files, search, sharing, and optional admin operations over stdio or Streamable HTTP. It defaults to read-focused tools and gates writes behind confirmation, with token redaction and dry-run previews.4 npmMIT
- AlicenseAqualityBmaintenanceMCP server exposing Komga's REST API as tools for browsing and managing comic, manga, BD, magazine, and ebook libraries.8MIT
- AlicenseNot gradedqualityAmaintenanceGives MCP clients read-only access to a local Calibre library, enabling metadata search with Calibre query syntax, BM25 full-text search across EPUB/PDF/MOBI/LIT, chapter and page reading, highlights, notes, reading progress, and duplicate detection. It runs over stdio or Streamable HTTP with bearer authentication, using direct SQLite connections so it keeps working while the Calibre GUI is open.5Apache 2.0
- AlicenseDqualityCmaintenanceEnables secure, configurable access to one or more Syncthing instances over MCP, with read-only defaults and opt-in write, destructive, and administrative operations. Supports stdio and authenticated Streamable HTTP transports, typed tools, bounded responses, and multi-instance configuration.40MIT
- 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
TDQS
Scored across 7 tools
Tools are split cleanly by Komga resource (books, series, collections, readlists, libraries, referential metadata, management), so the main boundaries are clear. However, collections and readlists have almost identical action shapes, and books/series both expose overlapping read-progress and listing actions, which could cause occasional misselection.
Every tool follows the same komga_<resource> snake_case convention, with plural resource names except for the clearly named referential_metadata and management sets. There is no mixing of camelCase or inconsistent verb/noun patterns at the tool level.
Seven tools is a reasonable scoping for a Komga server and keeps the top-level surface manageable. The only slight imbalance is komga_management, which contains a single actuator-info operation and feels underfilled compared with the other resource toolsets.
Core library management coverage is strong: books, series, collections, readlists, and libraries all support relevant read/write/lifecycle operations. There are still notable gaps around administrative surfaces mentioned in the warnings—users, roles, API keys, sessions, settings, password changes, and claims—which have no corresponding toolset.