oscine
v2.2.0Compose and arrange music with Claude in Oscine, a browser DAW. The plugin runs a sidecar that serves the app, opens and saves project files, transcribes audio with a local whisper, and exposes the pattern side (tracks, synth params, piano-roll notes, drum steps, mixer, pattern slots, transport) as MCP tools, plus an OSC gateway for TouchOSC, Max/MSP, Pd, SuperCollider, and other controllers.
By ChazLicense: MIT0 GitHub starsUpdated 11 hours ago
Directory evidence
- Runtimes
- Claude Code
- Parsed components
- 2 skill or MCP entries
- Source updated
- Sep 23, 2026
- Manifest status
- Canonical path parsed
The directory validates manifest shape and source location. It does not execute the plugin or provide a security endorsement. Review the indexing methodology →
Install oscine for Claude Code
claude plugin marketplace add IchenDEV/agent-plugin-mkt
claude plugin marketplace update agent-plugin-marketplace
claude plugin install oscine@agent-plugin-marketplacePaste and run these commands in a terminal with Claude Code. They add and refresh the PluginsMP catalog, then install this plugin.
The installer fetches third-party code from the source repository shown on this page. This directory validates manifest structure and source location, but does not perform a security audit; review the manifest, components, and source before installing.
Get the source manually
git clone https://github.com/chazmaniandinkle/oscineClone the source repository, then follow its setup instructions to add the plugin to a compatible client. The plugin root is plugin/.
Plugin files
├── .claude-plugin/plugin.json├── skills/composing-with-oscine/SKILL.md└── .mcp.json
Included Skills1
Compose and produce music in the Oscine browser DAW through its oscine_* MCP tools. Use when the user asks to compose music, make a beat, write a melody, bassline, chords or drums, design a synth sound, mix tracks, open or save an Oscine project, or control Oscine playback ("make a beat", "write a bassline", "open oscine", "make the pad warmer").
MCP servers1
- command
- node
- args
- ${CLAUDE_PLUGIN_ROOT}/server/oscine-mcp.mjs
- env.OSCINE_ALLOWED_ORIGINS
- https://chazmaniandinkle.github.io
MCP configuration uses runtime-provided plugin path placeholders such as ${PLUGIN_ROOT} or ${CLAUDE_PLUGIN_ROOT}. Review the manifest for the runtime-specific expansion rules.
Plugin manifests1
{
"name": "oscine",
"version": "2.2.0",
"description": "Compose and arrange music with Claude in Oscine, a browser DAW. The plugin runs a sidecar that serves the app, opens and saves project files, transcribes audio with a local whisper, and exposes the pattern side (tracks, synth params, piano-roll notes, drum steps, mixer, pattern slots, transport) as MCP tools, plus an OSC gateway for TouchOSC, Max/MSP, Pd, SuperCollider, and other controllers.",
"author": {
"name": "Chaz"
},
"keywords": [
"music",
"synth",
"daw",
"sequencer",
"composition",
"web-audio"
],
"license": "MIT"
}For maintainers
If you maintain this plugin, link to this source-backed listing from your README so users can review its manifest and indexed components.
[oscine on Agent Plugins Marketplace](https://pluginsmp.com/plugins/oscine)