audiomade
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDIOMADE_API_KEY | Yes | Your AudioMade API key, created from the AudioMade MCP setup screen. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_candidate_audioA | Load existing audio previews directly into the picker. Does not generate, select or install audio. |
| get_audio_capabilitiesA | Describe AudioMade's generate, audition, select and install workflow without using generation credits. |
| generate_sound_candidatesA | Start one real asynchronous AudioMade generation with exactly four candidates. Continue implementation while it renders, then call get_sound_candidates. |
| get_sound_candidatesA | Retrieve four real playable candidates for a started generation. Present them as 1, 2, 3 and 4, then wait for the user's numbered reply. |
| select_sound_candidateB | Record the user's explicit 1, 2, 3 or 4 reply. This does not install a file. |
| install_sound_candidateA | Install the explicitly selected AudioMade candidate into a Unity, Godot, Defold or generic project. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| candidate-picker |
TDQS
Scored across 6 tools
Most tools have clear boundaries, but get_candidate_audio and get_sound_candidates both relate to retrieving playable audio, requiring careful reading to distinguish existing previews from generated candidates. The remaining tools are unambiguous in their roles.
The verb_noun pattern is mostly consistent, but the nouns mix 'audio' and 'sound' (get_candidate_audio vs. get_sound_candidates), and 'candidate' appears as both singular and plural. This creates minor naming friction.
Six tools are well-scoped for the generate-audition-select-install workflow. Each tool maps to a clear step without redundancy or bloat.
The full generation-to-install lifecycle is covered, including loading existing previews. Minor gaps like a cancellation or status-check tool are absent, but the core workflow is complete enough for agent success.