audio-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDIO_MCP_OUTPUT_DIR | No | Override the output directory for generated audio files | .audio-mcp/ |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_musicB | Generate a mock music WAV from a text prompt. |
| generate_sound_effectB | Generate a mock sound-effect WAV from a text prompt. |
| get_generation_statusA | Return the state and asset metadata for a generation. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: generating music, generating sound effects, and checking generation status. The two generation tools are clearly separated by output type, and the status tool is orthogonal to the generation actions.
All tool names follow a consistent verb_noun pattern using snake_case: generate_music, generate_sound_effect, and get_generation_status. The naming is uniform and predictable.
Three tools is on the lean side but appropriate for a focused mock audio generation service. The set covers the essential operations without superfluous additions.
The tools cover the core workflow of starting a generation and checking its status. Minor gaps like canceling or listing generations exist but are not critical for a mock service.