Inspects and safely controls OBS Studio over obs-websocket v5. Provides read tools for version/performance stats, scenes, inputs, filters, outputs, video settings, and timeline data; guarded write tools for switching scenes, changing filter/input settings, and starting/stopping recording; plus Source Record and IRL readiness checks, an IRL BRB auto-switcher, and a scene timeline log for correlating scene changes with VOD timestamps.
Enables 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.
17
MIT
Why this server?
Controls OBS Studio through WebSocket API for automated scene switching, overlay management, and media element control during live streams
A TypeScript-based middleware that translates Claude AI's decisions into OBS WebSocket commands, enabling solo creators to automate streaming production without manual technical management.
23
2
MIT
Why this server?
Allows for the remote control of OBS Studio via the obs-websocket plugin, providing capabilities to manage scenes, recording and streaming status, audio inputs, and source visibility.
An MCP (Model Context Protocol) server for controlling OBS Studio via the built-in obs-websocket plugin. Lets Claude control your scenes, recording, streaming, audio, and more.
26
16 npm
1
MIT
Why this server?
Allows controlling AR lenses, face filters, Vtuber avatars, and effects in OBS Studio via Streamfog and Streamer.bot during live broadcasts.
AI-driven AR lens orchestrator for live OBS streams that enables control of Streamfog face filters, AR effects, and Vtuber avatars through MCP tools via the local Streamer.bot WebSocket bridge.
5
2
MIT
Why this server?
Provides tools for controlling and automating OBS Studio, including scene and source management, audio control, recording/streaming, transitions, filters, media playback, and diagnostics via OBS WebSocket.
Enables AI assistants to control and automate OBS Studio via natural language, covering scenes, sources, audio, recording, streaming, transitions, filters, media playback, diagnostics, and multi-step workflows over the OBS WebSocket protocol.
89
MIT
Why this server?
Provides tools for interacting with OBS Studio, enabling control of scenes, sources, filters, audio routing, media, and more, along with historical event insights such as audio levels and media status.
An MCP server for OBS Studio that subscribes to events and maintains a history, enabling queries about audio levels, source states, and past actions rather than only one-shot requests.
67
MIT
Why this server?
Provides tools for interacting with OBS Studio through its WebSocket v5 interface, enabling management of scenes, sources, audio, transitions, filters, recording, streaming, canvas, profiles, and other OBS functionality.
Enables MCP clients to control OBS Studio through an inspectable WebSocket interface. Provides 155 tools for managing scenes, sources, audio, transitions, filters, recording, and streaming through natural language.
155
296 npm
3
GPL 2.0
Why this server?
Provides control of OBS Studio via obs-websocket, including scene and input management, media source playback and seeking, audio mixer adjustments, and screenshots of scenes or sources.
Enables control of OBS Studio via MCP, including media source playback, scene management, audio mixer adjustments, and screenshot capture, using OBS's WebSocket v5 protocol.
32
MIT
Why this server?
Connects to OBS Studio via the WebSocket protocol, providing tools for scene management, source control, streaming/recording control, transitions, and general operations in OBS.
A server that provides tools to control OBS Studio remotely via the OBS WebSocket protocol, enabling management of scenes, sources, streaming, and recording through an MCP client interface.