A
licenseA
qualityD
maintenanceEnables AI assistants to control DualStream streaming studio: switch scenes, compose layouts, manage widgets, and react to stream events.
30
Apache 2.0
WAVE MCP Server
Officialby wave-av
Related Servers
Alternatives to WAVE MCP Server
No user-submitted related servers found.
Related Servers
Upstream MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables an AI assistant to run cloud live streaming end to end: starting and stopping broadcasts, reordering playback queues, searching and organizing the media library, planning stream schedules, and managing multistream destinations. It connects over a remote Streamable HTTP endpoint secured with OAuth or a personal access token, applying the same validation, ownership rules, and rate limits as the public REST API.1MIT- AlicenseAqualityFmaintenanceEnables management of multi-platform streaming through the Restream API, allowing control of streaming channels, stream settings, and access to analytics across platforms like YouTube, Twitch, and Facebook through natural language.912 npm1MIT
- AlicenseAqualityBmaintenanceEnables AI assistants and MCP clients to inspect camera streams, probe video/audio codecs, capture live JPEG snapshots, generate playback URLs, discover camera integrations, and manage streams dynamically with strict credential redaction.121MIT
APIVerve MCP Serverofficial
AlicenseNot gradedqualityBmaintenanceProvides access to 249+ production-ready APIs through the Model Context Protocol, enabling AI assistants to fetch weather, news, geocoding, validation, and more data.2 npm4MIT- AlicenseBqualityBmaintenanceAI-powered stream and recording control for OBS Studio through the Model Context Protocol10023Apache 2.0
TDQS
A3.5/5.0
Scored across 24 tools
Disambiguation5/5
Each tool maps to a distinct resource/action pair: design extraction, contract validation, stream lifecycle, camera control, billing reads, and analytics. Even similar-sounding tools like wave_design_contract vs wave_design_contract_check are clearly separated by compose-vs-validate semantics, and wave_get_viewers vs wave_get_stream_metrics are distinguished by account-wide vs single-stream scope.
Naming Consistency4/5
Most tools follow a consistent wave_<verb>_<noun> pattern across streams, productions, billing, and camera actions. Minor deviations like wave_design_contract (noun as operation), wave_voice_converse (noun-verb order), and wave.ask (dot separator instead of underscore) keep it from a 5.
Tool Count3/5
With 24 tools spanning design, productions, streams, billing, camera control, captions, voice, and a meta-planning tool, the server feels like an API grab-bag rather than a tightly scoped set. Most tools have a concrete purpose, but the count is on the heavy side for an MCP server.
Completeness3/5
Core workflows are present for stream lifecycle, production switching, design extraction/validation, analytics, and camera commands. However, there are notable gaps: wave_create_clip and wave_control_camera depend on recording/camera IDs with no discovery tool, and most resources lack update/delete operations.
Maintenance
ActivitySlowing
ResponsivenessSyncing