obs_websocket_workspace

Fast, reliable microphone and desktop audio control via the OBS MCP server. Use for short, imperative commands like "mute my mic", "unmute me", "mute game audio", "kill desktop audio", "silence everything except my mic", or "turn down the music to -12 dB". Encodes mute/unmute and volume workflows for live production.

Apply preset transforms (wide, close-up, corner placements, zoomed) to a visual source in OBS via the OBS MCP server. Use for short, imperative commands like "zoom in on me", "move my camera top-right", "go wide", "reset camera framing", or "put my cam bottom-left". Encodes named transform presets and uses server-side animation for smooth moves.

Optimize OBS scene switching using the OBS MCP server. Use for short, imperative commands like "switch to product placement scene", "go to intro scene", "show main camera", or "switch back to gameplay". Encodes a cached scene map workflow for low-latency scene changes. Prefer direct tool calls over long reasoning.

Bootstrap a structured OBS state snapshot — current/preview program scene, all scenes, scene items with their flat transforms, audio inputs, special-input slots, canvas dimensions, and studio-mode flag — in one batch so other obs-* skills can reuse it without redundant API calls. Use at the start of any OBS-control session, or whenever a stale cache is suspected (e.g., the user reports "no visible change", switches scenes mid-session, or mentions a scene/source name that doesn't match the cache).

Control a running OBS Studio instance through the OBS MCP server. Use when the user asks to connect to OBS, list or switch scenes, inspect or transform sources, control audio inputs, start/stop streaming or recording, trigger hotkeys, manage filters or transitions, or run any OBS WebSocket operation. Exposes 60+ tools via an `execute` + JavaScript invocation pattern.

Toggle visibility of OBS sources (overlays, webcams, lower thirds, BRB text, alerts) via the OBS MCP server. Use for short, imperative commands like "show my webcam", "hide the lower third", "bring up the BRB text", "turn off my camera", or "show the chat overlay". Encodes semantic-name → source-name mapping with a per-scene visibility cache.

Save instant replay clips from the OBS replay buffer via the OBS MCP server. Use for short, imperative commands like "clip that", "save the last 30 seconds", "save that last moment", "start the replay buffer", or "where did that clip save?". Optimized for fast, hotkey-style clipping during gaming or live content.

Schedule OBS recording or streaming starts/stops via the OBS MCP server. Use for commands like "record for 45 minutes then stop", "start recording at 9:00 and stop at 10:15", "stop the stream in 30 minutes", or "record this lecture for an hour". Handles the wait via obs_client_sleep so the JS sandbox stays idle.

Control OBS transitions and Studio Mode via the OBS MCP server. Use for short, imperative commands like "cut to preview", "fade to the next scene", "roll the stinger", "enable studio mode", "set transition duration to 500 ms", or "switch to fade transition". Optimized for live production switching.

Control OBS streaming, recording, and virtual camera transport via the OBS MCP server. Use for short, imperative commands like "go live", "start the stream", "end the stream after this segment", "start recording", "pause the recording", "stop recording", "turn on virtual camera", or "kill the virtual cam". Optimized for low-latency, hotkey-style transport control.

Control a running OBS Studio instance through the obs-mcp-stdio MCP server. Use when the user asks to connect to OBS, list or switch scenes, inspect or transform sources, control audio inputs, start/stop streaming or recording, trigger hotkeys, manage filters or transitions, or run any OBS WebSocket operation. Exposes 60+ tools via an `execute` + JavaScript invocation pattern.

Add new OBS WebSocket requests to the obs_websocket package following protocol specification. Handles enum creation, response models, request methods, exports, tests, and README updates. Use when adding new OBS WebSocket protocol requests, implementing protocol methods, or extending the obs_websocket package functionality.

Add easy_api annotations (@Server, @Tool, @Parameter) to existing Dart code to expose methods as MCP tools or REST API endpoints. Use when converting Dart libraries to MCP/REST servers, adding tool exposure to existing functions, or when the user wants to make their Dart code callable via the Model Context Protocol or HTTP APIs.