Skip to main content
Glama
elibonk

MyDramaList MCP

by elibonk

Related Servers

Alternatives to MyDramaList MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managing a personal media collection of films, series, animation, books, and games via MCP, including adding, searching, filtering, updating, deleting, and retrieving statistics.
      MIT
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides access to The Movie Database (TMDB) API for searching movies, retrieving movie details, cast information, and browsing current, upcoming, popular, and top-rated films, as well as searching for actors and directors.
      50 npm
      -
    • A
      license
      C
      quality
      A
      maintenance
      Connects stdio-compatible Model Context Protocol clients to a TIDAL account, enabling catalog search, recommendations, lyrics and credits, favorites, playlists, folders, and discovery through 112 typed tools. Account changes stay off by default and require an explicit preview-then-approval commit, keeping OAuth credentials local.
      117
      927 npm
      4
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server and CLI for accessing Douban movie and book data, including search, details, reviews, charts, and user collections. Supports read-only and write operations (mark movies/books) when authenticated.
      11
      18 npm
      11
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      MCP server for The Movie Database (TMDB): search and look up movies, TV shows and people, and read IMDb/Rotten Tomatoes/Metacritic ratings (via OMDb) in the same call.
      31
      303 npm
      5
      MIT

    TDQS

    C2.8/5.0

    Scored across 89 tools

    Disambiguation4/5

    Most tools have distinct resource+action semantics (e.g. mdl_reviews_submit vs mdl_reviews_edit vs mdl_reviews_delete), and namespaces like titles_/users_/custom_lists_ keep domains separated. A few boundaries are fuzzy, notably mdl_comments_like vs mdl_feeds_like vs mdl_articles_like (like operations across content types) and the get/fetch pairs (mdl_feeds_get vs mdl_feeds_fetch, mdl_watchlist_fetch vs mdl_watchlist_fetch_page), but descriptions mostly disambiguate.

    Naming Consistency5/5

    Every tool follows the same namespace_verb_noun convention (mdl_<domain>_<action>), with consistent snake_case and a predictable verb vocabulary (get, list, fetch, create, edit, delete, like, add, remove). No camelCase mixing or irregular verb styles across all 89 tools.

    Tool Count2/5

    89 tools is far beyond the 15-25 range that keeps a surface navigable for an agent. While the server covers a rich multi-domain API (titles, users, reviews, comments, lists, feeds, notifications, account), the sheer count creates selection and context-loading overhead that undermines usability.

    Completeness5/5

    Coverage is exceptionally thorough: full CRUD for reviews, comments, custom lists, feeds, and watchlist; read paths for titles, users, explore, articles, groups, awards, calendar, leaderboard, plus account/profile management and auth-aware operations. Almost no obvious domain gap remains, with server_status and capabilities providing introspection.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues