Skip to main content
Glama
KshamayBharadwaj

OBS MCP

by KshamayBharadwaj
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OBS MCP

No user-submitted related servers found.

    Related Servers

    • obs-control-mcp

      rjla-developer
      A
      license
      A
      quality
      C
      maintenance
      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

    • 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
      296 npm
      3
      GPL 2.0

    • obs-mcp

      LHenri88
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables an LLM agent to control a local OBS Studio instance via obs-websocket, launching it, arranging scenes and sources, and starting or stopping recordings so it can capture its own screen as raw footage without manual intervention.
      1
      MIT

    • dcc-mcp-obs

      dcc-mcp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables typed, native control of OBS Studio—scene/source discovery and recording start/stop/pause/resume with status readbacks—through a secure loopback WebSocket interface.
      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.2/5.0

    Scored across 89 tools

    Disambiguation4/5

    Tools are generally well-separated by resource and action, but some overlap exists (e.g., get_obs_stats vs get_obs_status vs diagnose_obs; start_recording vs start_recording_session). Descriptions help clarify these boundaries, making accidental misselection unlikely.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (get_, set_, create_, delete_, start_, stop_, etc.). Minor exceptions like 'media_control' and 'obs_help' invert the pattern, but the overall style is uniform.

    Tool Count2/5

    With 89 tools, the server is extremely large. While OBS has many features, the sheer number of tools is excessive, and some could be consolidated (e.g., diagnostic tools could use a single parameterized endpoint). This is well beyond the 25+ threshold for 'too many'.

    Completeness5/5

    The tool surface covers virtually every major OBS domain: scenes, sources, audio, video, media, filters, transitions, studio mode, profiles, collections, recording, streaming, replay buffer, hotkeys, and diagnostics. It even includes higher-level session workflows, leaving no obvious gaps for typical automation.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources