StreamElements MCP Server
Related Servers
Alternatives to StreamElements MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI assistants to inspect and safely control OBS Studio over obs-websocket v5, exposing scenes, inputs, filters, outputs and video settings as read and write tools that default to dry runs and refuse changes while live unless explicitly confirmed. It also provides Source Record and IRL readiness checks, a BRB auto-switcher, and a scene timeline log for cutting clips from VODs.17MIT

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
WAVE MCP Serverofficial
AlicenseAqualityBmaintenanceExposes WAVE streaming APIs as tools for AI assistants to manage live streams, studio productions, and real-time analytics. It enables users to control stream lifecycles, monitor health metrics, and access billing usage through the Model Context Protocol.24157 npm1Apache 2.0- FlicenseBqualityDmaintenanceThis project is a fork and expansion of TomCools' Twitch MCP Server, which implements a Model Context Protocol (MCP) server that integrates with Twitch chat, allowing AI assistants like Claude to interact with your Twitch channel.101-
- AlicenseAqualityDmaintenanceEnables AI assistants to control DualStream streaming studio: switch scenes, compose layouts, manage widgets, and react to stream events.30Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to build channels from video and audio playlists, start, schedule, sync, stop and monitor live broadcasts across YouTube, Facebook, Twitch, LinkedIn and X, and read stream analytics afterwards. Also covers project and scene editing, media library management with upload and encode workflows, and destination validation, over a stateless streamable HTTP endpoint authenticated with a LiveReacting API key.1MIT
TDQS
Scored across 140 tools
Many tools target distinct resources, but overlaps exist: contests_delete is documented as the same as contests_close, giveaways_create vs giveaways_create_by_id, and several get/details variants (channels_get, channels_get_details, channels_me). Descriptions often note preferences, which helps, but an agent could still misselect among near-duplicates.
Names follow a mostly consistent snake_case resource_action pattern (giveaways_draw_winner, points_get_user, store_items_create). Minor deviations like channels_me, channels_socket, and long names like channels_revoke_access_token are readable but slightly break the verb_noun convention.
140 tools is an extreme mismatch for a single MCP server; the rubric marks 50+ as extreme. Many tools could be consolidated or scoped to sub-servers, and the sheer count makes discovery and selection impractical.
The surface covers a huge portion of the StreamElements API across giveaways, contests, commands, timers, filters, loyalty, points, store, tips, activities, overlays, and chat stats. Minor gaps remain, such as no obvious tool to approve/deny moderated tips or update bot module settings, but core lifecycle operations are present.