TMDB MCP Server
Related Servers
Alternatives to TMDB MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceAn MCP server that wraps The Movie Database (TMDB) API, enabling search for movies and TV shows, retrieval of movie details, recommendations, similar movies, trending content, streaming providers, and movie discovery.8-
- FlicenseAqualityDmaintenanceAn MCP server that wraps the TMDB API, enabling search of movies and TV shows, retrieval of details, trending titles, recommendations, and streaming provider information.8-
- AlicenseAqualityDmaintenanceMCP server for the OMDb API - search movies, series, and episodes from any MCP-compatible client.512 PyPIMIT
- AlicenseBqualityCmaintenanceA local, read-only MCP server for discovering movies and TV series from The Movie Database (TMDB). It provides tools for search, details, trending, discovery, and related content.2966 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables searching movies, TV shows, and people on TMDB, with full details, credits, ratings, trailers, images, recommendations, trending, discovery, and region-aware streaming availability via MCP.Apache 2.0
- AlicenseBqualityCmaintenanceEnables searching and browsing TMDB catalog data, discovering movies and TV shows, checking streaming availability, and managing a user's ratings, watchlist, favorites, and custom lists through MCP tools.3066 npmMIT
TDQS
Scored across 33 tools
Most tools have a clearly distinct role, and the descriptions explicitly disambiguate the risky pairs (search_movies vs search_multi, get_movie vs get_movies, get_movie_recommendations vs get_similar, get_movie_releases vs discover_movies vs get_trending). The remaining hazard is naming-level: singular/plural pairs like get_movie/get_movies and get_tv/get_tv_shows look interchangeable at a glance even though the descriptions define one as full detail and the other as a batch card.
The surface follows a predictable verb_noun scheme (get_movie, search_tv, discover_movies, get_tv_episode, get_watch_providers), which makes the set easy to scan. Minor deviations exist: find_by_imdb_id uses 'find' instead of get/search, and get_similar/get_trending omit the noun.
33 tools is heavy and sits in the 'too many' band, but the TMDB domain is genuinely broad (movies, TV, seasons, episodes, people, credits, collections, providers, genres, keywords, ratings, discovery), so nearly every tool maps to a real capability rather than filler. It is still borderline: a few batch/detail pairs (get_movie vs get_movies, get_tv vs get_tv_shows) and the four search_* tools could arguably be consolidated.
Coverage is exceptional: search across all media types, full detail plus compact batch cards, credits for movies/TV/people, recommendations and similar, reviews, collections, trending, two rich discover endpoints, watch providers, videos, seasons and episodes, plus external ratings, genre/keyword/company/provider resolution and IMDb-id resolution. Only minor read paths are absent (images/posters, company/network detail endpoints, account lists), which agents can work around.