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-
- AlicenseAqualityCmaintenanceMCP server for the OMDb API - search movies, series, and episodes from any MCP-compatible client.5MIT
- AlicenseBqualityBmaintenanceA 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.29138 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.46 npmApache 2.0
- FlicenseBqualityCmaintenanceEnables searching, discovering, and reading movie information from TMDB through MCP tools.5-
TDQS
Scored across 31 tools
The tool set is generally well-differentiated by search_/get_/discover_ verbs, but several tools have overlapping or easily confused purposes: get_movie vs. get_movies and get_tv vs. get_tv_shows differ in payload depth rather than resource, get_similar overlaps with both recommendation tools, and search_watch_providers vs. get_watch_providers operate in opposite directions. The detailed descriptions help, but an agent could still misselect among these similarly named variants.
Most tools follow a consistent snake_case verb_noun pattern: search_* for lookups, get_* for data retrieval, and discover_* for filtered discovery. Minor deviations like find_by_imdb_id, search_multi, and the misleading singular/plural pairs get_movie/get_movies and get_tv/get_tv_shows keep it from being perfectly consistent, but the overall convention is readable and predictable.
At 31 tools, the surface is well past the 25+ threshold where tool selection cost starts to outweigh coverage benefits. The broad TMDB domain justifies many of these, but the server could be consolidated by merging the compact batch variants into the primary get_movie/get_tv tools and reducing search_multi/search_movies/search_tv redundancy.
As a read-only media metadata server, the surface is impressively complete: search, full and compact details, credits, reviews, ratings, recommendations/similar, discovery, genres, watch providers, videos, and TV episode/season data are all covered. Minor gaps such as images, translations, and now-playing/upcoming list endpoints remain, but agents can usually work around them with discover_movies/discover_tv and get_videos.