TMDB MCP Server

Created By
rakeshgangwara year ago
Overview

what is TMDB MCP Server?

TMDB MCP Server is a Model Context Protocol (MCP) server that provides access to The Movie Database (TMDB) API, enabling AI assistants to search and retrieve movie information through the MCP interface.

how to use TMDB MCP Server?

To use TMDB MCP Server, clone the repository, install the dependencies, build the server, and configure it with your TMDB API key in the MCP settings file.

key features of TMDB MCP Server?

  • Search movies by title, year, and other criteria
  • Retrieve detailed movie information
  • Easy integration with MCP-compatible AI assistants

use cases of TMDB MCP Server?

  1. AI assistants providing movie recommendations based on user queries.
  2. Applications that need to fetch movie details for display.
  3. Research projects analyzing movie data from TMDB.

FAQ from TMDB MCP Server?

  • Do I need an API key to use TMDB MCP Server?

Yes, you need to obtain a TMDB API key to access the movie database.

  • What are the prerequisites for running TMDB MCP Server?

You need Node.js version 18 or higher and a TMDB API key.

  • Is TMDB MCP Server open source?

Yes, TMDB MCP Server is open source and licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
rakeshgangwar
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago