MCP TMDB MCP Server

MCP TMDB becomes available to MCP clients through the mcp tmdb mcp server. This project implements a Model Context Protocol (MCP) server that integrates with The Movie Database (TMDB) API. It enables AI assistants like Claude to interact with movie data, providing capabilities for searching, retrieving details, and generating content related to movies.

What MCP TMDB does

This project implements a Model Context Protocol (MCP) server that integrates with The Movie Database (TMDB) API. It enables AI assistants like Claude to interact with movie data, providing capabilities for searching, retrieving details, and generating content related to movies.

Tools it exposes

Once connected, the assistant can call these 6 tools directly:

• Resources — The Resources tool exposed by this server
• Prompts — The Prompts tool exposed by this server
• Tools — The Tools tool exposed by this server
• Prerequisites — The Prerequisites tool exposed by this server
• Installation — 1. Clone this repository git clone https://github.com/your-username/tmdb-mcp.git cd tmdb-mcp
• Testing — Use the MCP Inspector to test your server during development:

Installing the mcp tmdb mcp server

The server is distributed via npm as @modelcontextprotocol/inspector, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.

Configuration

Before the server will start you need to supply one environment variable: TMDB_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js (v16 or later) - npm or yarn - TMDB API key

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. MCP TMDB sits in that group, and the shape of its toolset — Resources, Prompts, Tools among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• Maintained by ShubhanshuSondhiya, written in Go.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the mcp tmdb mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.