IMDb MOVIEmeter API

Entertainment teams watch IMDb popularity because it clusters with trailers and press cycles. Trends MCP returns the MOVIEmeter leaderboard as JSON for agents and dashboards.

People search in plain language: IMDb MOVIEmeter API, IMDb trending movies JSON, movie popularity feed for newsletters. The web results split quickly between enterprise data marketplaces, scraper marketplaces, and forum threads that end with "there is no official trending endpoint".

Trends MCP lists IMDb MOVIEmeter as a top_trends feed in the public reference. The practical outcome for builders is a stable JSON contract and a single auth model shared with the rest of the catalog.

Request shape

{
  "mode": "top_trends",
  "type": "IMDb MOVIEmeter",
  "limit": 25
}

The type string must match documentation character for character. If a script silently lowercases strings, the server responds with a parameter error instead of a silent empty list.

Why entertainment teams still open this feed

Studios, streamers, and creator networks watch popularity lists because they compress many weak signals into one ordered view. A writer room can spot a title climbing before the meme accounts post the clip dump. A partnerships lead can time outreach when attention is rising rather than after the peak.

The leaderboard is a blunt instrument. A rank move can reflect trailer drops, awards chatter, controversy, or Wikipedia rabbit holes. Strong workflows keep a second column in the spreadsheet, for example news volume for the title string from https://trendsmcp.ai/news-volume-api, or YouTube search interest from https://trendsmcp.ai/youtube-api.

cURL example

curl -s -X POST https://api.trendsmcp.ai/api \
  -H "Authorization: Bearer YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"mode":"top_trends","type":"IMDb MOVIEmeter","limit":25}'

Official meter products versus automation JSON

IMDb publishes meter definitions in developer documentation. MOVIEmeter ranks the most active movie titles on the site, and bulk history exists for licensed analytics buyers. That path is appropriate for heavy research departments.

Trends MCP targets engineers who need a lightweight pull inside an agent or a nightly job. Read the meter dictionary if the team must explain the metric to legal or finance reviewers. Keep the implementation details in https://trendsmcp.ai/docs so token spend stays predictable.

MCP wiring for creative assistants

Claude, ChatGPT, and Cursor setups follow the same pattern as other feeds. The product index includes https://trendsmcp.ai/mcp-server-for-claude and https://trendsmcp.ai/mcp-server-for-chatgpt. Ask the model explicitly to query via TrendsMCP so the call routes to tools instead of a hallucinated chart.

Adjacent culture signals

For books and GitHub activity in the same research pass, see https://trendsmcp.ai/culture-trends-api-books-movies. For games concurrency context, https://trendsmcp.ai/steam-api stays closer to live player demand than film buzz alone.

Common questions

No. The feed is a compact ranked list intended for trend detection. Enrich titles in a second system if the workflow needs credits, distributors, or financials.
That is outside the MOVIEmeter leaderboard contract. For long horizon attention curves on a topic, use Wikipedia page views or Google Search volume where the keyword mapping is clean.
No. Official bulk products ship historical rank snapshots for licensed data buyers. Trends MCP focuses on a simple developer surface for the current leaderboard inside automation.
Get IMDb MOVIEmeter API in 30 seconds
Free tier includes 100 requests per month. No credit card required. Works with Claude, Cursor, ChatGPT, Raycast, and every MCP client.
Get your free API key