Skip to main content
Glama
jwang47

Space Dust MCP

by jwang47
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_presetsA

List the presets installed in the user's Space Dust preset folder.

read_presetA

Show how a preset is set up, grouped by section.

Only settings that differ from the synth's defaults are listed, which is what makes
the sound what it is. Set include_defaults to see every parameter.
list_parametersA

Look up Space Dust parameters, their ranges and defaults.

Pass a word to filter — a section name like "filter" or "reverb", or part of a parameter name. With no query this returns every parameter, grouped by section.

create_presetA

Create a new preset and save it to the user's preset folder.

changes maps parameter ids to values written the way the plugin shows them —
{"filterCutoff": "260", "osc1Waveform": "Saw", "subOscOn": "on"}.

based_on is the preset to start from; "Init" starts from the synth's default state.
Starting from an existing preset the user likes is usually the better move.

Refuses to overwrite an existing preset — pick another name, or use adjust_preset.
adjust_presetA

Change settings in an existing preset, in place.

changes maps parameter ids to values written the way the plugin shows them —
{"filterCutoff": "180", "softClipperDrive": "0.6"}.

The previous version is saved first, so undo_preset can always take it back. Use
note to record what the user asked for ("darker, more low end").
read_current_soundA

Show what Space Dust is playing right now, without the user naming a preset.

Use this whenever they say "this sound", "what I'm hearing", "the current patch".

adjust_current_soundA

Change the sound the user is playing right now, and hear it within a second.

Use this for "make this darker", "less muddy", "more bite" — anything about the sound in front of them rather than a preset by name. Writes to the preset Space Dust currently has loaded; the plugin picks the change up on its own, so the user doesn't have to touch the preset menu.

Needs a preset to be selected in the plugin. If they're on an unsaved sound, ask them to save it as a preset first.

undo_presetB

Take a preset back to how it was before the last change.

preset_historyB

List the saved earlier versions of a preset, newest last.

compare_presetsA

Show every setting that differs between two presets.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing vs reading presets, adjusting named presets vs the current sound, and separate tools for undo, history, and comparison. The descriptions explicitly disambiguate potentially similar pairs like adjust_preset and adjust_current_sound.

Naming Consistency5/5

All tool names follow a consistent verb_noun snake_case pattern (e.g., list_presets, read_preset, adjust_current_sound). Verbs are semantically appropriate (list, read, create, adjust, undo, compare), and no mixed naming conventions are present.

Tool Count5/5

At 10 tools, the set is well-scoped for a synth preset management server. Each tool covers a distinct capability without redundancy, and the count feels neither sparse nor bloated.

Completeness4/5

The core lifecycle of preset management is covered: list, read, create, adjust, undo, history, and compare. However, a delete operation is missing, and saving the current sound as a new preset would require a workaround, leaving minor gaps.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources