
Connects Claude to the TVMaze API for querying TV show data without authentication. The source shows one tool (search_people for finding actors by name with details like country, birthday, and images), though the description suggests broader episode and schedule metadata is available. Part of the Pipeworx gateway ecosystem, which hosts 673+ data sources and offers an ask_pipeworx natural language interface as an alternative to direct tool calls. Useful when you need Claude to answer questions about TV shows, cast information, or programming schedules. Available as a standalone server or through the full Pipeworx gateway. Runs over streamable HTTP transport.
TVMaze MCP — TV show metadata, episodes, schedules, cast. No auth.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
search_shows(query)get_show(show_id, embed_episodes?, embed_cast?, embed_seasons?)list_episodes(show_id, specials?)get_schedule(country?, date?)search_people(query)https://api.tvmaze.com — public REST/JSON.
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"tvmaze": {
"url": "https://gateway.pipeworx.io/tvmaze/mcp"
}
}
}
tools/list at https://gateway.pipeworx.io/tvmaze/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 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
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 Tvmaze data" })
The gateway picks the right tool and fills the arguments automatically.
MIT