Skip to main content
Glama

Related Servers

Alternatives to bookshelf-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      MCP server exposing Seerr's full v1 REST API as tools, enabling LLMs to search and discover media, manage requests and approvals, users, issues, watchlists, and integration settings for Plex/Jellyfin/Emby and Sonarr/Radarr, including reads and writes with destructive operations flagged.
      15
      MIT
    • 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
    • A
      license
      Not graded
      quality
      C
      maintenance
      HTTP MCP server enabling LLMs to search, create, read, update, and delete BookStack entities (books, chapters, pages, shelves) using API tokens.
      242 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Exposes the Sonarr v3 REST API as MCP tools, enabling LLMs to read and manage a Sonarr instance including series, episodes, downloads, history, and more. Supports both read and write operations, with destructive tools flagged.
      15
      MIT
    • 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
    • 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

    TDQS

    B3.2/5.0

    Scored across 15 tools

    Disambiguation4/5

    Each tool covers a distinct functional domain (media, profiles, config, system, etc.), making primary purposes clear. However, some domains overlap conceptually—e.g., media_library handles bookfiles while storage handles filesystem paths—so an agent might occasionally hesitate between tools.

    Naming Consistency5/5

    All tools follow the consistent pattern `bookshelf_<domain>` using snake_case. This makes the naming predictable and easy to navigate, with no mixed conventions or irregular verb forms.

    Tool Count4/5

    With 15 tools, the server sits at the upper boundary of the typical well-scoped range. The count is reasonable for a full-featured media server API, though the number is on the higher side and might feel slightly heavy.

    Completeness4/5

    The tools cover a broad spectrum of Bookshelf operations including CRUD for books, authors, profiles, config, notifications, indexers, queue, and more. Minor gaps exist—e.g., no explicit 'remove from shelf' operation—but core workflows are well represented.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues