Connect OBS scenes, sources, audio and recording through its official WebSocket API or community MCP bridges. For Cursor, 1 route is explicitly documented by the integration maintainer.
The official remote-control API, usable by a custom script or agent bridge.
Platforms: Windows, macOS, Linux
A custom client script or bridge is required; agent-specific setup is not listed.
OBS with WebSocket enabled, authenticated connection, and a separate client script or bridge.
This is a WebSocket API. Connecting an AI agent requires a client script or an additional MCP bridge.
A Node.js MCP bridge maps OBS WebSocket operations to agent-callable tools.
Platforms: See documentation
MCP transport compatibility is inferred; this agent is not explicitly documented for this connection.
OBS Studio with WebSocket enabled and the Node.js bridge configured with connection credentials.
Requires a reachable OBS WebSocket server; it does not replace OBS or configure streaming service accounts.
A Python MCP server connects scene, source, audio and output controls to OBS WebSocket.
Platforms: Windows, macOS, Linux
The maintainer documents Cursor setup for this connection.
Python 3.10+ and OBS Studio 28+ with WebSocket v5 enabled and connection settings configured.
The WebSocket connection must be active. Output availability depends on the OBS configuration and installed sources.
| Integration | Cursor compatibility | Requirements |
|---|---|---|
| OBS WebSocket API | Not documented | OBS with WebSocket enabled, authenticated connection, and a separate client script or bridge. |
| OBS MCP · Node bridge | MCP compatibility (inferred) Setup guide | OBS Studio with WebSocket enabled and the Node.js bridge configured with connection credentials. |
| OBS MCP · Python bridge | Documented setup Setup guide | Python 3.10+ and OBS Studio 28+ with WebSocket v5 enabled and connection settings configured. |
The sources establish the capabilities listed above, not complete application coverage. Check each bridge’s limitations and your application version before starting.
Choose a route that explicitly documents Cursor and matches your environment. Start with the maintainer’s setup guide and a disposable project copy. Shared MCP support alone is listed as an inference.
All OBS Studio integrations