Search, details, trending — the surface is small enough that an assistant will not get lost in it, and the `append` parameter on the details call means credits and images arrive with the record instead of costing another round trip. The proxy hostname is baked into the setup, so this is a good fit if you are already inside that stack and a poor one if you want to point at TMDB directly.
A JavaScript MCP server that puts The Movie Database in front of an assistant. It covers the three things you normally hit TMDB for: finding a title, opening one record in full, and seeing what is trending right now. Calls go through the TNL TMDB proxy at production-api.tnl.one rather than straight to TMDB.
- Multi-search across movies, TV shows and people from one query string, with `page`, `language` and `include_adult` on the call — `search_tmdb`
- The full record for one item by type and id, with an `append` parameter to pull extra blocks such as credits and images in the same response — `get_tmdb_details`
- Trending titles across all media types for a chosen time window — `trending_all`
A TMDB API key in bearer-token form, supplied as `TMDB_AUTH_TOKEN`. Node.js 18 or higher, because the server relies on global fetch. The package is `wizzy-mcp-tmdb` (1.0.2 in package.json); the documented client entry runs `npx` with `wizzy-mcp-tmdb`, or you can clone and start `mcp-tmdb-server.js` with `node`. It speaks stdio.
One command plus a key — npm install -g wizzy-mcp-tmdb, then supply credentials