obs-studio-mcp
Related Servers
Alternatives to obs-studio-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityFmaintenanceA 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.100139 npm132GPL 2.0
- AlicenseBqualityCmaintenanceMCP server enabling LLMs to control OBS Studio through high-level show and effect APIs.1810 npmMIT
- AlicenseAqualityDmaintenanceAn 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.2610 npm1MIT
- AlicenseAqualityBmaintenanceAn 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.67MIT
- AlicenseBqualityBmaintenanceMCP server that gives AI assistants direct control over Streamlabs Desktop, enabling scene switching, source/audio management, and streaming/recording controls through natural language.59MIT
- AlicenseBqualityBmaintenanceEnables 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.155139 npm2GPL 2.0
TDQS
Scored across 36 tools
Every tool has a clearly distinct purpose, targeting specific OBS functions such as scenes, sources, audio, streaming, recording, etc. There is no meaningful overlap that would cause an agent to misselect.
All tool names follow a consistent verb_noun pattern using snake_case, e.g., list_scenes, set_mute, start_stream. No mixing of conventions or irregular naming.
With 36 tools, the count is slightly higher than the typical well-scoped range, but each tool covers a distinct and essential aspect of OBS control, making the set feel comprehensive rather than bloated.
While the tool set covers many common workflows, it lacks creation and deletion actions for scenes and sources (e.g., create_scene, remove_input), leaving notable gaps in full lifecycle management.