About Movies
Movies is an MCP server for finding film and TV information through iTunes Search and TVmaze. It supports title searches, show records, and broadcast schedules.
Key features
- 01Search movies by title or keyword
- 02Find TV shows by name
- 03Retrieve episodes by TVmaze ID
- 04Check schedules by date and country
Use cases
- 01Find a film's director and release date
- 02Look up a series rating and status
- 03Review a show's episode air dates
- 04Check broadcasts for a country and date
MCP support
Exposes four search and lookup tools to MCP clients through a Pipeworx gateway endpoint or as a local stdio server. Gateway connections also include shared Pipeworx meta-tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://gateway.pipeworx.io/movies/mcpclaude mcp add --transport http pipeworx-io-movies https://gateway.pipeworx.io/movies/mcp{"mcpServers":{"pipeworx-io-movies":{"type":"http","url":"https://gateway.pipeworx.io/movies/mcp"}}}Open in Cursor{"servers":{"pipeworx-io-movies":{"type":"http","url":"https://gateway.pipeworx.io/movies/mcp"}}}Open in VS Code{"mcpServers":{"pipeworx-io-movies":{"type":"http","url":"https://gateway.pipeworx.io/movies/mcp"}}}{"mcpServers":{"pipeworx-io-movies":{"serverUrl":"https://gateway.pipeworx.io/movies/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEmcp-movies
Movies MCP — wraps iTunes Search API (movies, free, no auth) and TVmaze API (TV shows, free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1683+ live data sources.
Tools
| Tool | Description |
|---|---|
search_movies | Search for movies by title or keyword. Returns title, director, release date, genre, description, and artwork. |
search_tv_shows | Look up a TV SERIES BY NAME on TVmaze and get its facts in one call — "tell me about the TV show Breaking Bad", "when did The Sopranos air", "how was Chernobyl rated", "what network was Mad Men on", "is The Bear still running". Returns the show name, genres, premiere and end dates, status (Running/Ended), rating, network, summary and images for each match. THE entry point for a named series: it takes the TITLE directly, so a show known by name is answered here without resolving an id first. |
get_tv_show | Full TVmaze record for ONE TV series by its numeric TVmaze show id — the episode list with air dates, plus network, status and rating. The id is an internal TVmaze number, so resolve it with search_tv_shows first and pass what that returns; when the caller names the show rather than an id, search_tv_shows answers directly. |
get_tv_schedule | Check what's broadcasting on a specific date and country (e.g., 'US', 'GB'). Returns shows, times, and channels. |
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"movies": {
"url": "https://gateway.pipeworx.io/movies/mcp"
}
}
}
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/movies/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}
Both URLs reach the same gateway and the same 1683+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
No MCP client? Call it over HTTP
curl -X POST https://gateway.pipeworx.io/v1/tools/search_movies \
-H 'Content-Type: application/json' \
-d '{"query":"Inception"}'
No account needed for the first calls. Inspect any tool: GET https://gateway.pipeworx.io/v1/tools/search_movies. Find one: POST https://gateway.pipeworx.io/v1/tools/search_packs with {"query":"..."}.
Standalone (no gateway account)
This package also runs as a local stdio MCP server — no Pipeworx account, no gateway round-trip:
{
"mcpServers": {
"movies": {
"command": "npx",
"args": ["-y", "@pipeworx/mcp-movies"]
}
}
}
Or run it directly to confirm it starts:
npx -y @pipeworx/mcp-movies
It speaks MCP over stdin/stdout and answers initialize/tools/list/tools/call
for only this pack's tools — none of the shared meta-tools the gateway
connection above adds. Same source, same tools, no ask_pipeworx routing.
Using with ask_pipeworx
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Movies data" })
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.