No user-submitted related servers found.
Scored across 155 tools
Most tools map cleanly to distinct OBS resources and actions, and the consistent get/set/toggle/start/stop pattern helps separate them. Only a couple of concepts, such as source active/show state versus scene item enabled state, could cause misselection.
Every tool is prefixed with obs- and follows a predictable hyphenated verb-noun pattern, e.g., get-, set-, create-, remove-, toggle-, start-, stop-. Despite the large number of tools, the naming convention remains highly consistent throughout the entire set.
155 tools is far beyond the 25+ threshold and constitutes an extreme tool-surface mismatch for an MCP server. The set is comprehensive, but the sheer count creates excessive selection overhead and is especially redundant given that obs-call-request already provides generic access to the full OBS WebSocket API.
The surface covers nearly all major OBS domains: scenes, scene items, inputs, filters, transitions, audio, outputs, recording, streaming, profiles, collections, hotkeys, media, and more. Any niche gap can likely be addressed through obs-call-request, so agents are unlikely to hit dead ends.