Audio Analysis MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUDIO_ANALYSIS_OUTPUT_DIR | No | The directory where visual analysis outputs (spectrograms, waveforms, etc.) are saved. Defaults to ~/.audio-analysis-mcp if not set. | ~/.audio-analysis-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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audio_analyzeA | Analyze audio. ops: fingerprint|formants|compare|diff|spectrogram|waveform|waterfall|pitch|onsets|batch |
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 1 tool
With only one tool, there is no possibility of confusion between tools. The single tool's purpose is clearly defined as audio analysis.
With only one tool, naming consistency is trivially maintained. The name 'audio_analyze' appropriately describes its function.
The server has only one tool for a broad domain (audio analysis), which is too few for the apparent scope. A more modular set of tools (e.g., separate tools for each operation) would be appropriate.
The single tool covers many common audio analysis operations via the 'ops' parameter, but bundling them into one tool makes the surface less intuitive and may miss operations like audio input handling or transcription.