Tvheadend MCP
Related Servers
Alternatives to Tvheadend MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityAmaintenanceMCP server for SiliconDust HDHomeRun network TV tuners, providing tools to control and query tuners, manage DVR recordings, and run diagnostics.58MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to read and change your Teamarr sports-EPG configuration, including teams, event groups, templates, settings, channels, and Dispatcharr sync. Also provides curated tools for safe settings updates, template fillers, event channel summaries, unmatched stream discovery, and TheSportsDB gating checks.MIT
- AlicenseBqualityBmaintenanceEnables MCP-compatible assistants to inspect and diagnose NVIDIA Shield TV and Kodi over a local network, including redacted logs, playback and add-on checks, settings changes, reversible repairs, backups, and rollback. It runs locally and defaults to read-only until writes or plugin browsing are explicitly enabled.257MIT
- AlicenseNot gradedqualityAmaintenanceEnables managing and observing Technitium DNS Server through MCP, including read-only or read-write tool surfaces, scoped bearer authentication, audit logging, and confirmation gates for destructive operations.MIT
- AlicenseAqualityCmaintenanceMCP server for safely inspecting and operating a local Caddy admin API. Provides read-only tools and dry-run mutations for config management.7MIT
- AlicenseAqualityAmaintenanceMCP server for Nginx Proxy Manager: manage proxy hosts, redirections, streams, Let's Encrypt certificates, and access lists, with dry-run previews on every change and a one-shot HTTPS host workflow.3249 PyPI1MIT
TDQS
Scored across 53 tools
Many tools are resource/action-specific, but the generic tvh_update_node and tvh_delete_node overlap with specialized tools such as tvh_assign_services, tvh_assign_networks, and tvh_update_epg_config. Other boundaries like create_dvr_rule vs. create_timer and scan_networks vs. diagnose_network/probe_reception are mostly clarified by descriptions, but selection is not always obvious.
All tools consistently use the tvh_ prefix plus snake_case, and most follow a tvh_verb_noun pattern. A few nouns/action-style names such as tvh_status, tvh_hardware_tree, tvh_mapper_status, and tvh_recording_action are minor deviations from the dominant pattern.
At 53 tools, the surface is far beyond the typical 3-15 well-scoped range and lands in the 50+ extreme-mismatch band. Even for a broad Tvheadend backend, the set is large enough to overwhelm an agent, and the generic get/update/API-read tools suggest some specialized tools could be consolidated.
The tool set covers the major Tvheadend lifecycle areas: channels/services, networks/muxes, EPG configuration and sources, DVR profiles/rules/timers/recordings, hardware/adapters, diagnostics, snapshots, and maintenance plans. Generic get_node/update_node/delete_node/api_read also provide fallback coverage where explicit CRUD tools are absent.