nuvio-mcp
Related Servers
Alternatives to nuvio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage videos on PlayVideo, including collections, videos, webhooks, embed settings, API keys, and account management.2 npmMIT
- FlicenseNot gradedqualityDmaintenanceEnables full management of a Plex Media Server via Claude, including browsing libraries, fixing metadata, managing collections, and more.-
- AlicenseNot gradedqualityDmaintenanceEnables users to manage and control their Plex media library through natural language commands in MCP-compatible AI clients. It supports searching content, managing playlists, tracking library statistics, and monitoring live viewing sessions.MIT

@volter/tunnel-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables AI agents to manage account, usage, and abuse operations for the Volter tunnel relay.1,109 npm2Apache 2.0- AlicenseNot gradedqualityDmaintenanceEnables AI systems to manage Verodat accounts, workspaces, and datasets, including creating datasets, querying data, and executing AI-powered queries through natural language.9 npmApache 2.0
- FlicenseNot gradedqualityDmaintenanceProvides interaction with Jellyfin media server via the Jellyfin REST API, enabling content management and server configuration through natural language.4-
TDQS
Scored across 73 tools
The canonical tools are mostly distinct by resource+action, but the set includes 8 deprecated aliases that duplicate core operations (set_setting/unset_setting vs update_settings, copy_profile_setup/copy_settings vs copy_setup, toggle_addon vs update_addon, mark_watched vs add_to_watch_history). The [DEPRECATED] cross-references help, but in a 73-tool surface they still create avoidable selection ambiguity.
All tools share a nuvio_ prefix and mostly use verb_noun names, but the verb vocabulary is mixed: list_ vs get_ for reads, update_ vs set_ vs unset_ for settings, and deprecated aliases (toggle_, mark_, copy_) break the canonical pattern. It remains readable because the resource nouns are clear.
73 tools is an extreme count for a single MCP server, even for a broad media-profile management domain. The deprecated compatibility aliases could be hidden or stripped to reduce the surface significantly; exposing them all bloats the toolset.
The surface covers the full lifecycle of every major entity: profiles, addons, plugins, settings, collections, library, watch progress/history, provider credentials, trackers, sessions, and backups, plus snapshot/undo infrastructure. I don't see obvious operational gaps that would force agents into dead ends.