Skip to main content
Glama
takurot

obs-showrunner-mcp

by takurot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to obs-showrunner-mcp

No user-submitted related servers found.

    Related Servers

    • OBS MCP Server

      royshil
      A
      license
      B
      quality
      F
      maintenance
      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.
      100
      139 npm
      132
      GPL 2.0

    • streamlabs-mcp

      AhmadTariq1337
      A
      license
      B
      quality
      B
      maintenance
      MCP server that gives AI assistants direct control over Streamlabs Desktop, enabling scene switching, source/audio management, and streaming/recording controls through natural language.
      59
      MIT

    • OBS MCP

      Tom-R-Main
      A
      license
      B
      quality
      B
      maintenance
      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
      139 npm
      2
      GPL 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 18 tools

    Disambiguation4/5

    Most tools are clearly distinct by resource and action: start_show/end_show/switch_segment handle show flow, while set_scene/get_scene_list handle scenes, and show_overlay/hide_overlay handle overlays. The only mild ambiguity is between switch_segment and set_scene, and between trigger_effect and update_source_content, but the descriptions clarify their different purposes. Overall boundaries are distinct.

    Naming Consistency5/5

    The naming is highly consistent: nearly all tools use a clear verb_noun pattern (start_show, end_show, switch_segment, show_overlay, hide_overlay, get_scene_list, set_scene). All use snake_case with imperative verbs. The style is uniform and predictable throughout.

    Tool Count4/5

    18 tools for a show-runner MCP server feels appropriate given the breadth of capabilities it needs to cover: show lifecycle, OBS scene management, overlays, effects, health monitoring, and audio. Each tool serves a distinct function and none feel extraneous for the apparent scope of running live shows via OBS.

    Completeness4/5

    The tool set covers show lifecycle (start/end/segment), OBS scene control, overlays, audio, effects, and health/connection diagnostics. Gaps exist: no segment rollback or scene visibility controls, and no realtime state subscription mechanism, but the core show-running operations and OBS basics are covered. The inclusion of debugging utilities (get_debug_config, reconnect_obs) is a thoughtful addition, though there's no explicit 'stop' for effects or a way to revert sources.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources