Documentation

Explore Maru's instruments, plugins, racks, agent-led Studio, Engine, PluginUI, music-theory computation, learning tools and research.

Connect Maru to Claude, ChatGPT, Claude Code, Codex, Cursor or VS Code, with or without a terminal: talk through your projects, learn from the guides and the community, start projects and generate sounds.

Install the maru CLI, create a module, shape it with an agent, and hear it in the workbench.

Turn a musical brief into a working audio tool without becoming a plugin-framework specialist.

Five ideas behind Maru: the module is the product, sound and interface are separate, one source reaches several targets, generation runs beside the audio, and your agent uses the same tools you do.

The few project areas you change and the output the toolkit generates.

Audition a module, map pedal controls, build and emulate, then qualify the exact artifact on a board.

Load a built VST3 in a plugin host and check its audio, controls, MIDI, and state.

Bring Maru into your agent's workflow to create instruments, effects, musical tools and sound collections.

What the platform gives a developer to build on, with the package entry point, guide and a public module for each: 60 named effects, modules, DSP, UI kit, generation, musical data, hosting, plug-in builds, licensing and agent operations.

Start from 60 named effects and a library of working instruments, recompose them in Studio, with your assistant or in code, and write custom DSP only when you need something new.

Technical overview of hosted generation: task types, durable jobs, the module face capability, server and standalone app integrations, consent and metering, and how results reach an instrument.

Technical setup for distributing what you build: plug-in license activation in release builds, the face license prop, testers and status, sampler bank access, and publishing commands.

Technical entry points for integrating Maru into a DAW, web app, online service, controller, device or agent product: embedding, generation, sign-in, operations API, plug-in builds and their boundaries.

Create with an agent, edit live, save a revision and prepare a supported release.

Create keyboard instruments and drum kits in Studio, then export their sounds and mappings as MAS or ZIP banks.

Write chords, keys, drums and seeded generators as code in the Code Sequencer, and build songs from the layers of other songs.

Check package availability and use Symbolic's JavaScript and TypeScript functions for notes, chords and rhythm.

Build a flexible module face with host-bound controls, portable dependencies, and the UI kit.

Embed a compiled module and its face with a headless React provider, parameter hooks and audio handles.

Reusable, prepared audio building blocks for filters, effects, synthesis, and analysis.

The typed boundary shared by module graphs, browser audio, and native hosts.

The shared contracts every surface agrees on: parameter descriptors and their normalization, timed events, and the module face props.

Sell a native plug-in with Maru activation in one command: seats, trials, offline grace, refunds, tester copies and the dry-through gate, with no licensing code in your module.

Render chords, MIDI takes and free improvisations as audio with the experimental Accompanist module.

Run a small Node audio generator with a Maru account token or a configured inference service.

Use Maru's AI toolkit to turn prompts into audio, follow generation jobs and add a Generate action to your app or instrument.

Run Maru builds in GitHub Actions, retain the output and publish a trusted release to your Maru profile.

The few rules Maru's architecture depends on, for developers coming from JUCE or another framework, with links to the guides that own the details.

Choose an authoring workflow around your product, existing tools and delivery needs.

How the Engine connects one portable module to a Linux pedal service or microcontroller firmware.

How to make a small number of physical controls useful across modules with many parameters.

Experimental board and FM-1 targets, consumer multi-effects research, delivery paths and physical qualification limits.

How layered testing keeps audio dependable across browsers, native builds, plugin hosts, and hardware.

Prepare a module, presets and assets for a versioned release.

Ownership and commercial terms during the private beta.

Choose platform runners, validate VST3, Audio Unit and CLAP builds, prepare installers and downloads, and understand hardware delivery limits.

The default licence for new modules: remix on Maru, credit kept by the lineage, your music stays yours.

Install the maru command, find its command groups, and use it from a terminal, a script, CI or a coding agent.

Sign the maru CLI in to your Maru account with maru login, check it with maru whoami, and use tokens in CI.

Create a runnable effect or instrument project with maru init or npm create maru, then open it in the workbench.

Live audio, MIDI, hot reload, diagnostics, and agent-assisted iteration with maru dev.

Validate, evaluate, preview, build, export and prepare a release of a module with the maru module commands.

Build, verify, inspect, install and remove AU, VST3, CLAP and AAX plugins with the maru plugin commands.

The agent skill, the CLI, the local MCP server and the hosted MCP connector: what each one is for, which you need, the install commands and how they work together.

Install the Maru agent skill, register Maru's MCP servers with your coding agents, serve the local operations over MCP, and let an agent discover guides and schemas from the CLI.

Add the Maru MCP server to Claude, ChatGPT, Claude Code, Codex, Cursor or VS Code: one command for coding agents, setup steps for each client, what you approve, personal tokens, testing, disconnecting and troubleshooting.

Prompts to try with the Maru MCP server: review a project, answer from the guides, learn from community modules, check a plug-in build and start a new project.

Every tool the Maru MCP server offers, what it does and the permission it needs, plus the machine-readable catalog.