Skip to main content
Glama
rollecode

Audiobookshelf MCP server

by rollecode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Audiobookshelf MCP server

No user-submitted related servers found.

    Related Servers

    • Sonarr MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables full control of Sonarr from Claude.ai and Claude Code by exposing all 234 v3 API operations as tools for managing media libraries.
      234
      8 npm
      MIT

    • seerr-mcp

      rollecode
      A
      license
      B
      quality
      A
      maintenance
      Enables running Overseerr or Jellyseerr from Claude.ai and Claude Code, with all 170 API operations exposed as tools for managing requests, settings, users, issues, and media services.
      170
      MIT

    • Plex MCP server

      rollecode
      A
      license
      C
      quality
      B
      maintenance
      Enables running Plex from Claude.ai and Claude Code by exposing all 405 operations as tools, covering both your media server and plex.tv cloud services with automatic routing to the appropriate host.
      405
      12 npm
      MIT

    • BookStack MCP Server

      pnocera
      A
      license
      B
      quality
      A
      maintenance
      Connects BookStack knowledge bases to Claude through 47+ tools covering complete CRUD operations for books, pages, chapters, shelves, users, search, attachments, and permissions. Enables full management of BookStack content and configuration through natural language.
      56
      108 npm
      87
      MIT

    • Trakt MCP server

      rollecode
      A
      license
      C
      quality
      A
      maintenance
      Enables reading and writing Trakt data from Claude.ai and Claude Code, covering all 334 API endpoints including shows, movies, lists, calendars, scrobbling, and account sync.
      338
      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

    C2.3/5.0

    Scored across 209 tools

    Disambiguation2/5

    209 auto-generated tools with boilerplate descriptions ('Create or act on...', 'Get api...') make it hard to tell similar actions apart. Many tools share structural patterns (batch add/remove, cache purge, continue-listening modifications) and some descriptions are misleading (e.g., create_podcasts_feed says 'Get podcast feed').

    Naming Consistency3/5

    There is a consistent snake_case verb-noun pattern based on HTTP method (list_/get_/create_/patch_/delete_), but 'create_' is used for every POST even when the operation is not a create, and 'get_' is used for state-changing actions like remove-from-continue-listening. This makes names predictable in form but semantically misleading.

    Tool Count1/5

    209 tools is an extreme count for an MCP server, far beyond the 3-15 well-scoped range and well over the 50+ threshold. The surface is essentially the entire REST API dumped into MCP tools, which overwhelms an agent's tool-selection space.

    Completeness4/5

    The tool set covers most major CRUD and admin workflows for an Audiobookshelf server: libraries, users, collections, playlists, podcasts, notifications, backups, and media items. Minor gaps exist, such as no get_settings or get_podcasts_by_id, but the overall surface is broad enough for typical agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources