MyDramaList MCP
Related Servers
Alternatives to MyDramaList MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityBmaintenanceEnables local-first, read-only access to public Letterboxd profile and diary data through a stdio MCP server backed by a SQLite cache.3-
- AlicenseNot gradedqualityCmaintenanceEnables managing a personal media collection of films, series, animation, books, and games via MCP, including adding, searching, filtering, updating, deleting, and retrieving statistics.MIT
- FlicenseNot gradedqualityNot gradedmaintenanceProvides 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-
- AlicenseCqualityAmaintenanceConnects 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.117927 npm4MIT
- AlicenseAqualityBmaintenanceMCP 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.1118 npm11MIT
- AlicenseAqualityAmaintenanceMCP 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.31303 npm5MIT
TDQS
Scored across 89 tools
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.
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.
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.
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.