OSCAR

io.github.trafalmejov1.0.2Updated Oct 5, 2026

An assistant reads your OSCAR installation (OSC, MIDI, DMX) and drafts interfaces you review.

VerifiedSTDIODesktop onlyDeveloper ToolsMedia & Design

Overview

AI-generated overview

Lets an assistant inspect a local OSCAR control-interface installation and draft new OSCAR interfaces for review.

What it does
Connects an assistant to OSCAR, a free open-source editor and server for control interfaces made of buttons, sliders and other widgets that phones and tablets open and that send OSC, MIDI and DMX. The assistant can read the running installation: projects, what is published, each widget's settings, MIDI ports, and recent OSCAR traffic, which helps diagnose why a control does not respond. It can also draft an interface, which OSCAR's validators check and which then appears under File > Open project or template with a Draft badge for the user to open, check and publish.
When to use it
Useful when you build or troubleshoot OSCAR control interfaces for show software, instruments or lighting and want an assistant to inspect the live setup or generate a starting layout. It is meant for local desktop use alongside a running OSCAR instance.
Requirements
OSCAR 2.1 or later must be running on the same computer with the MCP pill in its top bar green. The server runs locally over stdio via npx and needs Node 18 or later; the Claude Desktop bundle uses Claude's own runtime. It locates OSCAR through the file ~/.oscar/mcp.json, which holds OSCAR's local address and a token that changes at every start. No accounts, API keys or environment variables are declared.
Before you install
The server reads local OSCAR state and passes requests only to OSCAR on the same computer. It states that it never sends anything to your rig, publishes, or changes a project; drafts still require the user to open, check and publish them. The token in ~/.oscar/mcp.json changes each start, and switching the MCP pill off in OSCAR closes access.

Installation

In SourceWeft

  1. Open OSCAR in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

createwithoscar

Connects an AI assistant to OSCAR, the free, open-source editor and server for control interfaces: pages of buttons, sliders and other controls that phones and tablets open, and that send OSC, MIDI and DMX to show software, instruments and lights.

With it, an assistant such as Claude can:

  • Find out why something does not respond. It reads the OSCAR running on your computer: its projects, what is published, every widget's settings, the MIDI ports, and what OSCAR lately received and sent.
  • Draft an interface for you. It writes one, OSCAR's own validators check it, and it appears in OSCAR under File > Open project or template with a Draft badge, for you to open, check and publish yourself.

It never sends anything to your rig, publishes, or changes a project.

Connect

OSCAR 2.1 or later must be running on the same computer, with the MCP pill in its top bar green.

Claude Code

claude mcp add oscar -- npx -y createwithoscar

Claude Desktop: download OSCAR.mcpb from createwithoscar.site and double-click it. Nothing else to install.

Cursor, VS Code, Windsurf, Codex, Gemini CLI and other MCP apps: add a server with the command npx and the arguments -y createwithoscar. In most apps that is:

json
{  "mcpServers": {    "oscar": { "command": "npx", "args": ["-y", "createwithoscar"] }  }}

If it does not start on Windows, use the command cmd with the arguments /c npx -y createwithoscar.

Then ask, for example:

  • "Build me an OSCAR interface with four faders and a blackout button for my lighting desk."
  • "My OSCAR slider is not moving the light. Can you see why?"

How it works

This is a small program with no dependencies. The assistant starts it and speaks MCP to it; it passes each request to OSCAR on this computer and nowhere else. It finds OSCAR through a file OSCAR writes when it starts (~/.oscar/mcp.json), which holds OSCAR's local address and a token that changes at every start. Switching the MCP pill off in OSCAR closes the door.

If OSCAR is not running, the assistant still sees the tools, and is told to ask you to start OSCAR.

Needs Node 18 or later (the Claude Desktop bundle uses Claude's own).

Licence

BSD-3-Clause, as OSCAR is. Source: github.com/trafalmejo/OSCAR.

Source: createwithoscar/README.md at commit 5caee38

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.2LatestOct 5, 2026