Most TMDB wrappers stop at search; exposing a movie as an addressable resource means a client can pull one record into context without a tool call, and the two prompts turn a data lookup into something that produces writing. Small surface, but the shape is more thoughtful than the usual API wrapper.
An MCP server over the TMDB API that uses all three MCP primitives rather than tools alone. Tools handle the lookups, resources expose TMDB information and a movie record by id, and prompts package two writing tasks — a review in a chosen style with a rating, and a recommendation based on genre and mood.
- Tools: find movies by title or keyword, retrieve trending movies for a day or a week, and find movies similar to one you name
- Static resources at `tmdb://info` for information about the TMDB API and `tmdb://trending` for the current trending list
- A resource template at `tmdb://movie/{id}` so any movie record can be read by its identifier
- Two prompts: a movie review generated with a specified style and rating, and a personalised recommendation driven by genres and mood
A TMDB API key, supplied as `TMDB_API_KEY` in a `.env` file at the project root. Node.js v16 or later; `npm install` and `npm run build` from a clone, then point the client at `build/index.js` over stdio. `npx @modelcontextprotocol/inspector node build/index.js` is the documented way to check it works before wiring it into a client.
One command plus a key — npx -y tmdb-mcp, then supply credentials