# OSCAR [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/trafalmejo/OSCAR  
**GitHub Stars:** 192  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/oscar

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

## Tools
Capabilities this server exposes over MCP:

- **status** — OSCAR's version, its ports (HTTP, the fixed OSC listening port, the socket bridge), whether editing is locked, the MIDI driver's condition, and how many projects and published interfaces there are. Start here.
- **list_projects** — Every project OSCAR holds, with its id and its title, as File > Open project or template lists them. A project is what a person edits; it reaches phones only once it is published (list_published).
- **read_project** — Every widget in one project, published or not, with its full settings as the editor holds them: addresses, ports, channels, MIDI mappings, DMX targets. Also says where the project is published, if it is. A setting nobody touched reads as its default. What phones see is the published copy, which may be older: read_published reads that one.
- **list_published** — Every published interface: its name, the project it was published from, the path it is served at, who can open it (access: "network", or "off" for one no device can open, whose schedules and bridges still run), and how many widgets it holds. Published interfaces are running -- phones and tablets may be on them, and the rig hears them.
- **read_published** — Every widget on one published interface, with its full settings as phones have them: addresses, ports, channels, MIDI mappings, DMX targets. For answering why something does or does not respond.
- **installation_map** — One picture of the whole installation: this computer's network addresses and ports, its MIDI ports and USB interfaces (a USB DMX interface among them), and everything the published interfaces talk to and listen for -- each OSC destination with the addresses sent to it, each MIDI port with its channels and controllers, each DMX output with its universe and channels -- with the control and interface behind every one. notices lists what does not add up: a MIDI port or USB interface that is not there, OSC followed while OSCAR cannot listen, two controls on the same DMX channels. It is worked out from settings and sends nothing onto the network: it says where OSCAR sends, not whether anything is there to hear it.
- **midi_ports** — The MIDI inputs and outputs this machine has right now, and the driver's condition.
- **recent_activity** — The network log's recent rows: what OSCAR's server actually received and sent, oldest first, repeats within a moment gathered into one row with a count n. Each row has what (OSC address, MIDI control, DMX universe and channels) and value (what the latest carried). Incoming rows: device (the sender's address, or the MIDI port), surfaces (published interfaces that follow it), canvas (the editor's canvas followed it); with neither, nothing follows it. Outgoing rows: to (where it went), origin (whose move: canvas, local, internet, schedule, bridge), surface (the published interface) and widget. dropped, on either, says why it was refused. The first place to look when something moves that should not, or does not move when it should.
- **describe_widgets** — Every widget OSCAR has -- tag, attributes, defaults, and each setting with its type, options and meaning -- plus how an interface is written as HTML. Read this before building one.
- **validate_draft** — Run an interface written as HTML through the widgets' own validators: unknown settings, values their panels would refuse, missing or repeated ids. Returns the complaints to correct. Nothing is saved.
- **create_draft** — Validate an interface and, if it is clean, save it as a draft: it appears in OSCAR under File > Open project or template, with a Draft badge. It is a file for a person to review: nothing is published, nothing is sent, and no project is changed. An existing draft of the same name is only replaced when overwrite is true.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

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

## Documentation

## What OSCAR MCP server does

OSCAR is presented as a visual interface builder for sending control messages to interactive installations. A project is edited in a browser-based canvas, where controls can be connected to an IP address, port, and OSC message address. The resulting interface can be opened on a phone or tablet connected to the same network as the computer running OSCAR.

The project targets systems that accept OSC, including the examples listed in the README: Modul8, MapMapper, Resolume Arena, TouchDesigner, Ableton Live, Processing, Pure Data, Unity, and Unreal Engine.

## How it works

OSCAR runs a local web server and opens the editor at `http://localhost:8080` by default. It also reports a LAN address for other devices. The browser communicates with the server through a socket connection, while OSC messages are sent from configured source ports to the selected destination.

A Button can send one value when pressed and another on release, or operate as a toggle. A Slider sends its changing value and can use an inverted range or vertical orientation. An XY Pad sends two values together or separates them into X and Y addresses. The XY Pad supports inverted axes and sends the final position when the user releases it.

The supplied repository does not describe an MCP protocol endpoint, MCP tool schema, or agent-facing operations. Therefore, the OSCAR MCP server label should not be treated as evidence that an AI client can directly create projects or send messages through MCP.

## Setup and configuration

Prebuilt installers are available for Windows, macOS, Linux, and 64-bit ARM Linux systems, including Raspberry Pi-compatible builds. Builds are not code signed, so operating systems may show a warning on first launch.

To run from source, install Node.js 18 or newer, clone the repository, run `npm install`, and start it with `npm start`. The project also provides commands for serving without rebuilding, watching changes, running tests, and launching the Electron version.

Optional environment variables configure the HTTP, socket, OSC, and DMX ports; the projects directory; browser startup; update checks; and DMX behavior when the application exits. `OSCAR_NO_OPEN=1` prevents opening a browser automatically, while `OSCAR_NO_UPDATE_CHECK=1` disables release checks.

## Tools and capabilities

The documented interface includes:

- A browser canvas for arranging controls
- Buttons with press, release, and toggle behavior
- Sliders with adjustable orientation and range direction
- XY Pads with combined or separate OSC addresses
- Project and template loading
- LAN access from phones and tablets
- Electron desktop packaging for Windows, macOS, and Linux

## Limitations and notes

The OSCAR MCP server documentation supplied here contains no MCP-specific setup, transport details, authentication model, environment variables required by an MCP runtime, or supported MCP clients. It also does not establish that an AI agent can inspect an OSC installation or draft interfaces for review. The documented workflow is manual: build the layout in the editor, configure each control, publish or run the interface, and operate it from a networked device.

OSCAR makes a daily-at-most request to GitHub to check for a newer release unless update checks are disabled.

_Full upstream README: https://allmcps.com/mcp/oscar/readme_