stremio-mcp
Related Servers
Alternatives to stremio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenancePython MCP server for TMDB search, Stremio library management, and Android TV playback/control over native ADB.56MIT
- FlicenseAqualityDmaintenanceMCP server for controlling Android, Fire TV, and Android TV devices through ADB, enabling device management, app operations, screenshots, UI dumps, and OBS recording.30-
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables users to search for movie and TV show resources across multiple sources and validate video link playability. It supports both STDIO and SSE transport modes for seamless integration with AI applications.34 npm5MIT
- AlicenseAqualityDmaintenanceAn MCP server that lets AI agents control Android TVs via ADB, including searching and playing content across streaming services, managing power and volume, and sending remote control commands.68 npm4MIT
- FlicenseAqualityDmaintenanceAn MCP server that wraps the TMDB API, enabling search of movies and TV shows, retrieval of details, trending titles, recommendations, and streaming provider information.8-
- AlicenseBqualityCmaintenanceA local, read-only MCP server for discovering movies and TV series from The Movie Database (TMDB). It provides tools for search, details, trending, discovery, and related content.29271 npmMIT
TDQS
Scored across 55 tools
Most tools target distinct resources or platforms, and the descriptions clarify device-specific playback, addon installation, and subtitle handling. However, there is meaningful overlap among the many playback, search, and addon-management tools (e.g., play vs. stremio_desktop_play vs. stremio_cast_play; search vs. search_all_catalogs; install/configure/show addon), so an agent must read carefully to avoid misselection.
Most tools use snake_case with a stremio_ prefix, but a significant subset (play, add_subtitle, tv_control, push_subtitle, sync_addon, playback_status, etc.) omits that prefix and mixes verb-first, noun-first, and bare-verb styles. The result is readable but not a consistent verb_noun convention.
55 tools is far beyond the practical range for an MCP server, even one covering account, desktop, TV, casting, subtitles, and addons. Many operations could be consolidated or grouped, and the large surface will burden tool selection and agent context.
The surface is extensive: authentication, discovery, library/watch state, addon lifecycle and profiles, subtitle serving/pushing, desktop, streaming server, Android TV, casting, and Trakt sync are all represented. Minor gaps exist (e.g., deleting saved addon profiles, browsing arbitrary installed catalogs), but core workflows are well covered.