
Trakt
io.github.pipeworx-io由 GitHub 帳號 pipeworx-io 發布v0.1.1更新於 Oct 24, 2026
Trakt MCP — TV/movie metadata + watch tracking signals
概覽
Pipeworx 閘道上的 Trakt 遠端套件,讓助理查詢影視中繼資料以及熱門、流行榜單。
- 可以做什麼
- 依關鍵字、類型、欄位、年份、地區、語言等條件搜尋電影與影集
- 取得電影、影集、季與單集的詳細資訊,可選用延伸資料
- 依類型列出熱門(trending)與流行(popular)項目,支援分頁與數量上限
- 透過閘道的 ask_pipeworx 路由工具以自然語言提問
- 適用情境
- 當助理需要 Trakt 的影視目錄資料——片名、季、單集、類型、年份,或目前熱門與流行內容——又不想自行串接 Trakt 時適用。僅提供唯讀查詢,適合資料查找與推薦類問題。
- 執行需求
- 需連線至 Pipeworx 閘道上的遠端 MCP 端點,不需在本機安裝套件。需要 Trakt 的 client_id:使用閘道平台金鑰,或在註冊 Trakt 應用程式後以 _apiKey 查詢參數帶入自己的 client_id。需要能連上該閘道的網路。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Trakt,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Web executable,透過 Streamable HTTP。 遠端服務在工作區中設定後即可從網頁執行環境執行。
交給代理程式安裝
把這段提示詞貼上到 Claude Code、Codex、Cursor 等代理程式,或 SourceWeft 對話中。代理程式會讀取該伺服器的安裝指南,先向你展示發布者、端點和登入方式,經你同意後再把它新增到你的客戶端。金鑰不會寫進任何命令。
閱讀 https://sourceweft.com/mcp/io.github.pipeworx-io%2Ftrakt/install.md,並按其中說明把這個 MCP 伺服器接入我的客戶端。修改任何設定之前,先告訴我它的發布者、端點和登入方式,等我確認。不要把 API 金鑰寫進命令或我會提交的檔案;問我金鑰應從哪裡取得。其他 MCP 客戶端
把它新增到你客戶端的 mcpServers 設定中。
{
"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
來源:README.md,提交 cf9e0cb
工具
0版本歷史
1- v0.1.1最新Sep 16, 2026
評分
已滿足適用檢查項的 85%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通必需25 分
- 已宣告認證方式必需10 分
- 已列出工具必需15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分