
Audio Analyzer
io.github.JuzzyDeePublished by GitHub account JuzzyDeev1.0.0Updated Oct 24, 2026
Gives LLMs ears. Spectral, harmonic, rhythm, stereo, and structural audio analysis.
Overview
A local MCP server that lets an assistant analyze audio files on disk, returning key, tempo, loudness, stereo, timbre and section data as compact text.
- What you can do
- Read basic file info such as duration, sample rate and sample count from a local audio file (mp3, wav, flac, ogg, aac). Compute spectral and temporal features: brightness, richness, MFCC timbre, frequency band energy, spectral contrast, dynamic range, LUFS loudness and stereo field. Detect key, pitch class distribution and tonnetz, plus tempo, beat positions and tempo stability. Run a full analysis combining all of the above with percussive character and structural section boundaries. Compare two tracks side by side in a compact diff table. Optionally return time-series tables at low, medium, high or custom resolution to show how features evolve.
- When to use it
- Useful when you want an assistant to describe, diagnose or compare music and other audio files already on your machine, for example checking key and tempo, judging mix loudness and stereo issues, or mapping a song's sections. It suits music production and audio review work rather than playback or editing.
- Requirements
- Runs as a local stdio process on the user's machine, installed as a platform-specific bundle for Claude Desktop or as a binary for Claude Code; building from source needs Rust and Cargo. It requires Claude Desktop or Claude Code and does not work in the browser or mobile apps. No accounts, API keys or environment variables are declared. Audio files must be given by full local path.
Installation
In SourceWeft
- Open Audio Analyzer in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
audio_visualizer_rs
An MCP server that gives Claude the ability to hear music.
Point Claude at any audio file and it can tell you the key, tempo, dynamics, timbre, percussive character, stereo field, structural sections, and how the music evolves over time -- all from raw audio analysis, no images, no guessing, under 1% context window usage.
Compare two tracks side-by-side. Detect where the music changes structurally — intro, verse, chorus, bridge — and zoom into the moments that matter.
What is this?
LLMs can see (vision) and read (text), but they can't hear. This project bridges that gap by running real audio analysis -- the same DSP techniques used in music information retrieval research -- and returning structured numerical data that Claude can reason about.
It's an MCP server that exposes audio analysis as tools Claude can call on demand. Ask Claude to analyze a song and it will decode the audio, run spectral/harmonic/rhythm/percussive analysis, and return the results as compact text. No spectrograms, no images, no wasted tokens.
Full analysis of a 60-second track completes in under 2 seconds (including source separation). Pure Rust. No Python, no FFmpeg, no system dependencies.
Features
- Audio decoding -- mp3, wav, flac, ogg, aac via Symphonia (pure Rust)
- Spectral analysis -- centroid (brightness), bandwidth (richness), rolloff, flatness (tonality)
- Frequency band energy -- RMS energy across 7 standard producer bands (sub-bass through brilliance) for mix diagnosis
- Spectral contrast -- peak vs valley per band in dB, reveals clarity vs muddiness
- Dynamic range -- crest factor, loudness range (95th-5th percentile), peak dBFS
- LUFS loudness -- EBU R128 integrated loudness (ITU-R BS.1770-4 stereo channel summing), true peak (dBTP), loudness range (LRA), streaming platform targets. Validated to 0.0 dB of FabFilter Pro-L 2.
- Stereo field analysis -- phase correlation (mono compatibility), stereo width (mid/side ratio), L/R balance, mono compatibility score. Per-frame time-series to pinpoint where phase issues occur.
- Temporal features -- RMS energy (loudness), zero crossing rate (texture)
- Timbre -- 13 MFCCs (Mel-frequency cepstral coefficients)
- Harmonic analysis -- chromagram, key detection (Krumhansl-Schmuckler algorithm), tonnetz
- Rhythm analysis -- tempo estimation, beat tracking, onset detection, tempo stability
- Percussive character -- harmonic/percussive source separation (HPSS), attack sharpness, onset density
- Section boundary detection -- multi-feature novelty analysis detects structural changes (energy, spectral, harmonic, texture). Enables a summary→zoom workflow: get the map, then dive into interesting moments
- A/B comparison -- analyse two tracks side-by-side, get a compact diff table highlighting differences in loudness, dynamics, spectral balance, stereo field, key, and tempo
- Time-series data -- track how every feature evolves over time at selectable resolution
- Token-efficient -- downsampled output calibrated to fit comfortably in the context window
See it in action
Watch a fresh Claude analyse four tracks in one session — an original piano/brass composition, Bohemian Rhapsody's full structure mapped with section boundaries, an A/B mix comparison with production advice, and a thunderstorm field recording where it triages music metrics as "meaningless" vs "physically real." All four analyses fit in a single context window.
Installation
Claude Desktop — one-click install
Download the .mcpb bundle for your platform from GitHub Releases and open it. Claude Desktop will handle the rest — no config files, no terminal, no setup.
Claude Code — Homebrew (macOS)
Claude Code — manual (all platforms)
Download the mcp-server binary for your platform from GitHub Releases, then:
Build from source
Restart Claude Desktop. The audio analysis tools will be available in your conversations.
Note: This is a local MCP server using stdio transport, so it requires Claude Code or Claude Desktop. It does not work with claude.ai in the browser or mobile apps.
Usage
Important: This tool analyses files on your local machine. Give Claude the full file path (e.g., /Users/you/Music/song.mp3) -- don't try to upload or attach files to the chat. Claude will read the file directly from disk.
CLI (standalone)
MCP tools
Once configured, Claude can call these tools directly:
Example: full_analysis output
Here's what full_analysis returns for a 60-second jazz trio track:
When you add resolution: "medium", the output also includes a time-series table showing how every feature changes over the track's duration -- letting Claude see the intro build, the dynamic solo section, and the quiet outro.
Time-series resolution
All analysis tools accept an optional resolution parameter that controls time-series output:
You can also pass a numeric string (e.g., "20") for custom rates.
Without resolution, tools return summary statistics only (averages across the whole track). With it, you get a compact TSV table showing how features evolve over time -- centroid, RMS, dynamic range, chroma, onset strength, percussive ratio, band energy, spectral contrast, and more, all aligned to the same time axis.
The presets are calibrated for token efficiency. A 3-minute track at "medium" resolution produces roughly 180 rows of data -- enough to track musical structure without blowing up the context window.
Architecture
Two binaries share the same analysis library:
cli(src/main.rs) -- runs all analyses and prints resultsmcp-server(src/mcp_server.rs) -- exposes tools over stdio JSON-RPC via rmcp
Key dependencies: symphonia (audio decoding), rustfft (FFT), rmcp (MCP SDK).
Changelog
See CHANGELOG.md for version history.
License
MIT License. See LICENSE for details.
Source: README.md at commit 0387fe1
Tools
0Version history
1- v1.0.0LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts