Skip to main content

dcc-mcp-obs

Native, typed OBS Studio control for the DCC-MCP ecosystem.

This product is an OBS plugin plus a DCC-MCP sidecar. The C++ plugin runs inside the exact OBS process, owns host lifecycle and UI-thread dispatch, and registers bounded vendor requests through the official OBS WebSocket 5.x API. The Python sidecar exposes those contracts through MCP, the Gateway, an Install SOP v1 CLI, and a bundled Agent skill.

OBS WebSocket is the authenticated transport. It is not used as an unrestricted request escape hatch, and this product exposes no arbitrary script or raw WebSocket tool.

First slice

  • Exact native plugin, OBS version, PID, instance ID, readiness, and event sequence
  • Bounded scene discovery and current-scene readback
  • Bounded source discovery for the current or an exact named scene
  • Recording status
  • Start, stop, pause, and resume recording
  • A separate typed status readback after every mutation
  • Stable redacted errors, bounded UI dispatch, and exact-instance drift rejection

The machine-readable capability matrix tracks the remaining product domains. They are intentionally not represented as shipped tools until their typed contracts land.

Full-control roadmap

Requirements

  • OBS Studio 28 or newer with OBS WebSocket 5.x enabled
  • Python 3.10 or newer
  • dcc-mcp-core>=0.20.14,<1.0.0
  • The matching native plugin package for Windows, macOS, or Linux

Install

Install the Python control plane, then install a release-native plugin bundle whose SHA-256 digest you obtained from the same release:

python -m pip install dcc-mcp-obs
dcc-mcp-obs-install install \
  --plugin-archive dcc-mcp-obs-plugin.zip \
  --sha256 <release-sha256>
dcc-mcp-obs-install verify

The installer emits one Install SOP v1 JSON object. --dry-run performs bundle and ownership preflight without changing the OBS plugin directory. See installation details.

On POSIX systems, a successful filesystem result is a synchronous point-in-time verification, not a persistent namespace or writer lock. The report publishes POSIX_REVERIFY_BEFORE_USE in next_steps; re-run status or verify immediately before relying on the files.

Password and endpoint

Configure the OBS WebSocket password in the operator-owned environment:

set DCC_MCP_OBS_WEBSOCKET_PASSWORD=your-password

The first release accepts only ws://127.0.0.1:<port> and defaults to port 4455. A password is never returned in tool results, receipts, public errors, or logs. Use DCC_MCP_OBS_WEBSOCKET_URL only to select another loopback port.

Run the sidecar against one exact OBS process:

dcc-mcp-obs --host-pid <obs-pid>

Agent discovery

The bundled obs-control skill includes English and Chinese discovery aliases for OBS, Open Broadcaster Software, recording, scene/source inspection, pause, resume, 录屏, and 录制视频. Agents search and load the skill before calling the exact eight tools in this first slice. Streaming and scene switching remain roadmap capabilities, not shipped native controls.

OBS control is native-plugin/WebSocket first. Unsupported visual-only actions may use DCC-MCP ui-control with project-owned DCC-CUA only after exact PID and HWND binding, a fresh snapshot, and post-action readback. There is no generic Computer Use fallback.

Development

python -m pip install -e ".[dev]"
python -m pytest
python -m ruff check .
python -m ruff format --check .
dcc-mcp-cli lint src/dcc_mcp_obs/skills/obs-control --warnings-as-errors

The native build uses the official OBS plugin template toolchain and OBS 31.1.1 SDK inputs pinned with SHA-256 hashes:

cmake --preset windows-x64
cmake --build --preset windows-ci-x64

Equivalent CI builds run on Windows, macOS, and Linux.

Validation boundary

Unit tests, fake protocol sessions, native compilation, package smoke tests, and CI do not prove a licensed/live OBS host. This initial delivery makes no real-OBS acceptance claim. A disposable live-host acceptance issue remains a separate release gate.

License

GPL-2.0-or-later. The native module links to OBS Studio and vendors the official OBS WebSocket plugin API header with its original notice.

Metadata

Release files for dcc-mcp-obs 1.0.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for dcc-mcp-obs 1.0.0
File Size Uploaded Provenance Actions
dcc_mcp_obs-1.0.0.tar.gz 74.7 kB With provenance Details for dcc_mcp_obs-1.0.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for dcc-mcp-obs 1.0.0
File Interpreter ABI Platform Actions
dcc_mcp_obs-1.0.0-py3-none-any.whl Python 3 none any Details for dcc_mcp_obs-1.0.0-py3-none-any.whl

Total release size: 115.7 kB

Release files / dcc_mcp_obs-1.0.0.tar.gz

Download URL dcc_mcp_obs-1.0.0.tar.gz
Size 74.7 kB
Tags Source
SHA-256 checksum
How to use checksums
5249abe6d2e93cb8fafffaf4ffdbbde4df5c27a132a6cec5ecc24f3748e0e5a7
BLAKE2b-256 checksum
How to use checksums
c7fcc6c9d4e473ab5b9c8f6feba97633de51991548713a0215cd73fb1c9c23d7
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.

Transparency log

Release files / dcc_mcp_obs-1.0.0-py3-none-any.whl

Download URL dcc_mcp_obs-1.0.0-py3-none-any.whl
Size 40.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
e70a0217d0f6642cc69a05b2a74480af4d28fb41b3bad133b4aaedce355af0a3
BLAKE2b-256 checksum
How to use checksums
2ea17f597aa2ba1b08c2bdcb5f17d8829b735f4c3c3fe72e5a6cb303572f1115
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.

Transparency log

Security for dcc-mcp-obs 1.0.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

Full provenance

All 2 files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for dcc_mcp_obs-1.0.0.tar.gz

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 29, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page