MCP Audio Tweaker
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FFMPEG_PATH | No | Custom FFmpeg binary path (optional) | |
| AUDIO_TWEAKER_LOG_LEVEL | No | Set logging level (debug, info, warn, error) | info |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| process_audio_fileC | Apply audio processing operations to a single file using FFmpeg |
| batch_process_audioC | Apply audio processing operations to multiple files in a directory |
| apply_presetC | Apply predefined audio processing preset optimized for specific use cases |
| list_presetsC | List all available audio processing presets with their descriptions |
| get_queue_statusB | Get current status of the audio processing queue |
| generate_variationsC | Generate multiple variations of a sound from a single input - perfect for creating sound families |
| create_harmonicsC | Create harmonic variations by adding octaves and musical intervals |
| advanced_processC | Apply advanced audio processing including pitch shifting, spectral processing, dynamics, and spatial effects |
| layer_soundsC | Layer multiple sounds together with advanced blending and timing |
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 9 tools
Most tools have distinct purposes, but 'advanced_process' and 'process_audio_file' could cause confusion since both handle audio processing operations. The descriptions help differentiate them (advanced vs. single-file FFmpeg-based), but the overlap in core functionality creates some ambiguity.
All tools follow a consistent snake_case verb_noun pattern (e.g., 'apply_preset', 'batch_process_audio', 'layer_sounds'). The naming is predictable and readable throughout the set, with no deviations in style.
With 9 tools, the count is well-scoped for an audio processing server. Each tool appears to serve a specific and useful function in the domain, from basic processing to advanced features like harmonics and variations, without feeling bloated or thin.
The tool set covers core audio processing workflows well, including single and batch processing, presets, sound layering, and queue management. A minor gap exists in lacking explicit tools for audio analysis or metadata handling, but agents can likely work around this with the provided operations.