
Trakt
io.github.pipeworx-ioPublished by GitHub account pipeworx-iov0.1.1Updated Oct 24, 2026
Trakt MCP — TV/movie metadata + watch tracking signals
Overview
Remote Pipeworx gateway pack for Trakt that lets an assistant look up TV and movie metadata and trending or popular titles.
- What you can do
- Search movies and shows by query, type, fields, years, genres, countries and languages
- Fetch details for a movie, a show, its seasons and individual episodes, with optional extended data
- List trending and popular titles by type, with paging and limits
- Answer plain-language questions through the gateway's ask_pipeworx routing tool
- When to use it
- Useful when an assistant needs Trakt's TV and film catalog data — titles, seasons, episodes, genres, release years, or what is currently trending and popular — without building a Trakt integration. Read-only lookups, so it suits research and recommendation-style questions.
- Requirements
- A remote MCP endpoint at the Pipeworx gateway; no local package. A Trakt client_id is needed: either the gateway's platform key or your own via an _apiKey query parameter after registering a Trakt application. Network access to the gateway.
Installation
In SourceWeft
- Open Trakt in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.pipeworx-io%2Ftrakt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"trakt": {
"type": "http",
"url": "https://gateway.pipeworx.io/trakt/mcp"
}
}
}README
@pipeworx/trakt
Trakt.tv MCP — TV/movie metadata + trending/popular signals.
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tools
search(query, type?, fields?, years?, genres?, countries?, languages?, page?, limit?)get_movie(id, extended?)get_show(id, extended?)list_seasons(show_id, extended?)get_episode(show_id, season, episode, extended?)trending(type, limit?, page?)popular(type, limit?, page?)
Auth
- Platform key: gateway env
PLATFORM_TRAKT_KEY(client_id from a registered Trakt app). - BYO:
?_apiKey=<client_id>after registering at https://trakt.tv/oauth/applications.
Read-only endpoints work with just the client_id (no user OAuth required).
Data source
https://api.trakt.tv — header trakt-api-key + trakt-api-version: 2.
Quick Start
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
What this endpoint actually serves
tools/list at https://gateway.pipeworx.io/trakt/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:
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:
The gateway picks the right tool and fills the arguments automatically.
More
License
MIT
Source: README.md at commit cf9e0cb
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listedRequired15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts