Name: Decent Sampler Drums
Author: dandeliongold

LABSCO SUMMARY

Sample checks first, then the XML — which is the order that stops a preset failing in the plugin.

The validation is what makes this more than a code generator: non-standard WAV headers and metadata that disagrees between mic positions are exactly the things that break a multi-mic kit after the preset is written, and they get caught before the XML exists. The multi-mic routing tool goes further than most hand-written presets bother to — a volume control and its own auxiliary output per mic position, mapped to MIDI CC. Keep the first kit simple; large presets can outgrow the message limit of the client generating them.

What it is

A preset generator for the free Decent Sampler plugin. It checks the WAV files first, then produces the XML for the groups, controls and routing a drum kit needs.

What you get

WAV files checked before you build anything: non-standard headers, metadata inconsistencies across a multi-mic set, sample rate and bit depth compatibility, channel configuration and file format
The groups XML generated for the kit, in either a basic form — sample mapping and optional velocity layers, no UI or routing — or a fuller one for presets that need more
Per-drum pitch controls with the range you set, and ADSR envelope settings for natural decay
Round robin playback configured across a set of samples, with sequence positions validated and the sample files confirmed to exist
Multi-mic routing: a volume control per mic position — close, overheads left and right, room left and right — each routed to its own auxiliary output for mixing in a DAW, with MIDI CC mappings and duplicate assignments caught

Requirements

No account and no key — it reads your sample files and writes XML. Node.js v14 or higher; run it with npx -y @dandeliongold/mcp-decent-sampler-drums over stdio, from the npm package @dandeliongold/mcp-decent-sampler-drums, currently 0.1.5. Sample paths must be absolute. Two prompts ship with it, simple_preset_guidelines and advanced_preset_guidelines, and both ask for the absolute path to your samples directory so the examples use your own paths. One limit to know before starting a big kit: a complex preset with many mics and variations can produce XML that exceeds Claude Desktop's maximum message length, so simple presets are the reliable case today. Playing the result back needs the Decent Sampler plugin, which is free.

Setup effort

One command — npx -y @dandeliongold/mcp-decent-sampler-drums

See installation options

USE CASES

01

Turning a folder of recordings into a playable kit

Check the WAV files for problems first, then generate the groups XML from the sample mapping.

analyze_wav_samplesgenerate_drum_groups

02

Making repeated hits sound less machine-like

Configure round robin across the variations — positions are validated and missing files are caught.

configure_round_robin

03

Getting a kit that mixes properly in a DAW

Route each mic position to its own auxiliary output with a MIDI-mapped volume control.

configure_mic_routing

04

Tuning how each drum rings out

Set the ADSR envelope per drum, and give each one a pitch range you can play with.

configure_drum_controls

05

Diagnosing a kit that will not load correctly

Run the sample analysis over the paths — header, rate, bit depth and channel problems come back named.

analyze_wav_samples

5 tools

Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.

`analyze_wav_samples`

Analyze WAV files to detect common issues in drum kit samples.

This tool checks for:

Non-standard WAV headers that may cause playback issues
Metadata inconsistencies that could affect multi-mic setups
Sample rate and bit depth compatibility
Channel configuration issues
File size and format validation

Error Handling:

Reports detailed header format issues
Identifies metadata inconsistencies between related samples
Flags potential playback compatibility problems
Returns specific error messages for each issue type

Success Response: Returns detailed analysis including:

WAV header information
Sample metadata
Potential compatibility issues
Recommendations for fixes

IMPORTANT: Always use absolute paths (e.g., 'C:/Users/username/Documents/Samples/kick.wav') rather than relative paths.

`generate_drum_groups`

Generate DecentSampler <groups> XML for drum kits.

This tool supports two configuration types:

BasicDrumKitConfig:

For simple presets with minimal features
No UI controls, effects, or routing
Only supports basic sample mapping and optional velocity layers
Recommended for straightforward drum kits

AdvancedDrumKitConfig:

For complex setups combining multiple features
Supports UI controls, effects, and routing
Integrates with other tools (configure_drum_controls, configure_mic_routing, etc.)
Use when you need advanced features like round robin or multi-mic setups

Best Practices:

