Back to MCP directory
publicPublicdnsLocal runtime

obs-mcp

一台通过OBS WebSocket协议提供远程控制OBS Studio工具的服务器,可以通过MCP客户端界面管理场景、源、流媒体和录制。

article

README

OBS MCP Server

An MCP server for OBS Studio that provides tools to control OBS via the OBS WebSocket protocol.

Features

  • Connect to OBS WebSocket server
  • Control OBS via MCP tools
  • Provides tools for:
    • General operations
    • Scene management
    • Source control
    • Scene item manipulation
    • Streaming and recording
    • Transitions

Installation

npm install
npm run build

Usage

  1. Make sure OBS Studio is running with WebSocket server enabled (Tools > WebSocket Server Settings). Note the password for the WS.
  2. Set the WebSocket password in environment variable (if needed):
export OBS_WEBSOCKET_PASSWORD="your_password_here"
  1. Run the OBS MCP server to see that it is able to build and connect:
npm run build
npm run start
  1. Provision you Claude desktop with the MCP server settings:
{
  "mcpServers": {
    "obs": {
      "command": "node",
      "args": [
        "<obs-mcp_root>/build/index.js"
      ],
      "env": {
        "OBS_WEBSOCKET_PASSWORD": "<password_from_obs>"
      }
    }
  }
}
  1. Use Claude to control your OBS!

Available Tools

The server provides tools organized by category:

  • General tools: Version info, stats, hotkeys, studio mode
  • Scene tools: List scenes, switch scenes, create/remove scenes
  • Source tools: Manage sources, settings, audio levels, mute/unmute
  • Scene item tools: Manage items in scenes (position, visibility, etc.)
  • Streaming tools: Start/stop streaming, recording, virtual camera
  • Transition tools: Set transitions, durations, trigger transitions

Environment Variables

  • OBS_WEBSOCKET_URL: WebSocket URL (default: ws://localhost:4455)
  • OBS_WEBSOCKET_PASSWORD: Password for authenticating with OBS WebSocket (if required)

Requirements

  • Node.js 16+
  • OBS Studio 31+ with WebSocket server enabled
  • Claude desktop

License

See the LICENSE file for details.

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client