
Seerr Mcp Server
io.github.cyanheads由 GitHub 帳號 cyanheads 發布v0.2.0更新於 Oct 29, 2026
Search Jellyseerr/Overseerr, check availability, and create guarded media requests.
概覽
把助理連接到 Jellyseerr/Overseerr 實例,用來搜尋影視、查看可用性並提交需確認的媒體請求。
- 可以做什麼
- 依片名搜尋電影與影集,回傳含 TMDB ID 的排序結果與可用狀態
- 依 TMDB ID 取得精確詳情,影集可看分季概覽或某一季的集數清單
- 依狀態、類型與請求人篩選最近的請求清單
- 預覽並提交媒體請求交由 Radarr 或 Sonarr 處理,寫入前需確認
- 查詢單一請求的狀態、路由資訊與下一步提示
- 彙整已設定的 Radarr/Sonarr 服務、品質設定與實例能力
- 適用情境
- 適合已自架 Jellyseerr 或 Overseerr 的使用者,讓助理在對話中查找片名、確認是否已可觀看或已被請求,並直接送出請求。權限、配額與路由仍由 Seerr 實例本身控管。
- 執行需求
- 需要本機執行環境:Node.js v24+(npx)或 Bun v1.4.0+。需要可連線的 Jellyseerr/Overseerr 實例及其 API 金鑰,透過 SEERR_BASE_URL 與 SEERR_API_KEY 設定(以 X-Api-Key 標頭送出)。可選的 HTTP 傳輸設定如 MCP_TRANSPORT_TYPE、MCP_HTTP_PORT 與 MCP_AUTH_MODE。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Seerr Mcp Server,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。
其他 MCP 客戶端
參照 儲存庫 中的啟動說明。
README
@cyanheads/seerr-mcp-server
Search Jellyseerr/Overseerr, check availability, and create guarded media requests via MCP. STDIO or Streamable HTTP.
Overview
Request movies and shows through Jellyseerr or Overseerr. Search titles, confirm the exact match, check availability and request status, and submit a request for Radarr or Sonarr to fulfill. Your Seerr instance keeps control of permissions, quotas, and routing.
Tools
Resources
All request data is also reachable via tools — request enumeration is the job of seerr_list_requests (the tool-only access path).
Skills
Capability reference
seerr_search_media tool
- Search titles with
mediaType: movie | tv | all; people are excluded.pageis 1–1000;limitis 1–20, default 10. - Returns TMDB matches and decoded
status/status4kfor tracked titles. Empty results return[]with a guidance notice. - Optional ISO 639-1
languageselects localized titles and overviews.
seerr_get_media tool
- Availability plus any existing open request for the title (avoids duplicate requests)
- TV: omit
seasonNumberfor a per-season summary, or pass one to fetch that season's episode list (season 0 is Specials) - A TMDB ID that doesn't resolve surfaces as a typed
media_not_foundwith a search-recovery hint (Jellyseerr's raw HTTP 500 is classified in the service layer)
seerr_list_requests tool
- Filter by lifecycle
filter,mediaType, andrequestedById; sort byaddedormodified, ascending or descending.takeis 1–100, default 20;skipselects the offset. - Returns decoded statuses, requester
{ id, displayName }, and an enrichment trailer with applied filters. includeTitles: truejoins media titles once per distinct title (default off); unresolved rows retain their data and are disclosed in the notice.
seerr_request_media tool
- Guarded write.
mode: preview(default) returns the resolved title and exactPOST /requestpayload without writing.mode: requestasks for confirmation bound to the same caller, title and payload; declined, cancelled or invalid answers returnrequest_cancelled. - TV requests require
seasons: "all"or a list such as[1, 2]; season 0 (Specials) requires special episodes to be enabled. Instance capability checks run before any POST; existing requests appear in output and duplicate rejections returnduplicate_request. - Optional routing overrides:
serverId,profileId,rootFolder,languageProfileId. Omit them to use Jellyseerr's defaults.
seerr_request_status tool
- Accepts
requestIdfromseerr_request_media'screated.requestIdorseerr_list_requests. A missing request returnsrequest_not_found. - Returns decoded
requestStatus,mediaStatus/mediaStatus4k, requester{ id, displayName }, routing (serverId,profileName,is4k), andstateGuidance. - Joins
titleon each call; it is absent when notmdbIdexists or the lookup fails.
seerr_service_options tool
- Returns instance version, media server, capability flags (
movie4kEnabled,series4kEnabled,partialRequestsEnabled,specialEpisodesEnabled), and service IDs, defaults and quality profiles. - Failed service legs retain the available results with a notice.
includePaths: trueexposes root-folder paths and free space; both are omitted by default.
seerr://request/{requestId} resource
- Accepts
requestIdfromseerr_request_mediaorseerr_list_requests; a missing request returnsrequest_not_found. - Mirrors
seerr_request_status, including redaction and a title join.titleis absent when notmdbIdexists or the lookup fails; resources take no per-read options.
Features
Built on @cyanheads/mcp-ts-core: stdio and Streamable HTTP transports, pluggable auth (none / jwt / oauth), swappable storage (in-memory, filesystem, Supabase, Cloudflare KV/R2/D1), structured logging with optional OpenTelemetry tracing.
HTTP requires stateful sessions for 2025-era confirmation rounds; explicit MCP_SESSION_MODE=stateless fails startup. Consent records expire after ten minutes and changed or replayed records ask again. Redemption excludes concurrent retries in one process; request creation makes one POST attempt without automatic retries. Cross-instance read-and-delete is not atomic: use shared strongly consistent filesystem, Supabase or Cloudflare D1 storage for routed retries, and account for duplicate-submission races; Cloudflare KV is unsuitable for consent records.
Seerr-specific:
- Read + guarded-request only — admin-scope endpoints (approve/decline, retry, edit/delete, media/file deletion, user/settings/sync) are excluded by design, not by API limitation
- PII/infra redaction centralized in one normalizer choke point — requesters project to
{ id, displayName }; operator email, Plex/Jellyfin tokens, andserviceUrlnever reach output; filesystem paths are opt-in viaincludePaths - Status decoding centralized in one helper — request and media statuses (including the separate 4K availability) decode to
{ raw, label }everywhere, forward-compatible with new Jellyseerr status codes - Capability validation against cached instance settings catches most bad requests before they reach the API
- A short-TTL settings cache avoids a round-trip on every preview
Agent-friendly output:
- Provenance and disclosure — searches echo the effective query; capped lists disclose truncation; a degraded service leg surfaces a notice instead of silently dropping data
- Typed, actionable errors —
media_not_found,request_not_found,seasons_required,four_k_not_enabled,duplicate_request, and more carry a recovery hint so callers can branch and retry without parsing prose
Getting started
Add the following to your MCP client configuration file, pointing SEERR_BASE_URL at your own Jellyseerr or Overseerr instance and supplying its API key.
Or with npx (no Bun required):
For Streamable HTTP, set the transport and start the server:
Prerequisites
- Bun v1.4.0 or higher (or Node.js v24+).
- A running Jellyseerr or Overseerr instance, and its API key (Settings → General → API Key).
Installation
- Clone the repository:
- Navigate into the directory:
- Install dependencies:
- Configure environment:
Configuration
All configuration is validated at startup via Zod schemas in src/config/server-config.ts. Key environment variables:
See .env.example for the full list of optional overrides.
Running the server
Local development
-
Build and run:
-
Run checks and tests:
Docker
The Dockerfile defaults to HTTP transport, stateful session mode, and logs to /var/log/seerr-mcp-server. OpenTelemetry peer dependencies are installed by default — build with --build-arg OTEL_ENABLED=false to omit them.
Project structure
Development guide
See CLAUDE.md/AGENTS.md for development guidelines and architectural rules. The short version:
- Handlers throw, framework catches — no
try/catchin tool logic - Use
ctx.logfor request-scoped logging,ctx.statefor tenant-scoped storage - Register new tools and resources via the barrels in
src/mcp-server/*/definitions/index.ts - Wrap the Jellyseerr API: validate raw → normalize and redact to a domain type → return the output schema; never fabricate missing fields, and never let operator PII or paths reach output
Contributing
Issues are welcome. Run checks and tests before submitting:
License
Apache-2.0 — see LICENSE for details.
來源:README.md,提交 ebf32a1
工具
0版本歷史
4- v0.2.0最新Oct 29, 2026
- v0.1.5Oct 7, 2026
- v0.1.4Sep 21, 2026
- v0.1.3Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分