TMDB MCP Server

Created By
ShubhanshuSondhiyaa year ago
Created an MCP Enabled Server connecting with TMDB API , Tested With MCP Inspector
Overview

what is TMDB MCP Server?

TMDB MCP Server is a Model Context Protocol (MCP) server that connects with The Movie Database (TMDB) API, allowing AI assistants to interact with movie data for various functionalities.

how to use TMDB MCP Server?

To use the TMDB MCP Server, clone the repository, install dependencies, configure your TMDB API key, build the project, and start the server. You can then integrate it with AI assistants like Claude.

key features of TMDB MCP Server?

  • Access to static resources like trending movies and TMDB information.
  • Dynamic resource templates for detailed movie information.
  • Prompts for generating movie reviews and recommendations.
  • Tools for searching movies and retrieving trending data.

use cases of TMDB MCP Server?

  1. Generating customized movie reviews based on user preferences.
  2. Providing personalized movie recommendations.
  3. Enabling AI assistants to fetch and display movie data interactively.

FAQ from TMDB MCP Server?

  • What is required to run the TMDB MCP Server?

You need Node.js, npm or yarn, and a TMDB API key.

  • Can I use this server with any AI assistant?

Yes, it is designed to work with AI assistants that support the Model Context Protocol.

  • Is there any documentation available?

Yes, detailed setup instructions and usage examples are provided in the repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ShubhanshuSondhiya
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago