Skip to main content
Glama
pipeworx-io

mcp-tvmaze

by pipeworx-io

@pipeworx/tvmaze

TVMaze MCP — TV show metadata, episodes, schedules, cast. No auth.

Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.

Tools

  • 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)

Related MCP server: TMDB MCP Server

Data source

https://api.tvmaze.com — public REST/JSON.

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "tvmaze": {
      "url": "https://gateway.pipeworx.io/tvmaze/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/tvmaze/mcp returns the tools in the table above plus the shared Pipeworx meta-toolsask_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.

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 Tvmaze data" })

The gateway picks the right tool and fills the arguments automatically.

More

License

MIT

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

No tool schema history has been recorded yet.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • F
    license
    A
    quality
    D
    maintenance
    Enables querying TV programming data from Tunarr XMLTV feeds, including viewing channel listings, current and upcoming schedules, and searching for programmes by title or description.
    5
    -
  • A
    license
    A
    quality
    C
    maintenance
    Provides access to The Movie Database (TMDB) API, enabling users to search for movies, TV shows, and people, get detailed information, discover content with advanced filters, and retrieve recommendations.
    13
    31
    5
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables querying The Movie Database (TMDB) v3 API for movie and TV show information, including search, episode details, and trending content.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/pipeworx-io/mcp-tvmaze'

If you have feedback or need assistance with the MCP directory API, please join our Discord server