IMPORTANT: Always use absolute paths (e.g., 'C:/Users/username/Documents/Samples/kick.wav')
Group all samples for a drum piece into a single group
When using multiple mic positions, include them all in the same group
Use velocity layers within a group to control dynamics

Error Handling:

Validates all sample paths exist
Checks for valid MIDI note numbers
Ensures velocity layers don't overlap
Verifies muting group configurations
Returns specific errors for any invalid settings

Example Configurations:

Basic Configuration (simple drum kit):

{ "globalSettings": { "velocityLayers": [ { "low": 1, "high": 42, "name": "soft" }, { "low": 43, "high": 85, "name": "medium" }, { "low": 86, "high": 127, "name": "hard" } ] }, "drumPieces": [{ "name": "Kick", "rootNote": 36, "samples": [ {"path": "C:/Samples/Kick_Soft.wav"}, {"path": "C:/Samples/Kick_Medium.wav"}, {"path": "C:/Samples/Kick_Hard.wav"} ] }] }

Advanced Configuration (multi-mic kit with controls):

{ "globalSettings": { "velocityLayers": [ { "low": 1, "high": 127, "name": "full" } ], "drumControls": { "kick": { "pitch": { "default": 0, "min": -12, "max": 12 }, "envelope": { "attack": 0.001, "decay": 0.5, "sustain": 0, "release": 0.1 } } }, "micBuses": [ { "name": "Close Mic", "outputTarget": "MAIN_OUTPUT", "volume": { "default": 0, "midiCC": 20 } } ] }, "drumPieces": [{ "name": "Kick", "rootNote": 36, "samples": [ { "path": "C:/Samples/Kick_Close.wav", "micConfig": { "position": "close", "busIndex": 0 } } ], "muting": { "tags": ["kick"], "silencedByTags": [] } }] }

Success Response: Returns complete XML structure with:

Organized sample groups
Velocity layer mappings
Muting group configurations
All sample references and settings
Advanced features when using AdvancedDrumKitConfig

BEFORE YOU INSTALL

What to know first

Tools you get

5 tools when we connected. simple_preset_guidelines and advanced_preset_guidelines are prompts, not tools; sessions start from them, but they will not appear in a tool list.

Requires

Node.js (v14 or higher)
npm (usually comes with Node.js)
Claude Desktop app (for use with Claude)

Where it runs

The documented client runs the server on your machine.

CONTEXT COST

Light Standing cost

Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are

INSTALLATION

Connect your client

Server setup

TERMINAL

npx -y @dandeliongold/mcp-decent-sampler-drums

MCP Clients

Claude Desktop

CLAUDE DESKTOP · JSON

{
  "mcpServers": {
    "decent-sampler-drums": {
      "command": "npx",
      "args": [
        "-y",
        "@dandeliongold/mcp-decent-sampler-drums"
      ],
      "env": {}
    }
  }
}

Decent Sampler Drums

Sample checks first, then the XML — which is the order that stops a preset failing in the plugin.

What it is

What you get

Requirements

Setup effort

Turning a folder of recordings into a playable kit

Making repeated hits sound less machine-like

Getting a kit that mixes properly in a DAW

Tuning how each drum rings out

Diagnosing a kit that will not load correctly

5 tools

`analyze_wav_samples`

`configure_drum_controls`

`configure_mic_routing`

`configure_round_robin`

`generate_drum_groups`

What to know first

Tools you get

Requires

Where it runs

Light Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop

Decent Sampler Drums

Sample checks first, then the XML — which is the order that stops a preset failing in the plugin.

What it is

What you get

Requirements

Setup effort

Turning a folder of recordings into a playable kit

Making repeated hits sound less machine-like

Getting a kit that mixes properly in a DAW

Tuning how each drum rings out

Diagnosing a kit that will not load correctly

5 tools

analyze_wav_samples

configure_drum_controls

configure_mic_routing

configure_round_robin

generate_drum_groups

What to know first

Tools you get

Requires

Where it runs

Light Standing cost

Connect your client

Server setup

MCP Clients

Claude Desktop

Same category

AbletonMCP

Ableton Live MCP

Mureka

AudacityMCP

`analyze_wav_samples`

`configure_drum_controls`

`configure_mic_routing`

`configure_round_robin`

`generate_drum_groups`