audiobookshelf
Related Servers
Alternatives to audiobookshelf
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables 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.12MIT
- AlicenseAqualityBmaintenanceEnables interaction with a self-hosted Tube Archivist v0.6.0 archive through its JSON API and WebVTT subtitles, exposing tools for search, library, video, channel, playlist, download, task, configuration, maintenance, user, and media operations over stdio or Streamable HTTP. Write operations require explicit confirmation and an allow-writes setting.14MIT
- 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 self-hosted Miniflux instances through the HTTP API, covering feeds, categories, entries, enclosures, icons, OPML, users, and API keys. Write operations are confirm-gated with dry-run previews and secret redaction.6 npmMIT
- AlicenseAqualityBmaintenanceConnects an MCP client to a self-hosted Ampache 8.4.0 server through its JSON API, enabling library browsing and search, playlist and smartlist management, catalog tasks, shares, podcasts, and user administration. Writes are gated behind a boolean confirm flag plus an explicit allow-writes setting, and secrets such as API keys, session tokens, and passwords are redacted from responses.7MIT
- AlicenseBqualityBmaintenanceConnects 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.4MIT
TDQS
Scored across 13 tools
Top-level tools split cleanly by resource, but abs_libraries duplicates capabilities of other tools (get_collections, get_items, get_authors, get_narrators, get_playlists, get_series, get_search, get_stats), so an agent could reasonably pick either abs_collections.get or abs_libraries.get_collections. abs_me also overlaps with abs_sessions (get_listening_sessions vs get_session) and abs_items (bookmarks/progress). The descriptions are templates that never explain when to use the library-scoped variant over the dedicated resource tool.
Every tool follows a uniform abs_<plural-resource> pattern in snake_case, which is highly predictable. Internal action names are also consistently snake_case verb_noun, though some are awkward or generated-looking (get_series_id_series_id, get_progress_id_episode_id, post_batch_get).
13 tools is a good count for an API-covering server and each maps to a recognizable domain object. However, several tools are heavily overloaded (abs_libraries with 26 actions, abs_me with 23, abs_items with 18), so the true surface is much larger than the tool count suggests.
Core media domains are covered (items, libraries, series, authors, collections, playlists, podcasts, search, stats, sessions, me). But the descriptions repeatedly reference destructive actions for users, backups, API keys, and server settings that have no corresponding tool, leaving notable gaps for admin work. There is also no obvious 'help'/'list actions' tool beyond an action=help convention buried in descriptions.